What is an account
If a space is where you make things, an account is who you are across all of them. It is your personal identity on the platform, and it sits above spaces rather than inside any one of them. With a single account you can own or edit several spaces and follow many more, all without juggling separate logins.
Identity hangs on an accountId, not an email
An account is anchored to a stable accountId. Your email address is how you sign in, not who you are. This distinction matters more than it first appears: the email you use in one space may differ from the one you use in another, and you are still the same person to the platform. Your identity does not fracture because you used a work address here and a personal one there.
accountId → the stable you, the same in every space
email → a way to reach you, free to differ per space
The account dashboard
The account dashboard is your launchpad — a single overview of every space you touch. For each one it shows what you need to orient yourself and jump in:
| Column | What it tells you |
|---|---|
| Space | name and link to open it |
| Plan | what tier the space is on |
| Role | what you can do there (owner, editor, follower) |
From here you move between sites without re-authenticating against each one. It is the one screen that knows about all of them at once — precisely because it lives in the account layer, not in any single space.
Spinning up a second space
Because the account already knows you, creating another space is quick. If you are signed in, you do not repeat email verification — the platform already trusts this account. You name the new space, it is provisioned (see The adoption model), and it appears on your dashboard. The friction of “prove who you are again” is gone, because that question was answered once, at the account level.
Why accountId instead of email
Tying identity to a stable id rather than an email keeps a common, awkward event cheap. When you change your email, that change is a local mutation on one account record — a single edit in one place. If identity were keyed on email, the same change would mean rewriting your identity everywhere it appears, across every space you belong to: a risky, fan-out rewrite with many chances to go wrong. The accountId absorbs the churn so the rest of the system never has to.