Backed by: @pithy-sh/auth. Scopes: auth:users:read · auth:devices:read · auth:sessions:revoke · auth:users:logout · auth:devices:revoke · auth:users:export · auth:users:suspend · auth:users:delete.
What it shows
Sessions and devices is what a row here is, the token model is what revoking one actually kills, roles and permissions is who may, and the audit trail is where it is recorded.
The index lists users. The record shows one, with their sessions and their registered devices.
The search box searches the whole user table, not the page already read: your Worker matches the text against each address and display name, up to 200 characters, and answers a page at a time. Its filters are sent to your Worker too: State (active, suspended or deleted), Address (verified or unverified), and Signed up in the last 24 hours, 7, 30, 90 or 365 days. The overview is how the filter panel works.
A search goes in a body, never in a URL. A search term is usually somebody’s address, so the dashboard sends it to POST /auth/admin/users/search with the filters and the page cursor beside it. On a Worker older than @pithy-sh/auth 0.14 the search box is drawn locked, saying so, and the filters still narrow the listing.
The record says where the person stands: active, suspended until a date or until reinstated, or deleted and restorable until a date. A Worker too old to report it is said to be, rather than guessed at.
Fetched live from your D1 and discarded. Nothing is stored here.
What you can do
Revoke one session. Sign a user out everywhere. Revoke a device.
Each is a separate scope, so a support role can be given sign-out without being given device revocation.
Suspend, reinstate, delete and restore
Suspended and deleted accounts is what each state does in your Worker, and the Organizations pane is where the same acts are for an organization.
The act offered follows the standing. An active account can be suspended or deleted, a suspended one reinstated or deleted, and a deleted one restored inside its window. When your Worker does not report the standing, all four are offered, and an act that finds nothing to do says so.
Every act asks why, says what it will do, and confirms once. A suspension ends every session, and may carry an end date in the future; without one it lasts until somebody reinstates it.
Delete is soft unless you choose hard. Soft shuts the account now and leaves it restorable until the purge, and the record shows that date. Hard is irreversible: the purge starts at once, and it is sent only after you type the person’s email address. Restore shows the date the window closes.
A legal hold is a fact on the record, read from your Worker’s hold list with retention:read: held, and since when, because nothing is purged while it stands. Without that scope, the record names it.
A refusal from your Worker is said by name, and the question stays open on it. After a write, the record reads the person again.
Each pair is its own scope. Suspend and reinstate need auth:users:suspend. Delete and restore need auth:users:delete, which your Worker declares deletes, so they are an owner’s, and an admin sees them locked. All four are on the Team plan; on Free or Solo each is drawn locked, saying what Team buys. The standing is on every plan.
Our own trail records each act as customer/user_suspended, customer/user_deleted or customer/user_restored, a reinstatement included, with who pressed it, the person’s id, the outcome, the end or purge date, and the reason.
Export everything held on one person
Answer an access or erasure request is the route this calls and what each part of the document means.
Export everything answers a data-subject request from the record: everything each capability your Worker composes holds on this person, as one file. It asks for a reason first, typically the request’s reference, of at most 256 characters, and sends it as the route’s own reason, in the body of a POST rather than in its URL, so your trail records it beside the disclosure and no request log does.
The record then lists every part, with its state and its capability’s own summary sentence, and for a part kept rather than erased, the basis it is kept on. Download saves your Worker’s document byte for byte, as <subject>-<exportedAt>.json.
When any part is unavailable or not_exported, the record says the export is incomplete and names each one. The file still downloads, unchanged, and its name ends -incomplete. The act becomes Export again, which asks for its reason again, because a second read is a second disclosure.
Read for the screen and held nowhere. Nothing of the document is written to our database, cache or logs. Our own trail records customer/data_exported with who pressed it, the subject, the connection and the reason, when the document was read, and each part’s state. Never a part’s rows, summary or basis.
It needs auth:users:export and the Team plan. The kit declares the route a read, so a member may press it as an owner can. On Free or Solo the act is drawn locked, saying what Team buys. On a Worker older than @pithy-sh/auth 0.14, whose export takes its reason in the URL, the act is drawn locked too, saying to upgrade.
Allowances, one customer at a time
Tiers and allowances is what your Worker declares, and entitlements is where a whole key is comped or revoked, from this record too.
The record lists every quota and feature your Worker declares, with what applies to this person now, where it came from (a plan, a pin, unrestricted, the free floor, or nothing), and what it would be with the override removed. Both reads come from your Worker: the catalog for the names, the per-subject read for the values. A Worker that declares no allowances has nothing here to edit.
Pin a quota. Switch a feature on or off. Unpin one name. Make the account unrestricted, or withdraw it. Each asks for a reason and sends back the version it read. If somebody changed the account since, nothing is written: the record says so and offers to read it again, so two people never silently overwrite each other.
Unrestricted is drawn as its own line, from the read’s own field. A privilege that size is never inferred from every value happening to be unlimited.
Each write is its own scope: payments:overrides:set, payments:overrides:clear and payments:overrides:unrestricted, none of them in the default. Your Worker declares them charges, so they are an owner’s, and an admin sees them locked. The editor is part of Solo; on Free you see every value and where it came from, and each act carries the Solo chip.
No impersonation
Devices are what makes sign out my old phone answerable
A device is durable across every rotation; a session is one live credential.
Revoking a device deletes every session bound to it, then forgets the device — and the response is a count, which can legitimately be more than one.
Only registered devices appear. A client that never sends the device header signs in perfectly well and shows no device — that is an ordinary web session, not a gap.
Language is on the user row
locale is nullable, and null means this reader has never chosen — not English.
That distinction is the column’s whole purpose: null falls through to the browser’s own preference, and en asserts a choice nobody made.
What the dashboard cannot see
A password, because there are none — the kit is passwordless throughout.
A token’s value. Sessions are rows; access tokens are short-lived and not stored.
Every action here is audited
In your trail, under the control-plane actor kind, carrying the connection id and the dashboard user’s own subject.
So what did the management client do is a question your own database answers, separately from what your users did.
Denials are audited too, and this is a surface where an unaudited blocked attempt would be least acceptable.