Discord Roles and Permissions: How to Build a Safe Role Hierarchy

Discord roles follow a top-down list. According to Discord, members can only affect users whose roles are lower than their own highest role, and they cannot ban, kick or change the nickname of someone with an equal or higher role, even if they have those permissions.

Members with the Manage Roles permission can create and edit roles below their own, but they can only hand out permissions they have themselves, and they cannot change roles at or above their own position. New roles are placed at the bottom of the list, just above @everyone, and use @everyone as their template. You reorder roles by dragging them in Server Settings, Roles.

Permissions from several roles add up: a member gets every permission that any of their roles grants. Removing one role therefore does not take away a permission that another of their roles also grants. The server owner does not need any role and always has access to everything.

Role permissions set in Server Settings apply across the whole server. Channel permissions change that for a single channel, and Discord states that channel permissions override server permissions. Categories can carry permissions too: channels that are synced with their category update when the category changes, while unsynced channels keep their own settings.

When several overrides apply, Discord resolves them in a fixed order: the @everyone override for the channel first (deny, then allow), then the overrides for the member's roles (all denies, then all allows), then overrides for the individual member (deny, then allow). This has two practical consequences. If one of a member's roles is denied a permission in a channel and another of their roles is allowed it, the allow wins. And an override for a specific member beats both.

Denying View Channel to a role on a channel implicitly denies the other permissions on that channel, which is how private staff channels work: hide the channel from @everyone and allow it for the staff role.

A common pattern: a growing server gets too busy for one person, so the owner gives a few active members Administrator and asks them to help. Soon channels get deleted during a “clean-up”, the server icon changes, or the verification channel ends up in a category new members cannot see.

This happens because Administrator is not a helper permission. Discord describes it as the most powerful role permission: it grants all permissions and bypasses all channel restrictions. Someone who only needs to delete spam gets the ability to change everything.

What helps is giving each job its own role with only the permissions that job needs, and keeping Administrator for co-owners you trust with every setting. To check your server now, open Server Settings, Roles, and look at each role's Advanced Permissions for the Administrator toggle. BuildMyDiscord's AI Editor includes a server audit that flags @everyone having Administrator and warns when more than three roles have it.

Admin: very few people, ideally co-owners. Only this role, if any, gets Administrator, Manage Server and Manage Roles.

Moderator: Manage Messages (delete other members' messages), Time Out Members, Kick Members and, if you want moderators to ban, Ban Members. Leave Manage Channels, Manage Server, Manage Roles and Administrator off. A timeout stops a member from sending or reacting to messages and from joining voice channels, and the reason is recorded in the audit log, so a separate “Muted” role is usually unnecessary.

Helper: access to the staff channel so they can flag problems, with no moderation permissions.

Member or Verified: the normal permissions for chatting. Interest or notification roles can sit here too; they usually need no permissions at all.

Bot roles: a bot can only assign roles below its own highest role and can only grant permissions it has. Place each bot's role above the roles it hands out, and give it only the permissions its features need. For moderation workflows, see the moderation guide.

Self-assigned roles (through reaction-role or button panels) let members pick interests or notification settings without staff involvement. Level roles reward activity by handing out roles as members reach set levels.

Both depend on the bot that assigns the roles. If a role is not handed out, check that the bot's role sits above it and that the bot has Manage Roles.

A member cannot do something they should be able to do. Check the channel's overrides for @everyone, for each of their roles and for them personally, in the order described above. View Server As Role, available to owners and Administrators, shows which channels a role can see.

A moderator cannot act on another member. The target's highest role is probably equal to or above the moderator's highest role.

Something changed and nobody knows who did it. Members with View Audit Log can see recent changes in the audit log; Discord keeps entries for 45 days. For wider protection against compromised accounts and raids, see the server security guide.