Look beyond a single message.
Spam does not always arrive in one channel. Sentinel’s spam rules consider recent activity from a member across your server, including repeated messages and cross-channel bursts. Separate filters cover links, invites, mention floods, blocked terms, repeated characters and excessive capitals.
Choose which rules belong in your community. A busy event channel and a quiet help channel have different needs; channel and role exemptions help you preserve legitimate conversations.
Observe first. Enforce deliberately.
Enable a rule in dry-run mode to see what it detects without deleting messages or punishing members. Review the matches and adjust thresholds before turning enforcement on.
Actions are configurable. Message deletion, warnings and timeouts are not interchangeable, and a detection should not imply that every action succeeded. Discord permissions, channel overrides and role hierarchy still apply.
- Enable the moderation module and Auto-Moderation.
- Create and enable a rule; review its exemptions and actions.
- Test in dry run, inspect the results, then deliberately enable enforcement.
Keep a record your team can use.
Moderation cases connect an action to a member, reason and history. Discord log messages show the rule, context and action outcomes, including failures and detection-only runs. The dashboard gives staff a place to review records without scrolling through a busy channel.
Treat message evidence as sensitive. Choose a staff-only log channel, restrict dashboard access and review who can see moderation records.
Have a response ready for raids.
Incident mode brings raid signals, incident review and configured containment into the same workflow. Prepare your response before a burst of suspicious joins or messages, and keep staff involved in reviewing what happened.
No filter can guarantee that every harmful message will be caught. Continue to review false positives, Discord’s own safety settings and reports from your members.