Server access and dashboard
Select one approved server, understand access denial, and keep every administration action in the correct Discord context.
- Audience
- team lead · server admin
- Availability
- private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Keep every change in the right server
The dashboard uses the signed-in Discord account to list server-specific access states. Selecting a server establishes the context for settings, records, permissions, plan status, and every later API request; selection never grants authority by itself.
Confirm the account and selected server
The account must belong to the server, the server must have approved ModFlow runtime access, and the viewer must satisfy the live dashboard access policy. Individual pages and actions can require additional effective permissions.
Sign in through the public dashboard, choose the intended server, and verify the server name and Discord ID before opening administrative data.
- A Discord account in the intended server.
- Approved ModFlow access for that server.
- A server role or ModFlow team mapping that supports the intended page.
Open the required administration surface
Sign in and review the picker
Complete Discord sign-in and read the access state beside each available server.
Check: The viewer sees only server choices returned for the current account.
Select and verify
Open one server and confirm its name and Discord ID in the dashboard context before reading or changing anything.
Check: Later requests are scoped to the intended server.
Test the required page
Open the specific Settings, Health, Teams, Records, or Plan page needed for the job.
Check: The page either opens under its effective permission or returns an explicit access block.
Resolve the denial
Check membership, approved access, Discord permissions, and ModFlow team mapping with a server administrator.
Check: Access is corrected at the server boundary rather than bypassed.
Verify access before changing data
The authorized administrator reaches one selected server and can distinguish picker access from page-specific and action-specific permission.
Understand every access layer
| Layer | Question | What denial means | Who can correct it |
|---|---|---|---|
| Discord identity | Which Discord account completed sign-in? | The wrong account cannot see the intended server or role membership. | The user signs out and selects the correct Discord account. |
| Server membership | Is the account currently in the intended Discord server? | ModFlow cannot treat the user as server staff. | The server manages membership; ModFlow cannot bypass it. |
| Runtime approval | Does this server currently have approved ModFlow access? | The server can appear unavailable even when the user has Discord permissions. | The approved access process/product owner. |
| Dashboard entry | May this role open the selected-server dashboard? | The user can authenticate but cannot enter the server workspace. | A server administrator reviews the dashboard access mapping. |
| Page visibility | May the team open this page? | Navigation or a direct route is hidden/denied. | A team-permission manager grants only the needed page capability. |
| Record visibility | May the viewer see this Case, evidence item, transcript, note, or export row? | The page opens, but the item is hidden or redacted. | An authorized reviewer or server administrator reviews scope and visibility. |
| Action authority | May this operator perform this exact write on this target now? | The control is disabled or the API rejects the attempt. | The relevant team/Discord permission owner; never the viewer by workaround. |
Read the server picker and shell
Verify the account
Read the signed-in Discord identity before selecting a server, especially on shared or multi-account browsers.
Check: The dashboard session belongs to the intended staff account.
Read each server state
Distinguish available, approval-blocked, membership-limited, or otherwise unavailable rows instead of assuming every mutual server is operable.
Check: The user understands why a server may be listed but inaccessible.
Open one server
Select the intended server and confirm its name and numeric Discord ID in the shell, breadcrumb, or URL context.
Check: All later reads and writes use the correct server scope.
Check the page before the job
Open the exact page needed and read any permission, plan, feature, or maturity notice before preparing sensitive work.
Check: The operator knows whether the job can be completed on this server now.
| Element | Use |
|---|---|
| Server name and icon | Quick visual confirmation; do not rely on the name alone when servers have similar branding. |
| Discord server ID | Definitive scope for handoff, troubleshooting, and similarly named servers. |
| Breadcrumb/page title | Confirms which page and nested record the user is operating. |
| Navigation visibility | Shows pages the current dashboard response presents, not every action the user can perform. |
| Status or access notice | Explains plan, feature, approval, or permission restrictions for the current page. |
Safe session and deep-link practices
- Return to the server picker before switching between servers; do not edit the guild ID in a copied URL.
- Confirm the server after opening a deep link from Discord, a handoff message, or browser history.
- Refresh a stale detail page before performing a write, because another moderator may have changed the state.
- Sign out of shared devices and do not share session cookies, OAuth tokens, or authenticated deep links as a substitute for access.
- Use a supported record link for handoff; include the server ID and safe record identifier in case the recipient cannot open it.
- When the wrong server was selected, stop and verify whether any write already completed before repeating it in the correct server.
A copied link opens the wrong or unavailable context
What you see: A deep link redirects to server selection, opens an access block, or shows a similarly named server/record.
What may be happening: The user may be signed into another Discord account, lack server/record access, or be using a stale or manually altered URL.
What to do
- Return to the server picker.
- Confirm the signed-in account and server ID.
- Navigate to the record from the current server rather than editing the URL.
- Ask for a narrow permission review if the record remains denied.
Administrator page map
| Job | Page | Verify |
|---|---|---|
| Review selected-server status and urgent counts | Overview | Server identity, queue counts, recent activity, and links before opening detail. |
| Repair roles, channels, forums, permissions, or hierarchy | System Health plus /admin setup | Live Discord objects and staff/member visibility. |
| Change destinations and server behavior | Settings | Saved value plus one representative Discord event. |
| Map staff roles and least privilege | Settings → Teams | One allowed and one denied action with a representative account. |
| Manage developing staff review paths | Settings → Supervised | Public echo, private review, and escalation audience. |
| Review external source health | Imports / Settings sources | Source identity, provider, preview counts, and provenance. |
| Review plan or billing state | Billing & Plan | Selected-server status and processed entitlement, not only checkout return. |
| Investigate a user-visible failure | System Health | First failing check, owning guide, and post-repair state. |
Resolve an access denial
Discord membership alone does not grant dashboard access. This workflow does not provide generic control over every mutual server and does not expand the account's Discord permissions.
The server does not match the change you made
What you see: A control is unavailable, validation fails, or the resulting server state differs from the intended configuration.
What may be happening: Selected-server context, Discord permission, ModFlow team permission, feature access, stale Discord objects, or concurrent changes may block the workflow.
What to do
- Return to the server picker and verify Discord ID.
- Confirm approved runtime access for the server.
- Check the exact page permission in the server's team mapping.
- Sign out and back in only after the Discord/server access state has been corrected.