Safety & AutomationPro planAutoMod
A controlled implementation runbook for AutoMod, suitable for teams and multiple servers.
What does AutoMod?
Implement AutoMod with clear ownership, least privilege, test evidence, and verified handover.. This guide covers readiness, configuration, validation, launch, and ongoing ownership.
What you will achieve
AutoMod is configured for the selected server
Channels, roles, and exceptions are deliberately scoped
The setup is tested and has a clear owner
Before you start
Access & permissions
AutoMod setup
Complete the steps in order. Your progress is stored only in this browser.
Verify server and readiness
Select the correct server, open AutoMod, and resolve every blocking setup check.
Configure the essentials
Choose the behaviour, limits, channels, roles, and exceptions that fit your community.
Apply least privilege
Grant only the required access and make sure HubNova can reach every configured resource.
Preview and test safely
Use a restricted channel or test role and verify the member and administrator experience.
Launch and review
Enable the module, inspect the first live results, and schedule a periodic configuration review.
Troubleshooting
01The module is disabled again after refresh+
Check required fields, plan access, and blocking Setup Health findings before enabling it again.
02A channel or role is missing+
Refresh Discord resources and verify the bot role, selected server, and channel access.
03The test works but members see nothing+
Review channel overrides, member roles, visibility, and test-only targeting.
Best practices
- Verify the selected server before every change.
- Start in a restricted test channel or with a test role.
- Assign a module owner and periodically review access, exceptions, and results.
- Use /help or /commands for the current server-specific command list.
Continue learning
Ready to implement: AutoMod?
Open the correct organisation workspace, assign an owner, and complete the runbook.