When you assign roles in a Discord server, the order of those roles determines what permissions each role can grant or override. Many server administrators notice that a role with Administrator permission cannot manage a role placed above it in the list. This happens because Discord enforces a strict hierarchy based on role position, not just permission settings. Understanding this hierarchy is essential for building a server where moderators, admins, and bots work correctly without unexpected permission errors. This article explains how the role hierarchy works, why the order matters, and how to configure roles to avoid conflicts.
Key Takeaways: Discord Role Hierarchy
- Role position in Server Settings > Roles: Roles higher in the list can manage roles below them but not above them.
- Permissions vs hierarchy: Even with Administrator permission, a role cannot edit or delete a role placed above it in the list.
- Drag roles to reorder: To change hierarchy, drag roles up or down in the Roles list under Server Settings.
How Discord Role Hierarchy Works
Discord uses a linear hierarchy system where each role has a position number. The role at the top of the list has the highest position, and the role at the bottom has the lowest. A role can only manage roles that appear below it in the list. This applies to all actions that involve other roles: granting roles to members, editing role permissions, deleting roles, and assigning role colors.
The hierarchy does not consider the permission values of roles. A role with no special permissions placed above a role with Administrator permission can still be managed by the lower role. However, the lower role cannot manage the higher role because of the position difference. This design prevents a situation where a low-level moderator could accidentally or intentionally take control of an admin role.
How Position Numbers Are Assigned
When you create a new role, Discord places it at the bottom of the list by default. The position number is determined by the order in the list. You can change the position by dragging the role up or down in the Server Settings > Roles panel. The highest position is 1, and the lowest is the total number of roles in the server. The @everyone role always sits at the bottom and cannot be moved.
What the Hierarchy Controls
The hierarchy affects these specific actions:
- Assigning or removing roles from members: A role can only assign roles that are below it in the hierarchy. It cannot assign roles that are above it.
- Editing role permissions: A role can change the permissions of any role below it but not above it.
- Deleting roles: A role can delete roles that are below it in the list.
- Color display: When a member has multiple roles, the color of the highest role in the hierarchy is shown in the member list, unless the member has a role with a specific color set.
Steps to Configure Role Order Correctly
To avoid permission conflicts and ensure your staff roles work as expected, follow these steps to arrange roles in the correct order.
- Open Server Settings
Open your Discord server. Click the server name at the top left of the channel list. Select Server Settings from the dropdown menu. - Navigate to Roles
In the left sidebar, click Roles. You will see a list of all roles in your server, sorted by position from top to bottom. - Identify the top role
The role at the very top is the highest in the hierarchy. This role can manage all other roles. Typically, this should be the server owner or an administrator role. - Drag roles to reorder
Click and hold the six-dot icon to the left of a role name. Drag the role up or down to its desired position. Release the mouse to drop it. Repeat for each role that needs a new position. - Place admin roles above moderator roles
Roles that need to manage other roles must be placed above the roles they manage. For example, place Administrator above Moderator, and place Moderator above Member. - Place bot roles carefully
If you use bots that assign roles, place the bot role above the roles it needs to assign. The bot role must be higher than the target role in the hierarchy. - Save changes
Discord saves changes immediately as you drag roles. No save button is needed. Close the Settings panel when done.
Common Mistakes When Setting Up Role Hierarchy
Bot Cannot Assign Roles to Members
If your bot fails to assign a role to a member, the most common cause is that the bot role is placed below the target role in the hierarchy. For example, if your bot role is at position 5 and the Member role is at position 3, the bot cannot assign the Member role. Drag the bot role above the target role to fix this.
Moderator Can Edit Admin Role Permissions
If a moderator role is placed above an admin role in the list, the moderator can change the admin role permissions. This is a security risk. Ensure that admin roles are always placed above moderator roles. The highest role should be reserved for server owners and trusted administrators.
Role Color Not Showing for Members
When a member has multiple roles, the color of the highest role in the hierarchy appears in the member list. If you want a specific role color to show, move that role above other colored roles. For example, if you want the VIP role color to display, drag VIP above the Member role.
@everyone Role Cannot Be Moved
The @everyone role is always at the bottom of the hierarchy and cannot be moved. You cannot assign @everyone to a higher position. This is by design to prevent accidental permission changes that affect all members.
| Item | Role at Position 1 (Highest) | Role at Position 10 (Lowest) |
|---|---|---|
| Can manage roles below | Yes, all roles below | Yes, roles below position 10 |
| Can manage roles above | No roles above | No, cannot manage roles above position 10 |
| Can assign roles to members | Any role below | Only roles below position 10 |
| Color shown in member list | Color of this role if set | Color of highest role with a color set |
Role hierarchy is a fundamental part of Discord server management. By placing roles in the correct order, you ensure that staff members and bots can perform their tasks without permission errors. The key rule is simple: a role can only manage roles that appear below it in the list. Always arrange roles with the most powerful at the top and the least powerful at the bottom. For advanced setups, consider creating a dedicated admin role with no color and placing it at the top to manage all other roles, while keeping a separate role for display colors.