Guide: Automod setup

Build a sensible first automod ruleset: block slurs/spam, warn repeat offenders, and log actions for staff.

Time: about 15 minutes
Requires: Manage Server, Moderation roles defined

Before you start#

1. Invite AIO with permissions including Manage Messages.
2. Create #mod-log for Logging (optional but recommended).
3. Decide staff roles that should bypass strict filters.

Step 1 — Open automod#

Go to Dashboard → Servers → {Guild} → Automod and enable the feature.

Step 2 — Add a word filter rule#

1. Create a new rule (for example “Blocked words”).
2. Add terms your server prohibits—start with obvious slurs and scams.
3. Action: Delete message and optionally Warn the user.
4. Exclude staff channels or roles if the dashboard supports exemptions.

On Free, you can run up to 5 active rules and 50 word entries total across filters—prioritize high-impact lists. Pro adds regex, honeypot, and kick/ban actions. See Automod.

Step 3 — Add a spam or link rule (optional)#

If link spam is a problem:

1. Create a rule limiting repeated links or invites from young members.
2. Action: delete + mute for a short duration via automod/moderation integration.

Tune thresholds so normal conversation is not caught.

Step 4 — Connect logging#

1. Open Dashboard → Servers → {Guild} → Logging.
2. Enable message delete and moderation-related events to #mod-log.
3. Staff can correlate automod warnings with Moderation cases.

Step 5 — Test safely#

In a private staff channel:

1. Post a harmless test string you added to the block list.
2. Confirm the message is removed and the warn fires if configured.
3. Remove the test word from the rule afterward.

Never test with real slurs in public channels.

Step 6 — Document for members#

Add a #rules note that automated filters are active and appeals go to staff via Tickets or your usual mod channel.

Related#

• Automod
• Guide: Ticket panel
• Troubleshooting
• Commands for manual /warn and /mute