AutoMod
Explainable rules, exemptions, simulation, and review.
Start here
Create a rule safely, test it, and pause enforcement
PulseOne → Dashboard → select your server → Modules → AutoMod
Choose the server → Modules → AutoMod. Check the Runtime on/Runtime paused badge at the top of the console.
Open Rules. Under Custom rule set choose Rule type and press Add rule, then fill in the displayed rule fields and enable the configured rule.
Open Actions & exemptions. Choose Dry run under Evaluation mode before experimenting, review Severity action ladders, and add exempt User IDs, Role IDs or Channel IDs as needed.
Scroll to the bottom and press Save immutable policy. After a policy version is active, use Enable runtime to start evaluating messages.
Open Simulator, enter a synthetic Message ID, Author ID, Channel ID and example Message content, then press Run dry-run simulation. This runs against the saved active policy, not unsaved edits.
Open Incidents to inspect why a rule matched. When ready, change the policy to Enforce, review actions, and save the updated policy.
Practical example
To stop AutoMod from giving out new timeouts, either press Pause runtime, or switch Actions & exemptions → Evaluation mode to Dry run and save the immutable policy. Dry run records decisions without applying Discord actions.
Before you begin
- Enable first: moderation.
- Discord bot permissions for the operational slice: ManageGuild, ModerateMembers, ManageMessages.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Enable Moderation first, then open AutoMod. Decide whether the rule requires message content and the relevant Discord intent.
Configure
Configure a narrow rule and an exemption for an approved channel or staff role. Run the simulator on both matching and nonmatching examples.
Test and verify
Review dry-run incidents before activating a destructive action; inspect why a match happened and whether an incident was delivered.
Features explained
What each feature does and what to check before publishing or installing the result.
Explainable custom message filters with bounded durable state
Custom filters explain why content was flagged; keep patterns narrow enough to avoid legitimate chat.
Dry-run review before enforcement
Dry-run checks rules without deleting members' messages. Use it to evaluate exceptions and false positives.
Delete, warn, timeout, and privacy-minimal incident outcomes
Choose delete, warn or timeout only after simulation. Incident records preserve bounded evidence rather than entire chats.
If it still does not work
- The page must show Runtime paused after Pause runtime. If it still says Runtime on, confirm the change completed and refresh.
- Do not confuse an unsaved draft with the active version: Simulator only tests the active policy. Saving creates an immutable new version.
- If members are still timed out with AutoMod paused, check Security protections, Moderation and Discord’s Audit Log for the action’s actor.
Troubleshooting and safety checks
- Unexpected deletion? Disable the specific rule, inspect its match/exemptions and reproduce it in dry-run before reenabling.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.