Auth

Whose sign-in is waiting, so somebody on a shared computer can see it is not theirs.

When the step closes.

Where the sign-in was going, for a Google sign-in, whose destination the server carried; null for the other ways in, whose page kept its own.

Where the sign-in was going, for a Google sign-in, whose destination the server carried; null for the other ways in, whose page kept its own.

The one-time code. Returned exactly once and recoverable nowhere.

When the code stops being exchangeable.

Where the consent page should send the browser, code appended as a query.

The command line's own secret. Returned once; it is what collects the token.

When both codes stop working.

How long to wait between polls.

The short code a person types, grouped for reading.

Where to go to approve, for somebody typing it by hand.

The same page with the code already filled in, for a clickable link.

What was decided, echoed so a page rendering the result cannot disagree with the server.

What the command line calls itself, so the page can name it in the outcome.

What the waiting command line calls itself.

When the request stops being approvable.

Whether it asked from the same address as the browser now looking.

When the command line asked.

The two-letter country of that address, or null when not known.

The address it asked from, or null when that is not known.

When it was issued.

That account's address, so the command line can say who it signed in as.

The name it was given, which is what the command line called itself.

Its first characters, which is what every later listing shows.

The plaintext access token. Returned exactly once and recoverable nowhere.

ULID of the token, so it can be matched to a row on the tokens page.

The account it speaks for — whoever approved the request.

When it was issued.

That account's address, so the command line can say who it signed in as.

The name it was given, which is what the command line called itself.

Its first characters, which is what every later listing shows.

The plaintext access token. Returned exactly once and recoverable nowhere.

ULID of the token, so it can be matched to a row on the tokens page.

The account it speaks for.

OAuth 2.0 client id, safe to embed in client-side code.

Fewest characters a password may have, so the page's rule list says the server's number.

Key the sign-up form renders its Turnstile widget with, or null when this deployment has none — in which case sign-up with a password is unavailable and the page should offer Google alone.

Always two_factor; the page goes to /auth/2fa.

The address the link is about: the account's for a confirmation or a reset, the new one for a change of address.

Which kind of link it is — verify, reset or change — so the page says what its button will do.

Always two_factor; the page goes to /auth/2fa.

Always two_factor; the page goes to /auth/2fa.

email-changed once the account moved to the new address — sign in again with it.

The account this session is acting on.

What the account is called, or null for a personal one nobody has named.

Sent because every screen under /account is now about an account rather than about the person reading it, and a page headed with somebody's own name while describing a shared tier is the exact confusion the team screens were redesigned to remove.

Email from Google.

Extra quota this account holds outside its tier, one entry each, oldest first.

The figures in Plan already include these — every one of them is the effective number the server enforces — so this is not a second set of limits to add up. It is what lets a page say why a figure is larger than the tier it names, which is the difference between a benefit and an apparent bug in the dashboard. Empty for almost every account.

Display name from Google, if any.

pending while this person has neither answered nor skipped the first-visit questions, and done once they have.

On the person rather than the account, like the name and the address beside it: somebody in two accounts is asked once. Everybody who had an account before the questions existed reads as done, because the migration that added the table gave them a skipped row (A14).

When the account's grace for being over its plan runs out, or null while it fits.

Non-null means something will be cut on that date — the oldest sites are put to sleep and the oldest custom domains are removed, only as far as it takes to fit. It is served so the dashboard can say so beforehand: nobody should learn about this from a site going quiet.

The quota tier currently applied to this user.

How many unused two-factor recovery codes this person has, or null while two-factor is off. On the session rather than only on the profile because the reminder it drives — three or fewer — is shown on the site list, which does not read the profile.

What the signed-in person may do on that account: Owner or Member.

Served so the dashboard can leave out controls the caller cannot use — a delete button, the billing pages — rather than showing them and reporting a refusal afterwards. It is not the permission: every one of those actions is refused at the handler regardless of what the page drew, and a client that ignored this field would gain nothing but a worse error message.

How many seats the account is paying for, which is what its raised ceilings were computed from.

One on every tier not sold by the seat, where it is a constant rather than a measurement. It is not the number of members: seats are bought and members are people, and the two moving independently is the whole reason inviting somebody does not silently change an invoice.

How much of the plan is currently used.

ULID of the signed-in user.

When the deletion takes effect. Until then it can be called off.

Ten codes, each XXXX-XXXXXX.

Ten codes, each XXXX-XXXXXX.

The otpauth://totp/... URI to draw as a QR code.

The same key in Base32, for typing into an app on a device with no camera.

The browsers, most recently used first.

Every account they are in, with billing for the ones they own.

When the file was made.

What visitors sent through those sites' forms, as kept (ninety days).

The person.

The sites of the accounts they own.

How many accounts they are a member of. Sent because it is the sentence that tells a reader why this page is separate from the account pages, and one number is cheaper than a list nobody reads here.

When they first signed in here.

The address they are written to and sign in with.

Whether that address has been proven to reach them.

Whether Google is one of their ways in.

When Google became one, or null when it is not one — or when it became one before this was recorded.

Whether a password is one of their ways in. False for somebody who has only ever used Google, for whom the page offers to set one rather than to change one.

Their display name, shown to people on their teams, or null when they have none.

When the password was last set, or null when there is none.

Whether they get product email now: consent given and not withdrawn since. Mail about their account and sites is not affected either way.

The person's ULID, which is the identifier worth quoting in a support mail.