Role Hierarchy Visualizer

What is the Discord Role Hierarchy Visualizer?

The Discord Role Hierarchy Visualizer helps you plan and verify your server's role structure by displaying roles in a clear top-to-bottom hierarchy with permission indicators and conflict warnings. In Discord, role position determines power: higher roles can manage lower roles but never equal or higher ones. Getting this hierarchy wrong leads to permission issues, moderation gaps, and security vulnerabilities.

This tool lets you add your server's roles, assign key permissions to each, and rearrange their order to see how the hierarchy affects what each role can do. It automatically flags common mistakes like moderator roles placed below the roles they need to manage, or dangerous permission combinations that could compromise server security.

Understanding role hierarchy is crucial for anyone administrating a Discord server. Even experienced administrators occasionally create permission conflicts when adding new roles. This visualizer makes those conflicts immediately visible before they cause problems in your live server.

How to Use This Tool

1. Add roles by typing a name, selecting a color, and clicking Add. Create roles in any order - you will arrange the hierarchy next.
2. Arrange roles by moving them up and down in the list. The top role has the highest authority, and each role below it has progressively less power. This mirrors exactly how Discord's role list works.
3. Click on any role to toggle key permissions (kick, ban, manage roles, manage channels, administrator, etc.) for that specific role.
4. Watch for warning indicators that appear when the tool detects potential hierarchy issues or dangerous permission configurations.
5. Review the complete hierarchy to ensure moderator roles are above the roles they need to manage, and bot roles have appropriate positioning.
6. Use this plan as a reference when configuring roles in your actual Discord server settings.

How Discord Role Hierarchy Works

• Roles are ranked by position: the higher a role appears in Server Settings, the more authority it has over roles below it.
• A role can only manage (assign, remove, edit) roles that are strictly below it in the hierarchy. It cannot touch equal or higher roles.
• Members with Kick/Ban permissions can only kick or ban members whose highest role is below the kicker's highest role.
• The server owner bypasses all hierarchy restrictions and can always manage any role or member regardless of position.
• Bots are subject to the same hierarchy rules. A bot can only assign roles below its own highest role, which is why bot roles need careful positioning.
• The default everyone role is always at the bottom and cannot be moved. It applies to all server members as a baseline.
• When multiple roles grant different permissions, the combined (union) of all role permissions applies to the member.

Tips for Role Hierarchy Design

• Place your bot roles above any roles they need to manage. If a moderation bot needs to timeout or role members, its role must be higher than those members' roles.
• Create a clear separation between staff roles and member roles. Staff roles (Admin, Moderator, Helper) should all be above any member-facing roles.
• Use separator roles (empty roles with no permissions) between staff and member sections for visual clarity in the role list.
• Avoid giving Manage Roles permission to roles that are not in senior staff positions. A role with Manage Roles can assign itself any role below it, effectively escalating its own privileges.
• Keep the Administrator permission on as few roles as possible, ideally only the server owner's personal role. Administrator bypasses all permission restrictions.
• Test your hierarchy by having a moderator try to kick a test account with various roles. This quickly reveals hierarchy gaps that the visualizer warns about.

Frequently Asked Questions

Why can my moderator not kick certain members?

The member's highest role is at or above the moderator's highest role in the hierarchy. Move the moderator role higher, or move the problematic member role lower. Remember that hierarchy is determined by the highest single role each person has, not their total number of roles.

Does role color affect hierarchy?

Role color has no effect on hierarchy or permissions. However, a member's displayed color comes from their highest colored role (not their highest role overall). So two roles at positions 5 and 3, where position 3 has a color, will use position 3's color for display.

What happens if two roles have the same permissions?

Permissions combine (OR logic) across all of a member's roles. If any role grants a permission, the member has that permission. Role position only matters for hierarchy-dependent actions like kicking, banning, and role management - not for permission granting.

How should I position bot roles?

Place bot roles above any roles the bot needs to manage. A moderation bot should be above all member and moderator roles it might timeout or role-manage. Music bots only need to be above roles that use music commands. Integration bots need minimal hierarchy positioning since they primarily interact with channels, not roles.

Can I have more than one administrator role?

Technically yes, but it is not recommended. Multiple administrator roles increase your attack surface - if any account with Administrator is compromised, the attacker has full server control. Keep Administrator on one or two roles held only by the most trusted staff, and use granular permissions for everyone else.