Moderate Your Discord Server Effectively with Prowl

Ban, kick, mute, and warn members with full audit logging and conditional auto-bans. Keep your Discord server safe with Prowl’s moderation suite.

Prowl gives your moderation team a complete toolkit to keep your server safe and orderly. Every action is logged automatically, every decision is traceable, and configurable defaults mean the bot handles routine tasks before they become a problem — all without leaving Discord.

Commands

Use slash commands directly in any channel your moderators have access to. Every command records the acting moderator, the target, and the supplied reason in your audit log.

Command	Description	Key Options
/kick <member> [reason]	Remove a member from the server (they can rejoin)	member (required), reason (optional)
/ban <member> [reason] [delete_days]	Permanently ban a member from the server	member (required), reason (optional), delete_days (0–7 days of message history to purge)
/tempban <member> [duration] [reason]	Temporarily ban a member — they are automatically unbanned after the duration	member (required), duration in minutes (optional, default: 1440 / 24 hours), reason (optional)
/unban <user_id> [reason]	Revoke a ban and allow the user to rejoin	user_id (required), reason (optional)
/mute <member> [duration] [reason]	Timeout a member so they cannot send messages or join voice	member (required), duration in minutes (optional, default: 60), reason (optional)
/unmute <member> [reason]	Remove an active mute before it expires	member (required), reason (optional)
/warn <member> [reason]	Issue a formal warning that is saved to the member’s record	member (required), reason (optional)
/purge [count]	Bulk delete messages from the channel (1–100, default: 10)	count (optional, default: 10)
/settings	View the current moderation settings for this server	none
/lockdown	Toggle emergency lockdown — denies @everyone send_messages, deletes all invites, and restores on unlock	none

All commands require the moderator to have the Moderate Members permission, the Administrator permission, or a configured mod role.

Audit Logging

Prowl logs every moderation action — manual or automatic — to a dedicated mod-log channel of your choice.

Setting Up Your Mod-Log Channel

1. Open the Dashboard

   Navigate to prowlbot.xyz and select your server.

2. Go to Moderation Settings

   Click Moderation in the left sidebar.

3. Choose a Log Channel

   Pick an existing channel from the Mod-Log Channel dropdown, or create a new one in Discord first and then return here to select it.

4. Save

   Click Save Changes. Prowl will immediately begin posting log entries to that channel.

Viewing the Audit Log in the Dashboard

In addition to the in-Discord log channel, every action is stored in the dashboard’s Audit Log view under Moderation → Audit Log. From there you can:

• Filter by action type (ban, kick, mute, warn)
• Filter by moderator or target user
• Search by reason keyword

Moderation Settings

From the dashboard you can configure several global moderation defaults:

Setting	Default	Description
DM on Action	Enabled	Send the target a DM explaining the action taken
Require Reason	Enabled	Force moderators to supply a reason before executing an action
Silent Mod	Disabled	Suppress DM notifications to the target
Auto Thread	Disabled	Automatically create a thread for each moderation case
Track Stats	Enabled	Track member and message history for statistics

You can also enable or disable individual commands (/ban, /kick, /mute, etc.) and configure default durations and custom DM messages for each action type.

Emergency Lockdown

The /lockdown command provides a fast way to lock down your server during a raid or emergency. When activated, Prowl will:

1. Snapshot all channel permission overwrites
2. Deny @everyone the Send Messages permission in every channel
3. Delete all server invite links
4. Log the lockdown event to your mod-log channel

Running /lockdown again restores all channels to their previous state and recreates the deleted invites.

Only grant the lockdown command to senior moderators or administrators — it is a powerful tool that affects the entire server.

Best Practices

Always supply a reason for every moderation action. It keeps your audit log readable and gives the moderated user context if they appeal.

• Use mutes before bans. Escalate from warn → mute → kick → ban for non-severe infractions. Reserve immediate bans for spam, NSFW content, and clear raiding activity.
• Lock your mod-log channel. Give the Prowl bot role Send Messages permission and remove it from everyone else so the log stays clean and untampered.
• Review your audit log weekly. Patterns in warnings — multiple warns against the same user — are a signal to escalate before an incident escalates for you.
• Pair moderation with verification. Combining Prowl’s moderation tools with the Verification system provides layered protection against raids and bot accounts.