Permissions
Modulus uses Discord permissions and role hierarchy to protect your server. This page explains what the bot needs and what staff need.
Dashboard Access
- You must be the server owner or have the Manage Guild permission to edit settings.
- If dashboard access roles are configured, those roles can edit without Manage Guild.
Bot Permissions
Grant only the permissions you plan to use. The list below is the typical full set for moderation features:
- View Channels
- Send Messages
- Embed Links
- Read Message History
- Add Reactions
- Manage Messages (purge, automod deletes)
- Moderate Members (timeouts)
- Kick Members
- Ban Members
- Manage Roles (quarantine, role connections, reaction roles, auto roles)
- Manage Channels (lockdown, slowmode, join gate)
- View Audit Log (anti-nuke and raid analysis)
Notes
- If the bot cannot manage a role or member, move the bot role above that role.
- For reaction roles, the bot must be able to add reactions and manage the target role.
Staff Permissions
Moderation commands require the matching Discord permission. Examples:
- Ban: Ban Members
- Kick: Kick Members
- Mute (timeout): Moderate Members
- Purge: Manage Messages
- Lockdown or slowmode: Manage Channels
- Voice mute: Mute Members or Manage Channels (depending on server setup)
Modulus also checks that server setup is complete. If you see a setup error, finish Roles and Logging in the dashboard.