Code Genome · sign-in & token reskin
Two sign-in paths lead to a download token. Follow a path left → right.
Pages follow your OS light/dark setting; see them together in the
light + dark comparison.
On the token pages, click Reveal / Copy.
Path A · Social login #32 → #14
GitHub or Google, the default experience for most users.
Step 1 · Sign in
Sign in
Continue with GitHub / Google.
→
Step 2 · Consent
Consent (opt-in)
One-time screen after sign-in.
button: “Get my token”
→
Variants of steps 1 and 2:
OAuth error ·
no verified email (recoverable) ·
consent · notice (opt-out regions)
Path B · Customer account #32 → #14
Username + password, for customers provisioned by Moderne who don't use social login.
Step 1 · Sign in
Sign in
Username / password form on the same screen.
→
Step 2 · Manage tokens
Manage tokens
List of your tokens, with revoke.
button: “Generate a download token”
→
Step 3 · After minting
Fresh token
New masked token + snippets, above the list.
Variant of step 1: invalid credentials
Why two different buttons? “Get my token” (Path A) is part of a one-time consent step and
has no management page yet, so revisiting mints another token. “Generate a download token” (Path B)
lives on a real management page with a list and revoke. Unifying these (giving social-login users the
same manage/list/revoke model) is the parked backend work noted on ticket #14.