Initial setup and repair
Verify prerequisites and use the supported administrator command to create or repair Jail and Ban Review surfaces.
- Audience
- team lead · server admin
- Availability
- free · premium preview · private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
What setup can create or repair
The supported setup workflow checks and repairs the selected server's moderation role, jailed role, private jail category, logging destinations, and Ban Review forum where that feature is enabled.
Inspect health before running setup
The registered setup command requires Discord Administrator permission. The bot also needs sufficient channel, message, and role permissions with a role position above the roles it must manage.
Start in System Health to identify failed or warning checks, then run `/admin setup watchlist:false …` in the intended Discord server with only the supported options needed for that repair.
- The intended server and staff-only visibility model agreed.
- Discord Administrator permission for the person running setup.
- The bot role placed high enough for supported role and channel changes.
Repair one Discord surface at a time
Read Setup Checker
Review configuration, Discord object, bot permission, and feature-specific groups before changing the server.
Check: Each missing or stale prerequisite has an explicit status and detail.
Choose the repair scope
Use the setup command and select only the Jail or Ban Review options and existing private forums required by the server.
Check: The command receives a focused server repair request.
Review created or reused surfaces
Read the command result and inspect the resulting roles, private category, channels, and forums in Discord.
Check: The administrator knows what was created, reused, or still needs attention.
Re-run health and permission checks
Refresh System Health and test each staff-only surface with an appropriate staff role and an ordinary member account where your policy permits.
Check: Health and actual visibility agree before moderators begin work.
Verify roles, channels, and visibility
The selected server has supported moderation surfaces with verified staff visibility, or a concrete failed check that identifies the remaining server-scoped repair.
What supported setup creates or reuses
| Object | Purpose | Verify |
|---|---|---|
| Moderation/staff role reference | Identifies staff who should reach supported moderation surfaces. | Correct role ID, member assignment, and no unintended ordinary-member access. |
| Jailed role | Marks the active jail restriction and drives channel overwrites. | Bot can assign/remove it and it sits below the bot role. |
| Private jail category | Contains supported jail text and voice workspaces. | Jailed member, staff, bot, and everyone-role overwrites match policy. |
| Jail log/destination settings | Receives the supported jail and release record handoff. | A safe test action reaches the intended staff-only destination. |
| Ban Review forum and reviewer role | Hosts the senior review workflow when enabled. | Only authorized staff can see posts and the configured role is pinged/routed as intended. |
Bot permissions and hierarchy checklist
| Capability | Used for | Failure signal |
|---|---|---|
| Manage Roles | Apply/remove the jail role and restore assignable saved roles. | Role changes fail or Health reports hierarchy/permission problems. |
| Manage Channels | Create, update, archive, or delete supported jail/review surfaces. | Category/channel/forum creation or cleanup fails. |
| View Channel / Send Messages / Read History | Operate private staff and jail workspaces and post control messages. | Panels, logs, or transcript collection are absent/inaccessible. |
| Manage Messages / Embed Links / Attach Files | Render supported controls, logs, evidence, and notices. | Messages are incomplete or artifact delivery fails. |
| Moderate Members / Ban Members | Execute the corresponding moderation workflows. | Action is blocked even when the moderator is authorized. |
| Role position above managed targets | Discord hierarchy enforcement for role/member actions. | Target or role is not manageable despite permission flags. |
Run /admin setup
The supported setup command repairs one server. It can create or reuse the core Jail setup and, when requested, the Ban Review forum and reviewer role. Use Discord autocomplete because option availability can change; do not use legacy setup aliases.
/admin setup watchlist:false ban_review:true ban_review_role:@Senior Review/admin setup watchlist:false ban_review:true ban_review_forum:#ban-review ban_review_role:@Senior ReviewCapture the before state
Record selected role/channel/forum IDs, relevant overwrites, and the current Health result.
Check: Rollback information exists.
Use the narrow options
Keep the active-development setup option disabled, then select only the Ban Review options that the server has approved.
Check: The command request stays in scope.
Read created/reused/skipped results
Inspect every line of the ephemeral setup response.
Check: The administrator knows which objects changed.
Inspect Discord directly
Open the category, jail role, channels, forum, and reviewer role; review overwrites and bot hierarchy.
Check: The actual server state matches the command summary.
Run a safe fixture
Use a controlled test member or non-destructive visibility test according to server policy.
Check: Staff and ordinary-member visibility are verified.
Fix an incomplete setup
Setup created some objects but not all
What you see: The result lists created/reused resources alongside one or more errors, or Health still reports Action needed.
What may be happening: Discord hierarchy, missing permissions, stale configured IDs, duplicate names, feature access, or custom overwrites can block only part of the operation.
What to do
- Do not delete every created object.
- Open System Health and address the first failing check.
- Correct the specific role, channel, permission, or stored selection.
- Run the targeted setup repair once more and compare created/reused results.
Recover a partial setup
A successful command is not production certification and cannot override Discord hierarchy. Feature-specific forums still depend on their entitlement/flag, and existing custom permission overwrites need live review.
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
- Reopen System Health and address the first failed check.
- Verify the bot role position and required Discord permissions.
- Confirm staff-only forum/category visibility.
- Run the targeted repair once more only after confirming the previous result.