A full set of moderation slash commands — ban, unban, kick, mute, unmute, timeout, untimeout, warn, report, and mute-role setup — plus a web panel for toggling commands, configuring notifications, reviewing every action, and managing user-submitted reports.
Mokito's moderation system gives your server team the same core actions every Discord moderator needs — ban, unban, kick, mute, unmute, timeout, untimeout, and warn — plus a member-facing /report command and a one-command mute-role setup with /muterole. Every command is a Discord slash command, so your team runs them inline without leaving the conversation.
On the web panel side, the Moderation section of the guild dashboard lets you turn commands on or off per server, configure who can run them, set up notification preferences for each action, review a complete audit trail of every moderation command ever run, and work through user-submitted reports with notes, attachments, and resolve/reopen workflows.
/ban, /unban, /kick, /mute, /unmute, /timeout, /untimeout, /warn, /report, and /muterole./report to flag a user to the moderation team. Reports land in a dedicated channel and on the web-panel Reports page, where staff can add notes, upload attachments, and resolve or reopen them.By default, the following users can run moderation commands (ban, unban, kick, mute, unmute, timeout, untimeout, warn):
| Role | Can run moderation commands? |
|---|---|
| Server owner | Yes — always. |
| Mokito manager | Yes — always. |
| Discord Administrator (users with the Administrator permission) | Yes — always. |
| Additional roles you add on the Settings page | Yes — for the roles you choose. |
| Mokito moderator | Yes — moderators can run all moderation commands in Discord, but cannot access the Settings or Commands pages in the web panel. |
| Support team | No — support team members cannot run moderation commands. |
| Regular members | No — except /report, which any member can use. |
The /muterole command is further restricted: only the server owner or managers can run it. Moderators cannot.
For the full breakdown of what each dashboard role can see and do, see the Dashboard Roles page.
Before any moderation command works in your server, you must configure moderation settings on the Settings page. Until settings exist, every moderation command replies with an ephemeral message telling the caller to contact the admin team to configure moderation on the Mokito web panel.
The Commands, Logs, and Reports pages in the web panel also redirect to the Settings page until settings have been created. This ensures the moderation system is never accidentally left half-configured.
The Moderation section in the guild dashboard sidebar has four sub-pages (plus the Moderator role page, which lives under Members):
| Page | What it's for | Who can access |
|---|---|---|
| Commands | Turn each moderation slash command on or off for this server. | Owner, managers, Mokito admins. |
| Logs | View every moderation command invocation, filter by command, and open a detail view. | Owner, managers, Mokito admins, moderators. |
| Reports | Review user-submitted reports, add notes, upload attachments, resolve or reopen. | Owner, managers, Mokito admins, moderators. |
| Settings | Configure role access, log channel, reports channel, per-command notifications, custom messages, and default action options. | Owner, managers, Mokito admins. |
| Moderator role | Add or remove Mokito moderators for the server. | Owner, managers, Mokito admins. |
The Moderation → Commands page shows a card for each of the 10 moderation slash commands, with a toggle to turn it on or off. Commands are on by default. Toggling a command off only affects your server — it does not affect other servers. See the Command Reference for every command's arguments, permissions, and example responses.
The Moderation → Logs page is a paginated table of every moderation command run in the server, newest first. You can filter by command type, and each row links to a detail view showing the moderator, offender, reason, duration, result, and the full command payload. Moderators can view this page read-only. See the Logs page for the full breakdown.
The Moderation → Reports page lists every user-submitted report. Each report links to a detail view where staff can read the reason and evidence, add internal notes, upload attachments (images, PDFs, text files), and mark the report resolved or reopen it. See the Reports page for the full workflow.
The Moderation → Settings page is where you configure the entire moderation system: who can run commands, where logs and reports are posted, what notifications each action sends, custom public message templates, and default durations. See the Settings page for every option.
The Members → Moderators page lets you add or remove Mokito moderators — users who get a restricted dashboard layout with access to moderation logs and reports but not settings or management pages. See the Moderator Role page for details.
Unbanning a user can be done from two places: the /unban slash command in Discord, or the web panel on the banned user's member profile. Both paths do the same thing — remove the Discord ban and record the unban in the moderation logs.
Run /unban with the banned user's Discord ID and a reason. Because banned users are no longer in the server, you cannot @mention them — you must paste their numeric user ID. See the /unban command reference for the full details.
Open the banned user's member profile in the guild dashboard (Members → click the user). If the user has an active ban, an Unban button appears on their profile. Clicking it opens a confirmation modal that asks for a reason. Confirm, and Mokito removes the Discord ban, revokes the internal ban record, and logs the action in the moderation logs.
The web-panel unban is available to owners, managers, Mokito admins, and moderators. It requires moderation settings to be configured first.
Every moderation command can trigger up to three independent notifications, all configurable per action on the Settings page:
A private Discord DM sent to the user who was punished. The DM includes the action, the server name, the duration (if applicable), and the reason. This is independent of the public message — you can have one, both, or neither.
For /ban and /kick, the DM is sent before the user is removed from the server, because Discord cannot reliably DM a user the bot no longer shares a guild with. For /unban, the DM is never sent — the user is not in the server.
A message posted in the channel where the command was invoked. You choose one of five modes per action:
| Mode | What it posts |
|---|---|
| Disabled | No public message. |
| Public — action | "@user has been **Banned**." (action only, no reason) |
| Public — action + reason | "@user has been **Banned** for **spamming**." (includes the reason) |
| Public — action + reason + moderator | "@user has been **Muted** for **1 hour** for **spamming** by @moderator." (includes the moderator) |
| Public — custom | Uses your custom message template. Mokito Premium feature. |
By default, the five core punitive actions (ban, unban, kick, mute, timeout) are set to Public — action, and the reversal/warn actions (unmute, untimeout, warn) are set to Disabled. You can change any of them.
If you set a moderation log channel on the Settings page, every moderation action posts a structured, color-coded embed to that channel — regardless of the public message setting. The embed includes the offender, action, reason, duration, moderator, and a timestamp. Each action type has a distinct color so the log channel is scannable at a glance:
| Action | Embed color |
|---|---|
| Ban | Red |
| Kick | Yellow |
| Mute | Amber |
| Unmute | Green |
| Timeout | Blue |
| Untimeout | Green |
| Warn | Purple |
Two parts of the moderation system are Mokito Premium features. The core commands — ban, unban, kick, mute, unmute, timeout, untimeout, warn, report, and muterole — are free and available on every server. Premium unlocks the notification extras below.
The Public — custom mode lets you write your own template for the public channel message, per command, with six placeholders: {offender}, {action}, {reason}, {time}, {length}, and {moderator}. On a free server, the custom mode is not available in the dropdown and custom templates are not used — but any templates you save are retained and will activate the moment you upgrade to Premium.
See the Settings → Custom public messages section for the full placeholder reference.
For user-generated reports, Premium unlocks two optional DM notifications:
On a free server, both toggles are locked. Your toggle preferences are saved and will activate when you upgrade. See the Settings → Report DM notifications section for details.