1. Identify the pattern.
A single unwanted link is different from a member posting the same link across several channels. Use link or invite filtering for the content itself and a spam rule for repeated messages or bursts of activity.
Do not assume every link is harmful. A game community may depend on workshop links, clips and support resources. Decide which channels need stricter rules and keep exemptions deliberate.
2. Check all the switches.
Open Moderation for the correct server. The module, Auto-Moderation and the individual rule must all be enabled. Review the rule’s channel and role exemptions, spam window, thresholds and chosen actions.
Leave the rule in dry run first. Dry run records detections but intentionally does not delete messages or punish members. A matching log with no deletion is expected until enforcement is enabled.
3. Run a controlled test.
Use a test account and channels agreed with your staff. Try ordinary conversation as well as the pattern you want to catch. For a cross-channel rule, check the pattern across test channels rather than only repeating messages in one place.
Review the rule matches and case records. If legitimate conversation triggers the rule, adjust the threshold or a narrowly scoped exemption. Avoid broadly exempting a role that ordinary members can acquire.
4. Verify the action, not just the detection.
When the dry-run results look right, turn off dry run and enable only the actions you intend. Check that Sentinel can manage messages in the affected channels and has the permissions and role position needed for any timeout.
Read the action outcome in the log. Discord may reject a deletion or timeout; an attempted action is not proof of success. Review failed or partial results before deciding the rule is protecting the server.
- Detection absent? Check the enabled state, exemptions and thresholds.
- Detection present but no deletion? Check dry run and selected actions.
- Action failed? Check Discord permissions, channel overrides and hierarchy.
- Activity is escalating? Review incident mode and involve your moderators.
5. Keep the human review.
Revisit rules after busy events and after changes to channels or member roles. Keep evidence in a staff-only log channel and make it easy for members to report mistakes.
Spam detection is one part of community safety. Combine it with Discord’s safety settings, clear rules and moderators who can review context. No automated filter catches every case.