01
One sign-in, every room.
Sign in once at access.askfinz.ai and every workspace opens for you — chat, research, code, mail, the verticals. No second prompt, no separate password per app. The session is bound to the device, not to a subdomain.
Access · 2026
ASK
FINZ
/ ACCESS
One sign-in · every workspace.
Four identities · one device.
The identity layer underneath every askFinz room.
Access is what makes “sign in once” actually true across the askFinz workspaces. Passkey-first auth, up to four identities per device, session and device management, billing and seats in one place. It's also the dashboard that manages every askFinz OS device you own — SSH, remote desktop, deploy-from-repo, cluster ops.
Switch identity · every room reshapes
Same device. Same workshop. Different room you're in.
access.askfinz.ai
Signed in · passkey
Active sessions
Paul · Personal
paul@personal.tld
Chat
Travel notes · Lisbon
Research
Sleep + sunlight review
News
Daily briefing · 09:00
Switch identity above — every workspace reshapes to the new context. Memory stays scoped per identity.
The mock cycles between Personal, Work and Client identities — every workspace reshapes with the new context, and the billing footer follows the identity that's on the bill.
What it does
Three things.
02
Up to four identities, one device.
Personal, work and the two clients on retainer — keep them side by side without signing in and out. Switching identity reshapes every workspace; memory stays scoped to the identity that wrote it.
03
Recovery without a support ticket.
Passkeys, backup codes, trusted contacts. Lose a device, lose a key — you get back in without a queue. The recovery path is documented in /trust, and we keep a public ledger of how often it fires.
What Access manages
06 surfacesSessions
See every device you're signed in on; sign one out remotely.
Devices
Up to four identities per device; rotation tied to passkey.
Passkeys
Hardware-backed credentials; no passwords stored anywhere.
Recovery
Passkeys, backup codes, trusted contacts — three paths back in.
Billing & seats
Plan, invoices, seats, delegated client seats — one page.
Team & roles
Invite, assign, revoke — every change in the audit log.
Honest scope
What it isn't.
Access is the identity layer for askFinz workspaces. It is not a general-purpose identity provider for third-party apps — it does not issue SAML assertions to your HR tool, and it does not replace your corporate IdP. If you already run an IdP, we federate to it; if you don't, Access becomes the directory for the askFinz workspaces only.
It is also not a password manager. There are no passwords to manage — Access is passkey-first by design, and the recovery paths are documented in /trust.
Access · OS
Identity on top. Cluster ops underneath.
On a regular laptop, Access is the sign-in layer for the askFinz workspaces — one identity, every room. On a machine running askFinz OS it becomes the full management surface for the device: SSH (cert-minted, one-hour TTL), NoVNC, RDP, Wake-on-LAN, package install, k3s + KubeVirt operations, deploy-from-code.askfinz.ai, training-job dispatch. Same identity throughout — the person signing in at the kiosk is the same person running kubectl against their own cluster, with every consequential action landing in the immutable device audit log.
Frequently asked
04 answersDo I have to host my own identity provider?
No. Access is hosted by askFinz. If your organisation already runs an IdP (Okta, Entra, Google Workspace), we can federate to it — but the default is the askFinz identity layer with passkeys and the recovery flows below.
How does multi-identity differ from multi-account?
Other apps log you out of one account to log into another. Access keeps up to four identities open in parallel on the same device. The same workspaces, the same browser tab, the same desktop client — different memories, different billing.
What happens to a workspace when I sign an identity out?
The workspace stays available to the remaining identities on the device. Sessions are scoped per identity, so signing one out doesn't sign the others out. The audit log records who signed out, where and when.
How is this different from askFinz OS?
Access is two things at once: the identity layer underneath every askFinz workspace, and the dashboard you manage your askFinz OS devices from (SSH, NoVNC, RDP, Wake-on-LAN, deploy-from-repo, cluster ops). OS is the Linux distro that lets a device be managed that way. You can use Access on its own with a regular laptop; OS leans on Access for sign-in, remote management and audit logging.
Recovery paths and signal frequency are published in /trust — we keep the ledger honest.
How to start
Access is folded into every askFinz workspace — request access via /beta and your first sign-in provisions the identity layer behind the scenes.