🛡️ Moderation Checklist

A complete moderation setup before you trust automation in a live Discord server

Moderation tools are only useful when permissions, hierarchy, logging and staff expectations agree. This checklist helps server owners validate the entire setup before relying on it during a real incident.

1. Put the Bozos role in the correct place

Bozos Forever needs to sit above the ordinary roles it may moderate. Administrator permission does not override Discord's role hierarchy. Leave owner or intentionally protected infrastructure roles above the bot if you do not want them managed.

2. Confirm the moderation commands your team needs

Test harmless staff workflows such as warnings and reviewing moderation history before testing destructive actions. Make sure your moderators know which commands are available and what each action records.

3. Enable AutoMod deliberately

Turn on invite, banned-word or spam protection because your server needs them, not simply because switches exist. Test one rule at a time in a staff channel and watch for false positives during normal conversation.

4. Decide where operational logs belong

Configure Bozos Audit destinations that your staff will actually read. Separate moderation events from noisier member, message, voice or server-change events when that improves clarity. Keep those channels restricted to appropriate staff.

5. Test against role hierarchy

Create or use a safe test role below Bozos and confirm the bot can perform the intended moderation action on a trusted test member. Then confirm it cannot manage intentionally protected roles above it. Both outcomes are useful.

6. Check channel overrides

A server-level permission can be overridden in a specific channel. If moderation-related responses or logging fail only in one area, inspect that channel or category before changing global permissions.

7. Keep human review in the loop

AutoMod should stop obvious abuse quickly, while staff handle context, appeals and unusual cases. Write server rules that explain what members should expect instead of letting automation become invisible policy.

Launch checklist

  • Bozos role is above manageable member roles.
  • Administrator permission is present.
  • Moderation commands respond for authorized staff.
  • AutoMod rules have been privately tested.
  • Bozos Audit destinations are valid and staff-only.
  • Staff know where to review moderation history.
  • Protected roles remain intentionally above the bot.
Moderation documentation →Role hierarchy explained →