Discord Bot Not Giving Roles? How to Fix It

The bot is online, the settings are in place, and still nobody gets the role. This is almost always a permissions problem, not a bot problem. Work through this checklist from top to bottom; the most common causes come first.

Quick answer: In most cases the bot's role sits below the role it should assign in the role list. Drag the bot's role to the top in the server settings under Roles (just under your own admin role) and check that it has the Manage Roles permission.

1. The role order

Discord only lets a bot assign or remove roles that sit below its own highest role. This is by far the most common cause.

1. Open the server settings and go to Roles.
2. Find the bot's role. For Kage it is called "Kage".
3. Drag it above all roles the bot should assign.

Even the "Administrator" permission does not change this. Role order applies to everyone except the server owner.

2. The "Manage Roles" permission

The bot needs the Manage Roles permission, either in its role or through the Administrator permission. Check this in the bot's role settings.

3. The role itself

• Managed roles cannot be assigned. Roles created by an integration, such as another bot's role or the booster role, cannot be given out by hand by any bot or person.
• @everyone cannot be assigned, because everyone already has it.
• Deleted roles: If the role was deleted and recreated, it is a different role. Pick it again in the dashboard.

4. The module

The role is only assigned if the relevant module is switched on and belongs to your plan. Check the Auto-role active, Reaction roles active or Role Panels enabled switches and the "Related Kage features" box in the matching articles.

5. Specifics for each method

• Auto-Roles: Only act on join, not retroactively. Anyone who joined earlier gets no role. Bots only get them if the option for bot accounts is on.
• Reaction roles: Only work on panel messages that Kage posted, and only with standard emojis. A panel message deleted in Discord does nothing.
• Role Panels: Check the rules. "Only one role at a time" removes other panel roles, the maximum blocks further roles, and a minimum level refuses the role if the level is missing. After changes, republish the message with Update panel.
• Temporary roles: The role disappears on purpose once the duration is over.
• Verification: The role is only assigned after the click on the verification button.

6. The role is there but the member cannot see the channel

Then it is usually not about assigning but about channel permissions. Channel and category permissions can deny or allow a role access and override the role's own permissions. In the channel settings under Permissions, check what is set for the role.

7. Another bot takes the role away again

If several bots manage roles (for example a second bot with auto-roles or level roles), they can overwrite each other. Switch one of them off as a test.

8. Evidence in the audit log

Discord's audit log in the server settings shows when and by whom a role was assigned or removed. That tells you whether the bot tried or whether someone else intervened. For auto-roles, Kage's Monitoring module warns you if a role sits above the bot's role or no longer exists.

Quick test

Assign the role by hand once in Discord. If that works, the role is fine, and the issue is the bot's role, the module or the settings. If it does not even work by hand, something is wrong with the role itself, for example because it is managed.

FAQ

I gave the bot Administrator and it still does not work. Why?

Role order applies to administrators too. The bot's role must sit above the target role.

Does the bot's role have to be at the very top?

No, it only needs to sit above all roles the bot assigns or removes. It should stay below your own admin role, though.

Why does it work for some members but not others?

Either those members have higher roles than the bot, or they already have the role. For auto-roles the time of joining also matters.