How to configure moderation commands with GuildPilot

GuildPilot registers separate slash commands for warnings, timeouts, kicks and bans. The dashboard lets you enable each supported command, choose a private staff log channel and decide whether affected members receive a direct message.

Dashboard - ModerationReal dashboard

Before you start

• Staff need the Discord permission registered for each command: Manage Messages for /warn and /warnclear, Moderate Members for /mute and /unmute, Ban Members for /ban and /unban, and Kick Members for /kick.
• GuildPilot needs the corresponding Discord permission and must be high enough in the role hierarchy to act on the target member.
• Create a staff-only text channel if you want private moderation logs.

Warning: Moderation actions affect real members immediately. Test with a designated account and avoid testing bans or kicks on an account you cannot restore.

Configure moderation commands

1. Open the Moderation hub

Open the server dashboard and select Moderation. The hub shows Transparency channel, Channel Settings and one tile for each configurable command.

2. Open a command page

Choose /warn, /warnclear, /mute, /unmute, /ban, /unban or /kick. Review its description and keep the command enabled only when staff should use it.

3. Configure private logs and DMs

Choose Private staff log channel. Enable Send the affected user a DM when GuildPilot should privately explain the action, reason and moderator. Add Optional message from the moderator only when every use of that command should include the saved text.

4. Review command-specific defaults

For /mute, set Default timeout minutes, which is used when minutes is omitted. For /ban, set Default delete message history days from 0 to 7. Configure warning defaults in the warning guide.

5. Save every command page

Select the page's Save /command button. Settings are independent, so repeat the process for each command your moderators use.

Test the setup

1. Use a moderator with the command's registered Discord permission and a designated test member below the moderator and bot roles.

2. Run a reversible action, for example:

   /mute user:@TestMember minutes:1 reason:Configuration test
   

3. Confirm the private log and DM behavior.

4. Run /unmute user:@TestMember reason:Test complete to restore the account.

What a successful setup looks like

An authorised moderator receives a private command response, Discord applies the action, and the configured staff log or DM is sent. Unauthorised members cannot use commands whose default permission they lack.

Common problems

GuildPilot cannot moderate the member

Cause: The target's highest role is equal to or above the bot, or the bot lacks the required Discord permission.

Fix: Correct the role hierarchy and grant the active bot the matching moderation permission.

A moderator cannot see the command

Cause: They lack the command's default Discord permission or application commands are disabled in that channel.

Fix: Grant the appropriate staff permission and review the channel's Use Application Commands setting.

The user does not receive a DM

Cause: The DM setting is disabled or the member does not accept direct messages from the server.

Fix: Enable Send the affected user a DM. GuildPilot cannot override the member's Discord privacy settings.