Admin setup and dashboard handoff
Repair supported Discord setup, open the dashboard, and check the result in the same server.
- Audience
- server admin
- Availability
- free · premium preview · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Keep setup work inside one server
The current administrator command group provides a supported setup entry point. `/dashboard` hands an authorized user to the web server picker for deeper selected-server review.
Run the command in the intended server, keep the result, and open the selected-server dashboard only after confirming the server name.
Current server administration entry points
| Command | Server job | Continue in |
|---|---|---|
| /admin setup | Create or repair supported Jail and Ban Review surfaces | System Health and Settings |
| /dashboard | Open the authenticated server picker | The selected-server dashboard |
/admin setup watchlist:false ban_review:false/dashboardRepair, inspect, and continue in the dashboard
Choose the command
Use setup for supported server repair or dashboard for a web handoff.
Check: The request stays within one supported server workflow.
Review options and submit
Use Discord autocomplete, choose only the supported setup you need, and submit once.
Check: The command says what it created, reused, skipped, or could not access.
Continue in the dashboard
Open System Health or Settings for the same server.
Check: You can compare the command result with the live Discord setup.
Keep the error if it fails
If the result is partial or failed, keep the visible message and follow the matching setup guide.
Check: An administrator can diagnose one clear issue without repeating setup blindly.
A supported administrator workflow completes or hands off to the exact selected-server page where its state and recovery can be verified.
Read /admin setup options carefully
| Option | Use | Scope note |
|---|---|---|
| Jail-only: /admin setup watchlist:false ban_review:false | Create/repair the supported Jail foundation and server moderation surfaces. | One server; requires Discord Administrator and bot capabilities. |
| ban_review:true | Include supported Ban Review forum/configuration. | Feature/access state still applies. |
| ban_review_forum | Reuse a verified existing private forum. | Confirm forum ID and permission overwrites. |
| ban_review_role | Select the role to ping for new review work. | A ping role does not grant decision/execution permission. |
/admin setup watchlist:false ban_review:true ban_review_role:@Senior ReviewInterpret the setup response
| Result | Meaning | Next |
|---|---|---|
| Created | A supported role/channel/category/forum was created. | Inspect its ID, name, and permission overwrites. |
| Reused | An existing object matched and was selected. | Verify it is the intended private object, not only a name match. |
| Updated/repaired | Supported stored configuration or permissions changed. | Record the previous state and run a representative test. |
| Skipped | The option/feature was not requested or not available. | Do not infer an error without reading the reason. |
| Failed/partial | One prerequisite or Discord operation did not complete. | Keep the response and repair only the named boundary. |
Read line by line
Identify each object created, reused, updated, skipped, or failed.
Check: The result is not reduced to a generic success/failure.
Inspect Discord
Open each referenced role/channel/forum and verify audience/hierarchy.
Check: The actual server state matches the response.
Open System Health
Refresh setup groups for the same server.
Check: Stored and live prerequisites are re-evaluated.
Run one safe test
Exercise Jail or Ban Review with authorized fixture accounts.
Check: The complete staff/member visibility path works.
Use /dashboard as a context handoff
Run /dashboard in the intended server
Use the current Administrator-gated command.
Check: Discord provides the official dashboard handoff.
Complete normal sign-in
Do not forward or share the authentication/session.
Check: The user is authenticated as themselves.
Select the same server
Compare name and numeric ID.
Check: The web context matches Discord.
Open the owning page
Health for setup, Settings for configuration, Cases/Appeals for review, Records/Activity for history.
Check: The job continues in the correct surface.
Verify after a write
Return to Discord or refresh the owning detail record.
Check: Cross-surface state is confirmed.
Know what is not an administrator command guide
| Area | Status in this guide |
|---|---|
| Changing historical-import jobs | Reserved placeholder only; no commands, options, queue, or cancellation procedure. |
| Changing advisory setup | Reserved placeholder only. |
| Assignments/Task Queue | Unfinished placeholder. |
| Changing intelligence and scorecards | Excluded placeholder. |
| Bot owner/global feature flags | Non-public owner operation. |
| Deployment, tokens, database, backups, providers | Infrastructure-only and outside moderator/admin documentation. |
| Legacy aliases | Compatibility-only; use current grouped commands. |
Recover a partial setup or dashboard handoff
Administrator permission does not guarantee that every optional feature is available or that every Discord role and channel can be repaired automatically. Compatibility-only command names are not current entry points.
The Discord surface is missing or did not complete
What you see: A command, menu, reaction, queue, or panel is unavailable, denied, stale, or uncertain.
What may be happening: Registration, server feature access, Discord permission, ModFlow team permission, source visibility, or interaction state may not support it.
What to do
- Confirm the command under current Discord autocomplete.
- Verify the intended server and returned identifier.
- Open the matching selected-server dashboard page.
- Follow the setup or access guide instead of using unrelated commands.