Moderation System
Configure moderation command permissions, role restrictions, and channel limits through the dashboard
Overview
The moderation module lets you control who can use each moderation command and where they can use it. Navigate to Left sidebar > Moderation on your server dashboard to manage all command-level permissions. Each command (ban, kick, timeout, mute, warn, clear, role, massrole, lock, unlock, slowmode, jail, tempban, and more) has its own independent settings card. Server administrators always bypass these restrictions.
Enabling the Module
Toggle the main enabled switch at the top of the Moderation settings page to activate dashboard-level permission control. When the module is disabled, moderation commands still work but rely only on Discord's built-in permission system. When enabled, the dashboard permission layer is applied on top of Discord permissions, giving you more granular control over who can use each command.
Per-Command Settings
Each moderation command has its own settings card on the dashboard page with these options:
enabled (toggle): Turn the command on or off for the entire server. When disabled, no one can use this command regardless of their roles.
allowRoles (multi-role picker): Select which roles are allowed to use this command. Only members with at least one of these roles can execute it. Leave empty to fall back to Discord's default permission check.
ignoreRoles (multi-role picker): Select roles that are protected from being targeted by this command. For example, adding a staff role here prevents moderators from accidentally banning other staff members.
allowChannels (multi-channel picker): Restrict the command to specific channels only. Leave empty to allow everywhere.
ignoreChannels (multi-channel picker): Block the command from being used in specific channels.
deleteCommand (toggle): Automatically delete the slash command invocation message after execution.
deleteReply (toggle): Automatically delete the bot's response message after a few seconds.
enabled (toggle): Turn the command on or off for the entire server. When disabled, no one can use this command regardless of their roles.
allowRoles (multi-role picker): Select which roles are allowed to use this command. Only members with at least one of these roles can execute it. Leave empty to fall back to Discord's default permission check.
ignoreRoles (multi-role picker): Select roles that are protected from being targeted by this command. For example, adding a staff role here prevents moderators from accidentally banning other staff members.
allowChannels (multi-channel picker): Restrict the command to specific channels only. Leave empty to allow everywhere.
ignoreChannels (multi-channel picker): Block the command from being used in specific channels.
deleteCommand (toggle): Automatically delete the slash command invocation message after execution.
deleteReply (toggle): Automatically delete the bot's response message after a few seconds.
Permission Hierarchy
When a member uses a moderation command, the system evaluates access in this order:
1. Server administrators always pass all checks and can use any command.
2. If allowRoles is configured, the member must have at least one of the specified roles.
3. If allowChannels is configured, the command must be used in one of the allowed channels.
4. ignoreRoles and ignoreChannels add exclusions on top of the allow rules.
5. The bot enforces Discord's role hierarchy: a moderator cannot target a user who has a higher role position.
This layered approach ensures sensitive commands are only accessible to trusted staff in designated channels.
1. Server administrators always pass all checks and can use any command.
2. If allowRoles is configured, the member must have at least one of the specified roles.
3. If allowChannels is configured, the command must be used in one of the allowed channels.
4. ignoreRoles and ignoreChannels add exclusions on top of the allow rules.
5. The bot enforces Discord's role hierarchy: a moderator cannot target a user who has a higher role position.
This layered approach ensures sensitive commands are only accessible to trusted staff in designated channels.
Moderation Log
Every moderation action (ban, kick, timeout, warn, mute, jail) is recorded in the user's moderation log. Use the /modlog command to view a member's full history. Each entry shows the moderator who took the action, the reason provided, and the timestamp. Staff can use /warn_remove to delete individual warning entries. The /warnings command shows only warning entries for a specific user.
Tips
Restrict sensitive commands like ban, kick, and tempban to senior staff roles using the allowRoles picker. Use the allowChannels setting to confine moderation commands to a staff-only channel, keeping moderation actions out of public view. Enable deleteCommand on all moderation commands to keep channels clean. Add your staff role to ignoreRoles on destructive commands to prevent accidental actions against other moderators.