Graphden documentation

Lesson 36 — Signing up & signing in: your account

Goal: by the end of this lesson you can create an account on a graphden cloud, sign back into it (by password or a social provider), verify your email, protect the account with two-factor authentication — and you’ll understand how the same login surface behaves on a self-hosted instance. The org lessons earlier in this chapter (27 Members, 28 Grants) and 37 Plans, next, all assume the account this lesson makes.

Concepts introduced: the /login page, accounts and sign-in identities (one account, many ways in), email verification, account linking, personal orgs, the Account settings, TOTP 2FA.

Accounts and identities

Graphden’s identity model (the open accounts module — docs/ACCOUNTS.md) separates who you are from how you sign in:

One account can hold several identities. Sign up with a password today, link Google tomorrow — both land in the same account. If a social provider vouches for the same verified email your account already owns, the link even happens automatically.

The /login page (cloud)

Open /login. One card, two tabs:

Signing up through a social button skips the password entirely: the provider proves who you are, and a provider-verified email is trusted as verified from the start. (Telegram has no email, so a Telegram-created account starts email-less — you can add one later from your account settings.)

Sessions ride an HttpOnly cookie — sign in once and the editor, the API and every page share it. Signed out, / bounces you to /login.

Forgot your password?

The Forgot password? link on the Sign-in tab asks for your email and always answers the same way — “if that address has an account, a reset link is on its way” — whether or not the account exists (so addresses can’t be probed). The emailed link opens /reset, where you set a new password; doing so signs you out everywhere, on the assumption that a reset means the old password may be compromised. Then sign back in.

(These endpoints are rate-limited per IP, like sign-in and sign-up — a burst of attempts quietly gets the same generic answer.)

Account settings

Once signed in, your self-service surface lives in the editor: click your avatar in the top bar → Settings → the Account section (deep link: /#@settings/account; the old /account URL redirects here). It holds:

Sign out (this device, or everywhere at once) is in the same account menu.

The same surface, self-hosted

Run graphden yourself and the sign-in surface depends on what you enable:

Nothing is hidden; each deployment ships exactly the surface it needs. (Mechanics: docs/ACCOUNTS.md and docs/TENANCY_SEAM.md § Auth seam.)

Try it

On a cloud instance:

  1. Open /login, click Create account. Use a real email and a password (8+ chars).
  2. Submit → you land in the editor with your personal org already provisioned; check your inbox and click the verification link.
  3. Click your avatar → Settings → Account: link a social provider (e.g. GitHub), then sign out and sign back in with that provider instead of the password — same account, same org.
  4. Back in the Account section, enable 2FA: scan/enter the secret in an authenticator app, confirm the code, sign out, sign in with the password — the code is now required.

That’s the whole account lifecycle. Managing other people in your org — adding members by email, granting them narrower capabilities — is Lesson 27 onward.