How to set up GuildPilot AutoMod protection

GuildPilot AutoMod combines Discord-native spam, mention and word rules with deterministic invite and high-risk-link checks. The guided page lets you select protections, review exceptions and activate the resulting rules deliberately.

AutoMod protectionIllustration

Before you start

You need dashboard access and an active GuildPilot bot with permission to manage Discord AutoMod rules. Invite and link protection additionally require Message Content in GuildPilot and for the active bot in the Discord Developer Portal.

Configure protection

1. Open AutoMod

Choose your server, then select Safety → AutoMod. Read any synchronization, intent or custom-bot notice before changing protection.

2. Choose protection

Configure Spam protection, Maximum mentions in one message, Blocked words and phrases, Always block these domains and the invite controls that match your community rules.

3. Add narrow exceptions

Use Allowed exceptions, Trusted domains, approved invite codes, Exempt roles and Exempt channels only for known cases. Do not exempt broad staff or public areas without reviewing the impact.

4. Review and activate

Check Review and activate, turn on GuildPilot AutoMod, then choose Activate protection or Apply protection changes. GuildPilot will not replace a conflicting Discord rule it does not manage.

Recommended configuration

Start with Discord-native spam protection and a reasonable mention limit. Add blocked terms and domains from observed server needs, then use the smallest possible exception list.

Test the setup

1. Use a non-staff test account in a test channel that is not exempt. Trigger one safe test condition, such as exceeding the configured mention limit with consenting test accounts, and confirm Discord blocks the message. Remove the test content and review the configured AutoMod log destination if enabled.

What a successful setup looks like

The dashboard reports protection as active, Discord contains the managed rules, ordinary messages still work, and only the configured conditions are blocked.

Common problems

Discord reports a rule conflict

Cause: A Discord rule of the same managed type already exists outside GuildPilot.

Fix: Decide which tool should own that protection. Disable the conflicting Discord rule or continue managing it directly there.

Invite or link protection does not activate

Cause: Message Content is unavailable for GuildPilot or the active bot.

Fix: Enable it in both GuildPilot server settings and the Discord Developer Portal, then apply the protection again.