Moderator Dashboard

The oversight dashboard moderators see when they open a server — the server overview, ticket history, and the moderation logs and reports, and nothing else.

Overview

When a member is granted the Moderator role for a server, the Open Dashboard button on their My Servers page opens a focused dashboard for that server. It is a read-only oversight surface: the moderator sees the server overview, the ticket history, and the moderation logs and reports, but cannot change any settings.

For how the Moderator role compares to the other dashboard roles, and how to assign or revoke it, see Dashboard Roles. For the full moderation system (commands, settings, logs, reports), see the Moderation docs category.

What it is

The Moderator Dashboard uses the same Mokito dashboard chrome (fixed header, breadcrumb, sidebar, scrollable content area) as the owner/manager dashboard, but the sidebar is cut down to the three areas a moderator can reach:

• The server Overview page.
• Ticket History — the list of every ticket in the server.
• Moderation — a collapsible section with two sub-pages: Logs and Reports.

Every other module — Members, Fun, Notifications, Roles, Utility, Bot Settings, and the Premium pages — is hidden. The sidebar does not link to them, and opening their URLs directly is blocked.

Who sees it

A member sees the Moderator Dashboard when their highest role in the server is Moderator. If a member also holds a higher role (Owner, Manager, or Support Team), they see that higher role's dashboard instead — the role precedence rule always applies.

The dashboard

Sidebar

The sidebar shows the server icon and name (labelled "Guild"), then the three reachable sections, then the Quick links group.

• Overview — the server stat cards.
• Ticket History — the list of every ticket in the server.
• Moderation — a collapsible section with Logs and Reports.

Overview page

The Overview page is the same stat-card view the owner sees: member, role, and channel counts plus the ticket breakdown cards. The Refresh Data button is absent — the numbers shown are from the last refresh an owner or manager ran.

Ticket History

The Ticket History page lists every ticket in the server (open, closed, and deleted), newest first. Clicking a ticket opens its detail view, which shows the full message transcript and ticket metadata. Moderators can read tickets and transcripts but cannot change ticket settings, panels, or permissions — those live on the owner/manager dashboard. For the full ticket system reference, see the Tickets category.

Moderation

The Moderation section has two sub-pages:

• Logs — the moderation audit trail. Every moderation action (ban, unban, kick, mute, timeout, warn) is recorded with the moderator, the target, the command, and a timestamp. The page can be filtered by command, and active bans are highlighted. Clicking a log entry opens its detail view. See Moderation → Logs for the full reference.
• Reports — user-submitted reports from the /report command. Each report shows the reported user, the reporter, the reason, any notes and attachments staff have added, and a resolve/reopen control. See Moderation → Reports for the full reference.

Moderators can read logs and reports, add notes, and resolve or reopen reports. They cannot change moderation settings (role access, log channel, per-command notification templates, default action options) — those are owner/manager only.

Quick links

The bottom of the sidebar has three Quick links: Home (the public site homepage), My Servers (back to the server list), and Documentation (this docs site, in a new tab).

What it cannot see

The Moderator Dashboard deliberately omits every administrative and configuration surface:

• Members list and member profiles.
• Moderation settings (role access, log channel, notification templates, default actions).
• Fun commands, channel restrictions, and toggles.
• Notifications, Auto Message, and reminder command settings.
• Roles, Auto Roles, and the Embed Builder.
• Bot Settings (per-server bot identity and announcements channel).
• All Premium-gated pages (XP & Levels, Steam Links, Pinned Messages, Highlights).

Navigating to any of those URLs directly is blocked — the access check turns the request away.

Limits & Edge Cases

• Read-only oversight. Moderators can read logs and reports, add notes to reports, and resolve or reopen reports. They cannot change server settings, moderation settings, ticket settings, or any configuration.
• No Refresh Data. The Overview page reflects the last data refresh an owner or manager ran; a moderator cannot trigger a new one.
• Role precedence applies. A member who is both Moderator and a higher role (Owner, Manager, or Support Team) sees the higher role's dashboard, not this one.
• Moderation commands are separate. The ability to run moderation slash commands in Discord (ban, kick, mute, etc.) is governed by moderation settings, not by the Moderator dashboard role. A member can be a moderator in the dashboard without having command permissions, and vice versa. See Moderation → Settings for the role-access configuration.
• Per-server. Being a moderator for one server grants no access in any other server.
• Revocation is immediate. Removing a member from the moderator role takes effect on their next dashboard load — they lose the Moderator Dashboard and fall back to the member view (or nothing, if they are not a member).