Docs · Explanation

Organizations & ownership.

Your projects, domains and data belong to your organization rather than to your user account, so people can be added or removed without affecting anything you have deployed.

There are two things in a Canner login, and keeping them apart is what makes the rest of this predictable. Your account is you — your email, your password, your passkeys. Your organization is what owns things: every project, every domain, every dataset, every Canner Auth app, and the plan they are billed on.

You get one organization when you sign up, and you are its admin. If you gave a company name it takes that name; otherwise it is named after your email, and you can tell us different later.

Why the split exists

Because people change and infrastructure shouldn’t. Someone leaves, an email address changes, a founder hands over billing — none of that should be able to strand a running site. When the organization owns the project, those are edits to a membership list, not migrations.

It is also why plan limits are counted once per organization rather than once per person. Two people in one organization share a project count, a storage quota and a bill; they do not each get their own.

Names and handles

An organization has a name, which is a label — two organizations can share one, and you can change yours. It also has a handle, which is unique, and an ID, which never changes and is the thing to quote if you contact us.

Handles look like doneright-technologies-k4m9x2p. The short code on the end is random rather than a counter, so two organizations called the same thing get equal handles and neither is told the other exists.

Where to find it

Organization (under Settings) shows your organization and its users. Plans and quotas that apply to it are in Plans & limits.

Adding people

Invite people, choose Admin or a Member with fine-grained View/Edit permissions, and manage seats — see Users & permissions.

Requiring passkeys

An organization admin can require a passkey for every user (Organization → Sign-in security). It is off by default. While it is on, users can open the organization only after signing in with a passkey, and anyone who has none is asked to add one. To turn it on, sign in with your own passkey first, so you can’t lock yourself out. The same page lists who has no passkey yet. API tokens are not affected: they are the credential for automation, and they can be given an expiry of up to a year.

Your account

These settings are on Account and apply to you, not to the organization.

Changing your password

The new password applies the next time you sign in. Devices that are already signed in stay signed in until their session expires. To end them now, use Sign out all other devices on the same page. Resetting a forgotten password by email signs you out everywhere.

Passkeys on one device

A passkey synced by your password manager or platform account (iCloud Keychain, Google Password Manager, 1Password) follows you to your other devices. One that isn’t synced is marked This device only: it lives on that device, so if you lose the device you lose the passkey. Keep a second passkey, or a password, as a way back in.

Deleting your account

If other members remain in your organization, deleting your account removes only you, right away. The organization, its projects and its plan carry on.

If you are the last member, the organization is deleted with you. Its projects are stopped and its subscription is cancelled immediately, and everything is erased permanently after a 24-hour grace period. Signing back in during those 24 hours cancels the deletion, but the subscription stays cancelled: subscribe again from Billing. A domain bought through Canner is not deleted: it stays registered (auto-renew off) until you contact us.