Required permissions
A reference for what the bot needs at the Discord level to function correctly.
#Bot permissions (granted on invite)
These are requested at invite time — re-invite the bot if any are missing:
| Permission | Used for |
|---|---|
| View Channels | Reading messages in moderated channels |
| Read Message History | Pulling context for judgment, resolving message links |
| Send Messages | Posting log embeds, public warnings, mention-scan replies |
| Embed Links | All log entries and replies are embeds |
| Manage Messages | Deleting flagged messages |
| Moderate Members | Applying timeouts |
| Kick Members | Action: kick |
| Ban Members | Action: ban |
If the bot was invited without one of these, slash commands will still work, but moderation actions in that category will fail with Missing Permissions in the log channel.
#Role position
Equally important and easy to miss:
The bot's role must be above any role of any member it should be able to moderate.
Discord enforces this at the platform level — no permission grant overrides it. Drag the Blify Mod role up in Server Settings → Roles. Most setups put it at the very top, just below any human-admin roles.
The bot can never act against:
- The server owner (Discord limitation)
- A member whose highest role is at or above the bot's role
#Channel-specific overrides
If a channel has overrides that deny the bot any of the above permissions, the bot will skip that channel even if you've added it via /setmodchannels. Check Channel → Edit Channel → Permissions → Blify Mod if a specific channel isn't being moderated.
#User-side permissions
The slash commands have their own permission requirements:
| Command | Permission required |
|---|---|
All /set*, /enable, /disable, /dryrun, /modconfig |
Manage Server |
/immunerole, /immuneuser |
Manage Server |
/pro claim, /pro unclaim |
Manage Server |
/pro status, /pro info |
None |
/modlogs |
Moderate Members |
| Reverse button on log embeds | Moderate Members |
/vote, /credits, /credits-toggle, /redeem-pro-tier |
None (per-user) |
/blacklist, /unblacklist |
Bot owner only |
These are enforced both server-side (Discord won't even show the command to users without the permission, by default) and re-checked in the bot itself.
#Privileged intents
Blify Mod uses these Discord gateway intents:
- Guilds — basic server data
- Guild Messages — receiving messages
- Message Content — required to read messages for moderation
- Guild Members — fetching offender info, role-checks for immunity
- AutoModeration Execution — to deduplicate actions when Discord's native AutoMod has already handled a message
These are configured on the Discord developer portal side and don't require any setup from server admins.