Skip to main content

Role Hierarchy

Discord has built-in security rules about which roles can manage other roles. Understanding this is essential for RoleLogic to work correctly.

The Basic Rule​

A bot can only manage roles that are positioned BELOW its own highest role in the server's role list.

This is a Discord security feature, not a RoleLogic limitation. It prevents bots from giving themselves (or others) higher permissions than intended.

How Role Hierarchy Works in Discord​

Every Discord server has a role list that looks something like this (from top to bottom):

Server Owner (implicit)
    ↓
Admin
    ↓
Moderator
    ↓
RoleLogic ← Bot's role
    ↓
VIP
    ↓
Member
    ↓
Unverified
    ↓
@everyone

In this example:

  • RoleLogic CAN manage: VIP, Member, Unverified, @everyone
  • RoleLogic CANNOT manage: Admin, Moderator, or its own role

Setting Up RoleLogic's Role Position​

Step 1: Open Server Settings​

  1. Right-click your server name or click the dropdown arrow
  2. Select "Server Settings"

Step 2: Go to Roles​

  1. Click "Roles" in the left sidebar
  2. You'll see all roles listed from highest to lowest

Step 3: Find the RoleLogic Role​

When you invited RoleLogic, Discord created a role called "RoleLogic" (or similar). Find it in the list.

Step 4: Drag It Up​

Click and drag the RoleLogic role above all the roles you want it to manage.

For example, if you want RoleLogic to manage VIP, Member, and Unverified:

Admin
Moderator
RoleLogic ← Drag it here
VIP
Member
Unverified
@everyone

Step 5: Save​

Discord auto-saves, but make sure the new position is reflected.

tip

You don't need to put RoleLogic at the very top. Just above the roles it needs to manage is sufficient. Keeping it below Admin/Mod roles is a good security practice.

What Happens If the Hierarchy Is Wrong?​

If RoleLogic tries to manage a role that's above its position:

  1. The action fails for that specific role
  2. Other roles in the same action may still work (if they're below RoleLogic)
  3. An error appears in your dashboard and logs
  4. The rule continues trying to process other members

Error Message​

When you try to set up a rule with a role RoleLogic can't manage, you may see warnings like:

  • "Cannot manage this role due to hierarchy"
  • "Role is above bot's highest role"
  • "Missing permissions for this role"

The "Manage Roles" Permission​

In addition to hierarchy, RoleLogic needs the "Manage Roles" permission on your server.

Checking the Permission​

  1. Go to Server Settings → Roles
  2. Click the RoleLogic role
  3. Scroll to Permissions
  4. Ensure "Manage Roles" is enabled

This permission was requested when you invited RoleLogic, so it should already be enabled. But if you modified the role's permissions, double-check this.

Common Scenarios​

Scenario 1: VIP System​

You want RoleLogic to add/remove VIP roles.

Setup:

Admin
Moderator
RoleLogic
VIP Gold
VIP Silver
VIP Bronze
Member
@everyone

Result: RoleLogic can manage all VIP tiers and Member.

Scenario 2: Full Server Automation​

You want RoleLogic to manage almost every role.

Setup:

Server Owner
RoleLogic ← Very high position
Admin
Moderator
VIP
Member
@everyone

Result: RoleLogic can manage Admin, Moderator, VIP, Member.

caution

Be careful placing RoleLogic this high. While it won't do anything malicious, a misconfigured rule could affect staff roles. Always test thoroughly!

Scenario 3: Limited Automation​

You only want RoleLogic to manage new member roles, not staff or VIP.

Setup:

Admin
Moderator
VIP
RoleLogic ← Lower position
Member
Unverified
Guest
@everyone

Result: RoleLogic can only manage Member, Unverified, and Guest. Staff and VIP are protected.

The Dashboard Warning​

If RoleLogic detects that its role is positioned incorrectly, you'll see a warning in the dashboard:

"Let's Get Your Roles Ready"

This guide walks you through:

  1. Ensuring "Manage Roles" permission is granted
  2. Moving the bot's role above managed roles
  3. Refreshing to confirm the fix

Click "Refresh and Continue" after adjusting your server settings.

Tips for Role Hierarchy​

Keep RoleLogic Below Admin/Mod​

There's rarely a need for RoleLogic to manage staff roles. Keep it below your admin and moderator roles for security.

Plan Ahead​

Before creating rules, sketch out which roles need automation. Then position RoleLogic appropriately.

Be Consistent​

If you add new roles later, remember to check if RoleLogic needs to manage them. Adjust the hierarchy if necessary.

Don't Panic​

If something isn't working, hierarchy is often the cause. It's an easy fix—just drag the role up in server settings.

Troubleshooting​

"Cannot manage this role"​

The target role is above RoleLogic's role. Drag RoleLogic higher in your server's role settings.

Rules work for some roles but not others​

Check the hierarchy for each role in your rule. Some might be manageable while others aren't.

Nothing is working​

  1. Confirm "Manage Roles" permission is enabled
  2. Confirm RoleLogic's role is above the target roles
  3. Check that rules are enabled in the dashboard
  4. Verify the condition actually matches

Next Steps​