Sign in and select a server
Use Discord sign-in to reach a server dashboard that your account is authorized to operate.
- Audience
- moderator · team lead · server admin
- Availability
- private beta access
- Maturity
- alpha
Last reviewed
On this page
Outcome
You will sign in with Discord, select one approved server, and recognize the difference between seeing a server in Discord and being authorized to use its ModFlow dashboard.
Set up the lesson
- A Discord account that belongs to the server you intend to moderate.
- Approval-gated ModFlow access for that server.
- A server role or permission that grants the required dashboard surface.
Practice the workflow
Open the dashboard
Choose Open Dashboard and complete the Discord authorization prompt on the official sign-in flow.
Check: ModFlow can identify your Discord account without asking for a bot token or server secret.
Review the server picker
Choose the server where you are an authorized staff member. Do not assume every mutual server is available.
Check: The picker shows the server-specific access state and does not promise generic multi-server administration.
Confirm the selected server
Verify the server name and identifier shown in the dashboard shell before opening records or controls.
Check: Every later action is scoped to the intended server.
Verify your result
The dashboard opens for one authorized server, or it provides a clear access block instead of silently widening your permissions.
Read access as layered checks
| Layer | Question | When it fails |
|---|---|---|
| Discord identity | Which account completed OAuth sign-in? | The wrong account sees the wrong servers and role memberships. |
| Server membership | Is that account still in the server? | The server is absent or access is denied. |
| Runtime approval | Does the server currently have approved ModFlow access? | Membership alone does not open the dashboard. |
| Dashboard permission | May this role enter the selected-server dashboard? | Authentication succeeds but server entry is blocked. |
| Page/record/action | May this viewer open this page, record, source, or write? | A deeper surface can still be hidden, redacted, or denied. |
Verify the server before continuing
Confirm the account
Read the Discord username and avatar used for sign-in. On a shared device, sign out of other accounts first.
Check: The session belongs to the intended operator.
Read the server row
Check the server name, icon, and access state. Do not choose by name alone when two servers look similar.
Check: The correct server candidate is identified.
Open and verify the numeric ID
Confirm the selected-server ID in the page context or URL.
Check: Later handoffs and troubleshooting use the definitive server identity.
Open the exact page
Test the page needed for the job instead of assuming picker access grants all pages.
Check: Any page-specific denial is discovered before sensitive work begins.
| Check | Why |
|---|---|
| Server name and ID | Prevents cross-server actions and mistaken handoffs. |
| Current role/team | Role changes can narrow or expand available pages since the last shift. |
| Page header status | Availability, maturity, and feature state can differ by surface. |
| Target or record identity | A deep link can point to a different member or stale record than expected. |
Protect the dashboard session
- Use a staff-controlled device and supported browser profile.
- Do not share OAuth sessions, cookies, QR codes, or browser storage.
- Lock the device whenever leaving an open evidence, transcript, note, or export page.
- Sign out after using a shared or temporary workstation.
- Never paste a private deep link into a public channel; the link remains sensitive even though it does not grant access.
- Re-authenticate through the official sign-in flow rather than accepting a forwarded login URL.
Recover from a missing or denied server
The intended server is missing
What you see: Sign-in succeeded, but the server does not appear or cannot be opened.
What may be happening: The wrong Discord account, lost membership, runtime approval state, stale session, or dashboard access mapping can block entry.
What to do
- Confirm the signed-in Discord identity and current server membership.
- Return to the picker and search for the exact server name/ID.
- Ask a server administrator to verify approved access and the narrow dashboard permission.
- Sign out and complete one fresh OAuth flow only after the server-side state is corrected.
A page is denied after server entry
What you see: The dashboard opens, but a page or record does not.
What may be happening: Server entry, page visibility, record visibility, source access, and action authority are separate checks.
What to do
- Record the page and exact visible denial.
- Identify whether the missing capability is page, record, source, or action access.
- Request only the minimum permission needed for the job.
- Do not ask another staff member to copy restricted content into a wider channel.
Avoid these mistakes
- Selecting a similarly named server without checking it.
- Treating Discord membership as dashboard authorization.
- Asking for owner-level access when a server administrator should repair a server-scoped role.