Moderation Guide

Guardexa provides over twenty moderation commands to handle every common scenario. The core commands include /ban (permanently remove a member), /kick (remove a member who can rejoin), /mute (restrict a member's ability to speak), /warn (issue a formal warning), and /purge (bulk-delete messages in a channel).

To use any of these commands, type the command followed by the target member. For example, /ban @username breaks the rules repeatedly will ban the user and log the reason. Each command supports optional parameters like time durations for temporary bans or mutes. For /purge, you can specify a message count up to 100 and optionally filter by a specific user.

All moderation actions are automatically logged with a unique case ID. You can review any action by running /case <id> to see who performed the action, when it happened, and any attached notes. Every moderation command also notifies the target user via direct message when available, ensuring transparency.

For quick access, consider setting up custom slash command permissions so only specific roles can use moderation commands. This prevents accidental misuse and ensures accountability.

The warning system is designed to track member infractions progressively. Use /warn @username <reason> to issue a formal warning. Each warning is recorded as a case with a timestamp, the responsible moderator, and a detailed reason. Members can view their own warnings using /warnings.

Warning thresholds can be configured from the dashboard. For example, you can set the bot to automatically mute a member after three warnings, kick after five, and ban after seven. These thresholds are fully customizable and can vary by severity level — a spam warning might count differently than a harassment warning.

If a member believes a warning was issued in error, they can submit an appeal using the /appeal command. Appeals are sent to a designated staff channel where moderators can review the evidence. Staff can use /case <id> resolve to close an appeal as resolved, keeping the warning, or /case <id> delete to remove the warning entirely. All appeal decisions are logged for audit purposes.

We recommend requiring staff to include evidence with every warning (such as message links or screenshots) so that appeal reviews have sufficient context.

Guardexa's auto-moderation helps you enforce server rules without manual intervention. Start by configuring the bad words filter using /badwords add <word>. The filter supports exact matches and wildcard patterns, and can be toggled on or off per channel. When a filtered word is detected, the bot can automatically delete the message and optionally warn the sender.

Trap channels are a more advanced feature. Designate a channel where rule-breaking content is actively baited and caught. Members who post prohibited content in these channels are automatically sanctioned based on your configured rules. This is particularly effective for catching spam bots and users who ignore server rules.

Slowmode enforcement lets you set per-channel message rate limits. Use /slowmode <channel> <seconds> to set a cooldown between messages. Guardexa can automatically enforce this and log violations. You can also configure automated actions when members reach specific warning thresholds, such as temporary mutes or kicks, directly from the dashboard's auto-moderation settings page.

All auto-moderation actions are logged alongside manual actions, giving you a complete view of enforcement activity across your server.

Every moderation action in Guardexa creates a case record with a unique numeric ID. Cases are the backbone of your server's moderation history — they provide a complete, searchable log of every action taken by every moderator.

To view a specific case, use /case <id>. This displays the case type (ban, kick, warn, mute, etc.), the target user, the moderator who issued it, the reason, any attached evidence links, and the current status. Cases can be annotated using /case <id> note <text>, which appends internal notes visible only to staff.

The dashboard provides a powerful case browser where you can filter by moderator, user, action type, date range, or status. This is invaluable for performance reviews, identifying patterns of problematic behavior, or preparing reports. You can also bulk-resolve expired cases or export case data for external record-keeping.

We recommend establishing a clear case retention policy. Cases can be archived but are never automatically deleted, ensuring you always have access to your server's full moderation history.