A complete, filterable audit trail of every moderation command run in your server — who ran it, who the target was, the reason, the duration, the result, and when it happened.
The Moderation → Logs page in the guild dashboard records every moderation command invocation — ban, unban, kick, mute, unmute, timeout, untimeout, warn, and report — whether it succeeded, was blocked, or failed. Each entry captures the moderator, the offender, the reason, the duration (if applicable), the result status, the exact time, and the full command payload.
Logs are never deleted. They are the permanent audit trail for your moderation team.
Owners, managers, Mokito admins, and moderators can view the Logs page. Moderators see the same data as owners and managers — the logs are not filtered or redacted for them. This is intentional: moderators need the full history to make informed decisions.
If moderation settings have not been configured yet, owners and managers are redirected to the Settings page with a message to configure first. Moderators are redirected to the guild overview with a message to contact the admin team.
The list is a paginated table (25 entries per page, newest first) with the following columns:
| Column | What it shows |
|---|---|
| Time | When the command was run, formatted as date + time. |
| Command | The slash command name (e.g. /ban, /mute). |
| Moderator | The user who ran the command, with avatar + display name. "Mokito Bot Automation" for automated actions. |
| Offender | The user the command was run against, with avatar + display name. Links to their member profile if they are still in the server. |
| Reason | The reason the moderator provided. "No reason provided" if absent. |
| Duration | The duration in seconds, for timed actions (mute, timeout). Empty for non-timed actions. |
| Action | A "View" link to the detail page for the entry. |
Above the table, a row of filter chips lets you narrow the list to one or more command types. Click a chip (e.g. /ban) to add it to the filter; click it again to remove it. Multiple filters combine with AND. The All chip clears the filter. Only commands that have actually been run in your server appear as filter chips.
If an offender in the list currently has an active ban on record, their row is highlighted so you can see at a glance which bans are still in effect. This is useful for reviewing whether a user is still banned before deciding to unban.
Click View on any log entry to open the detail page. The detail shows:
0).If the offender is currently banned, the detail view also indicates this so you can decide whether to unban.
Every member's profile page in the guild dashboard (Members → click a user) includes a Moderation Actions section that lists every moderation command run against that user. The section has its own filter chips (same as the Logs page) and a paginated table. Each entry links to the full log detail view.
The member profile also shows a Reports subsection if any user-generated reports have been filed against this member, with links to the report detail view.