Which Discord permissions should I give OriusBot so every protection works?

PermissionsProtectionTroubleshooting

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

ProtectionPermissionWhat it is for
Anti-raid and anti-nukeView Audit LogWithout it, anti-nuke and the watchtower see no action at all.
Manage RolesCut an attacker’s rights.
Kick MembersKick raiders.
Ban MembersBan an attacker.
Manage ServerPause invites.
Manage ChannelsRecreate or lock channels.
Manage WebhooksDelete a malicious webhook.
CaptchaManage RolesCreate, give and remove the “Unverified” role; the bot’s role must be above it.
HoneypotManage ChannelsCreate the trap channel.
Ban / Kick / Timeout MembersApply the chosen response.
Create InviteAttach the return invite to the direct message.
SecurityManage 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: Protection

Last checked: 13 November 2026.