Skip to main content

​
Overview

For Flare to keep your server safe from raids, nukes, and rule-breakers, it must have the appropriate Discord permissions. If Flare lacks permissions, its core features (like AntiNuke, AutoMod, and Moderation) will fail to execute.

​
The Golden Rule: Role Hierarchy

CRITICAL: Flare cannot punish users who have a role higher than its own.You must drag the Flare role to the very top of your server’s role list in Discord settings (Server Settings > Roles). If Flare’s role is below a rogue admin, AntiNuke will fail to ban them.
When you invite Flare, it requests the Administrator permission by default.

​
Why Administrator?

Flare handles everything from channel deletion (AntiNuke) to role assignment (Welcome) and message filtering (AutoMod). The Administrator permission guarantees that Flare can execute these actions flawlessly without you manually hunting down specific channel overwrites. If you are uncomfortable granting Administrator, you must manually grant the following permissions to Flare’s role:
  • Ban Members
  • Kick Members
  • Moderate Members (For timeouts/mutes)
  • Manage Messages (For AutoMod and purge commands)
  • Manage Roles (For assigning mute/jail roles)
  • Manage Channels
  • Move Members
  • View Audit Log
  • Manage Webhooks

​
Troubleshooting Permissions

If a command fails or a module isn’t triggering, it is almost always a permission issue.
1

Check the Role Hierarchy

Ensure Flare’s role is above the target user’s role.
2

Check Channel Overrides

If Flare can’t delete messages in #general, check if #general has channel-specific permissions denying Manage Messages for the Flare role.
3

Verify 2FA Requirement

If your server requires Two-Factor Authentication for moderation, ensure the server owner has 2FA enabled, otherwise Flare’s admin actions might be blocked by Discord.