Who can affect whom
Members can kick, ban, or change nicknames only for members whose highest role is lower than their own. Equal and higher targets remain outside that boundary.
DISCORD ROLE HIERARCHY GUIDE
Put authority in the right order—and know what order cannot fix.
Discord role order controls who can manage whom, which roles an app can edit, and how members appear. It does not decide every permission conflict. Use this guide to audit the management boundary without confusing rank with effective channel access.
✓Official Discord behavior✓Six-step manual review✓No universal role template
THE TWO SYSTEMS
Role order and permission resolution answer different questions
Discord calls both concepts a hierarchy, but treating them as one is a common source of mistakes. Start by deciding whether you are debugging a management action or a member's access to a channel.
Which roles can be managed
Manage Roles applies below the manager's highest role. Bots follow the same lower-role boundary when assigning, editing, deleting, or sorting roles.
Which role overwrite wins
Channel overwrite collisions are calculated from combined deny and allow sets. A higher role does not automatically defeat a lower role's channel setting.
REFERENCE
What changes when a role moves
| Question | Does role order matter? | Rule to use |
|---|---|---|
| Can this moderator kick that member? | Yes | The target's highest role must be lower than the moderator's highest role. |
| Can this bot assign or edit that role? | Yes | The target role must be below the bot's highest role, and the bot cannot grant permissions it does not have. |
| Can this role edit an equal role? | Yes | No. Manage Roles does not reach roles at the same position or above. |
| Which color appears for a member? | Yes | Discord displays the color of the member's highest colored role. |
| Can a member see or send in a channel? | Usually no | Resolve guild permissions and channel overwrites; role position is not the conflict tiebreaker. |
These mechanics come from Discord's current permissions reference and Roles and Permissions guide. Discord may add permission flags over time, so audit the current configuration rather than relying on an old screenshot or copied role template.
SIX-STEP REVIEW
Audit the hierarchy from authority down
List every role from highest to @everyone
Record the role name, whether Discord marks it as managed by an integration, and its server-wide permissions. Treat decorative roles as part of the same hierarchy even when they grant no authority.
Identify Administrator before anything else
Administrator grants every permission and bypasses channel overwrites. Confirm why each Administrator role exists and manually review who holds it; a role-only audit cannot prove the assignments are appropriate.
Map each management boundary
For every role with Manage Roles or moderation powers, note its highest reachable target. A member can only affect members below their own highest role, and Manage Roles can only edit roles below that boundary.
Check each app and bot role
Place an app's highest managed role above every role it is expected to assign or edit. Keep it below human authority it should never manage, and verify that the app has only the permissions its job requires.
Separate order from channel access
Do not assume the higher channel overwrite wins. Discord combines role overwrites by deny and allow sets; an allow from one role can win over a deny from another regardless of which role appears higher.
Preview representative perspectives
Use Discord's View Server As Role feature for public, member, moderator, and specialist roles. Then separately test member-specific exceptions and multi-role combinations that a single-role preview or automated role perspective may not capture.
COMMON FAILURE MODES
Three hierarchy bugs that look like permission bugs
The app has Manage Roles but still fails
The permission flag is necessary, but hierarchy still blocks targets at or above the app's highest role. Moving the target down or the app role up changes that boundary.
A cosmetic badge becomes a shield
A high decorative role may unexpectedly place its members above moderators. Review every role's position, not only roles that contain permission flags.
Channel testing gives a false clean result
Administrator bypasses channel overwrites. Test ordinary member and moderator perspectives rather than using an administrator account as proof of effective access.
PRODUCT BOUNDARY
DisplayState can map configuration, not organizational intent
DisplayState reads supported role positions, permission values, managed-role markers, and role-by-channel perspectives. It can surface Administrator, management grants, hierarchy constraints, and evidence it could not resolve.
It does not read message content, decide which people deserve authority, or inventory member assignments. Role and channel recommendations are advisory in the current product; DisplayState does not silently reorder or mass-edit them.
Continue with the channel permissions resolution guide, review the @everyone baseline, or use the broader server audit checklist.
STRAIGHT ANSWERS
Frequently asked questions
Does the highest Discord role grant all permissions below it?
No. Role position sets management and moderation boundaries, but permissions still come from the permission flags on @everyone and the member's assigned roles. Only the Administrator permission grants all permissions and bypasses channel restrictions.
Does a higher role overwrite beat a lower role overwrite?
No. Discord does not use role position to resolve channel overwrite conflicts. It combines all role denies, then all role allows, so an allow on one assigned role can override a deny on another assigned role regardless of their order.
Why can a bot have Manage Roles but still fail to assign a role?
A bot can only assign or edit roles below its own highest role. It also cannot grant permissions it does not possess. Move the bot role above the intended target role while preserving the human authority boundary.
Can DisplayState tell which members hold a powerful role?
No. DisplayState's current configuration audit evaluates role permissions, ordering, managed-role state, and supported role-by-channel perspectives. It does not inventory members or certify that role assignments are appropriate.
FREE DURING BETA
See the hierarchy as configuration evidence.
Run a private, read-only-first Discord audit and review role ordering, powerful grants, and supported channel perspectives free during beta.
Audit my Discord server