Portal for R
Sign in with Discord. We verify your membership and the Staff role before a staff session is ever created.
Your Discord password never touches this app. OAuth tokens are not kept in the browser session.
Discord verification
Role check in progress
Staff member
Discord account · guild member
A session is created only after Discord confirms the role. Failed checks are sent back to this page.
Built for the whole stack
One identity check. Two ways to use it.
Humans get a focused staff dashboard. Other services get a narrow, token-protected lookup endpoint.
Discord OAuth
One sign-in path, backed by Discord. There is no second password to manage or forget.
Role-gated by design
Access is only granted when your guild member record includes the Staff role.
Machine-friendly API
A bearer-token endpoint lets another service look up any Discord user and, when relevant, their staff status.
How the login works
No role, no session.
- 01
Discord OAuth
You approve the identify and guild member scopes.
- 02
Role verification
The server reads your member record and checks the role ID.
- 03
Staff session
Only verified members reach the dashboard.
For the other webapp
Send a POST request with a Discord ID and an API bearer token.
Ready when your role is.
Sign in with the Discord account you use in our Discord server. If the Staff role is on your member record, you are in.