Create an account and sign in

Create an account at the hosted sign-up page and sign in with your identity provider. An account is global: it can belong to several organizations, and your seat is counted separately in each.

What an account gives you

• Hosted repositories, with the storage and history your plan includes.

• Membership in one or more organizations, each with its own role.

• Device enrolment, so each machine you work from is separately authorised and separately revocable.

• Sessions and personal access tokens, which are separate credential classes with separate rules.

What an account is not

It is not your encryption key. This is the most important thing to understand about hosted TOVIO. Your account authenticates you to the service; your keys decrypt protected file content and live on your devices. Losing access to your account is recoverable. Losing your key is not, and no amount of hosted support can undo it. Back your key up before you do anything else.

It is not the same as a sign-in on the feedback portal. Those are separate systems with separate accounts, and a session on one is never treated as authentication for the other — even though both sit under tovio.dev.

Sessions

Your account settings list every active session: when it was created, when it was last seen, and which one you are using now. You can revoke one, or revoke every session except the current one. Revocation takes effect at the next check the edge makes, not after a cache expires.

Devices

Each device is enrolled and approved individually. A lost laptop is handled by revoking that device, not by changing a password, and revocation takes effect without touching your other machines. Detaching the last device is allowed and returns you to the pre-enrolment state.

Detaching a device removes its binding from your account. The corresponding entry in the key transparency log is superseded rather than erased — an append-only log that could be edited would not be worth having, and the article on the audit chain explains why.

Step-up for high-consequence actions

An organization can require a fresh passkey assertion immediately before certain operations: approving or landing a proposal, breaking someone else's lock, changing settings, minting a token, or requesting a reviewer. The organization sets which operations, and how fresh the assertion has to be.

Two properties are worth knowing. Second factors are passkeys only — no SMS, no authenticator codes. And step-up is an authorization gate on server-mediated actions, never a decryption path: if you hold the keys, you can read your protected content with the identity provider, the authenticator and the hosted service all unreachable.

If you cannot sign in

Account recovery goes through your identity provider. Key recovery is a different problem with a different answer — see the article on losing your key in the permissions collection.