Which rule wins when several permissions contradict each other (block, allow, group, Moderator role)?

PermissionsCommandsPriorities

When a member runs a command, OriusBot checks several things, in this order. The first one that applies decides.

StepQuestion askedResult
1Is the member a server administrator?Yes: access.
2Is one of their roles blocked on this command?Yes: denied, whatever else they have.
3Is one of their roles allowed on this command?Yes: access.
4Is one of their roles in a permission group that contains the command?Yes: access.
5Is the command public (no permission required)?Yes: access.
6Do they have a Moderator role and is the command a moderation command?Yes: access.
7Do they have the Discord permission the command requires?Yes: access. Otherwise: denied.

After access: the command’s state

Even when allowed, a member can still be stopped by the command’s state: disabled, channel not allowed, cooldown or usage limit. See the troubleshooting article.

An example The role @Host is allowed on /giveaway and the member also has the role @Newcomer, blocked on the same command: they are denied, because a block takes priority over an allow.
Administrators are never blocked by a role A block does not apply to an administrator (step 1). To restrict an account, don’t give it the Administrator permission.

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: Configuration

Last checked: 13 November 2026.