Choose between the dashboard and Discord
Use Discord for in-context moderation and the dashboard for deeper review, configuration, records, and handoff.
- Audience
- moderator · senior reviewer · team lead · server admin
- Availability
- private beta access
- Maturity
- alpha
Last reviewed
On this page
Outcome
You will choose the surface that fits the moderation job without treating either surface as a permission bypass.
Set up the lesson
- An authorized server selected in the dashboard.
- A staff role with the permission needed for the intended task.
- A clear moderation job, such as acting on a message or reviewing a case.
Practice the workflow
Use Discord for context
Choose a registered slash command, user menu, message menu, queue, or panel when the source context is already in Discord.
Check: The action begins beside the relevant user, message, or staff workflow.
Use the dashboard for depth
Move to the dashboard for multi-record review, configuration, audit history, exports, or handoff between staff.
Check: The same server-scoped record can be reviewed with more context.
Verify the handoff
Check that the server, member, case, or record shown after the handoff matches the Discord context you started from.
Check: Staff do not act on a stale or cross-server selection.
| Job | Start here | Why |
|---|---|---|
| Warn, mute, jail, ban, or undo an action | Discord slash command or member Apps menu | The target is already in context and the command gives a private result. |
| Save the message that started a case | Right-click the message → Apps | The source message ID, channel, author, and timestamp stay attached to the handoff. |
| Read one member's recent history | /history user:@Maya | The Discord profile is fast and stays inside the current server. |
| Compare several incidents or work a long case | /dashboard, then Cases or Records | The web view has room for timelines, evidence, notes, and handoff. |
| Repair server setup | Use the documented /admin setup form, then Dashboard → System Health | The command performs supported setup; Health shows what still needs attention. |
/dashboardVerify your result
Staff can move between Discord and the dashboard while preserving the same server scope, record identity, and permission checks.
Choose the fastest safe surface
| Job | Start in | Continue in |
|---|---|---|
| Warn, mute, jail, ban, or reverse a member | Discord command or member Apps menu | History, Moderation Log, or linked Case to verify. |
| Preserve a source message | Message Apps menu | Case evidence workspace to label visibility and context. |
| Review several incidents | Dashboard Users or Moderation Log | Case when a decision needs a durable evidence trail. |
| Handle an appeal | Appeals dashboard or appeal command | Linked moderation/Case record and separate reversal result. |
| Review a proposed ban | /ban-request or Start Ban Review | Ban Review workspace for decision and execution. |
| Schedule future work | Scheduled Actions dashboard | Queue history and Moderation Log after execution time. |
| Run a recorded staff session | Soundcheck commands | Voice Evidence and linked Case if an artifact is preserved. |
| Repair settings or permissions | System Health, then Settings or the supported /admin setup path | A representative live test in Discord. |
Use Discord for source context
- Slash-command autocomplete exposes the current option names and required fields.
- Ephemeral replies keep immediate moderation results private to the operator.
- User Apps preserve the selected member identity.
- Message Apps preserve the source message, author, channel, timestamp, and supported context window.
- Case and evidence buttons can hand off into a deeper dashboard record without making the source public.
Use the dashboard for depth and continuity
| Group | Pages covered | Purpose |
|---|---|---|
| Home | Overview | Selected-server status, recent work, and navigation. |
| Operations | Moderation Actions, Jails | Direct action forms, active restrictions, and execution feedback. |
| Cases & Review | Cases and Appeals | Evidence-led review, decisions, and appeal handling. |
| Work | Scheduled Actions, Automation Rules; Assignments/Templates placeholders | Future work and recommendation-only rules. |
| People & Data | Users, Staff, Staff Notes, Voice Evidence, Moderation Log, Activity, Analytics, Export | Identity, history, metadata, staff context, reporting, and data extracts. |
| Admin | Imports, Settings, Billing & Plan, System Health | Sources, configuration, access, and readiness. |
Verify every Discord-to-dashboard handoff
Capture the identity
Keep the server ID, member ID, case number or case ID, and source message reference from Discord.
Check: The destination can be compared to the origin.
Open the dashboard link
Authenticate normally and select the same server.
Check: The web session uses the same server context.
Compare the record
Verify member, source, case title/number, and latest state before editing.
Check: A stale or wrong deep link is caught.
Complete one write
Use only the needed dashboard control, then refresh the owning detail page.
Check: The resulting state and timeline are explicit.
Return a concise handoff
Post the record reference and current state to the authorized staff location.
Check: Discord and dashboard remain synchronized through the record, not copied private content.
Avoid these mistakes
- Using the dashboard as a way around Discord permissions.
- Assuming every command is registered or enabled on every server.
- Opening a deep link without confirming its server and record.
Dashboard messages and Discord delivery
The Jail conversation panel reads recent messages from the live Discord Jail channel and can relay a staff response back to that channel. The Appeals conversation can send a Discord direct message to the appellant or save an internal staff-only note. Discord delivery, permissions, privacy settings, deletion, and attachment availability still apply.
- A participant-facing team label is not system-level anonymity; ModFlow retains internal actor attribution.
- A delivered message is not automatically a complete transcript or permanent evidence copy.
- Closed Jail and appeal conversations are read-only, and failed or ambiguous appeal DMs require staff review.