Which Discord permissions should I give OriusBot so every protection works?
A protection that “doesn’t work” almost always comes from a missing permission or a bot role placed too low. Here is what each protection requires.
The permissions, protection by protection
| Protection | Permission | What it is for |
|---|---|---|
| Anti-raid and anti-nuke | View Audit Log | Without it, anti-nuke and the watchtower see no action at all. |
| Manage Roles | Cut an attacker’s rights. | |
| Kick Members | Kick raiders. | |
| Ban Members | Ban an attacker. | |
| Manage Server | Pause invites. | |
| Manage Channels | Recreate or lock channels. | |
| Manage Webhooks | Delete a malicious webhook. | |
| Captcha | Manage Roles | Create, give and remove the “Unverified” role; the bot’s role must be above it. |
| Honeypot | Manage Channels | Create the trap channel. |
| Ban / Kick / Timeout Members | Apply the chosen response. | |
| Create Invite | Attach the return invite to the direct message. | |
| Security | Manage Server | “Pause DMs during an image raid”. |
| Manage Messages and Manage Webhooks | “Hold files while they are being analysed”. |
The role hierarchy trap
Even with the permission, Discord forbids a bot from acting on a member whose role is above its own. Place OriusBot’s role at the very top (just below the owner or the roles you never want to see sanctioned). See the diagnostic article.
The easiest way
Re-invite the bot with the official invite link from the website, which already asks for these permissions, then check the banner “What stops OriusBot from protecting this server”.
Still stuck?
Contact support with the title of this article, the step where you are stuck and what you see on screen.
Contact support More articles: ProtectionLast checked: 13 November 2026.