Account & access
How Discord sign-in works, which sessions last how long, and exactly who can open a server's dashboard.
Signing in#
Signing in uses Discord OAuth with the identify and guilds scopes — the site learns who you are and which servers you are in. It never joins a server as you, never reads your messages, and never requests your email.
After Discord returns you to the site, the server list is filtered before you see anything.
Who gets dashboard access#
A server appears in your dashboard if and only if you are:
- the owner of the server, or
- a member holding the Administrator permission (bit 3).
Nothing else qualifies — Manage Server alone is not enough, and there is no way to invite a co-admin to the dashboard beyond giving them Administrator on Discord itself. Opening a dashboard URL for a guild you do not qualify for answers "You don't have access to this server."
Sessions#
| Aspect | Behaviour |
|---|---|
| Storage | A server-side session referenced by an httpOnly cookie |
| Lifetime | Seven days, refreshed on sign-in |
| Contents | Your Discord identity, your eligible guild list, a CSRF token |
| Sign out | Clears the Discord identity; an active admin session is preserved so staff accounts are not logged out of admin tools |
Stale sessions#
If you lose Administrator or leave a server, the filtered list simply stops including it; attempts to open its dashboard are refused by the same guard. Sessions are re-verified against Discord's data when you sign in again.
Two levels, one login#
Regular dashboard access (owner/Administrator) and the site's separate admin area (for marketplace moderation and announcements) are different systems. Being a server owner never grants the site-level admin role.