Discord Role Hierarchy: Why Your Bot Can't Manage Some Roles
Published 22 Nov 2026
Also available in: Deutsch · Français · Português · Español
It's one of the most common support questions for any Discord bot: "I gave the bot Manage Roles, so why can't it give out this role?" or "Why won't it time out that member?" Nine times out of ten, the permission is fine. The problem is where the bot's role sits in your role list. Discord's role hierarchy is strict, and once you see how it works, these errors become a two-second fix.
The rule in one sentence
A bot (or person) can only manage roles below its own highest role, and can only moderate members whose highest role is below its own highest role.
That's it. A few corollaries follow:
- Roles at the same position or higher are off-limits, even with Manage Roles.
- When editing a role, a bot can't grant a permission it doesn't have itself.
- Nobody can act on the server owner.
- Administrator doesn't bypass this. An admin bot placed low in the list still can't manage roles above it.
Where the bot's role comes from
When you invite a bot, Discord creates a role named after it, managed by the integration. You can't assign that role to anyone else or delete it while the bot is in the server; it disappears if the bot leaves. What you can do is move it up or down like any other role.
The catch is that its position isn't always where you need it, and it often ends up underneath roles you create later, such as new reward or colour roles. Nothing looks broken in the settings; the bot just quietly fails when it tries to touch those roles.
Symptoms and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| A self-assign role button or menu works for some roles but not others | The failing roles are above the bot's role | Move the bot's role above them |
| Level-up reward roles aren't given | Reward roles sit above the bot | Move the bot's role above the reward roles |
| The bot can't time out, kick or ban certain members | Their highest role is at or above the bot's | Move the bot higher, or accept that it shouldn't moderate those members |
| The bot can't edit a role's settings | The role is above the bot, or the change grants a permission the bot lacks | Reorder, or give the bot that permission |
| Everything fails, even for low roles | The bot lacks Manage Roles (or the moderation permission) entirely | Grant the permission on the bot's role |
How to reorder roles
- Open Server Settings → Roles.
- Find the bot's role (it has the bot's name).
- Drag it above every role you want it to assign or manage, and above the members it should moderate.
- Keep it below roles it should never touch, such as your admin roles.
You can only drag roles that are below your own highest role, so do this with the owner account or an admin positioned near the top.
A role order that works
A layout that suits most community servers, from top to bottom:
Owner / Admin roles
Bot roles (moderation and utility bots)
Moderator roles
Helper / Support roles
Self-assign, level reward and colour roles
Member / Verified
@everyone
With this order, the bot can hand out every cosmetic and reward role and moderate regular members, while admins remain out of reach. Whether bots sit above or below moderators is a choice: above means automated sanctions can apply to moderators too; below means moderators are protected from automation mistakes. Putting the bot just above moderators keeps escalation rules consistent for everyone; either choice works as long as it's deliberate.
The colour role trap
Members' "highest role" counts regardless of what that role does. If you place a purely cosmetic colour role high in the list so the colour shows, everyone who picks that colour becomes immune to a bot placed below it. Keep colour and decoration roles below your bot roles. Name colours are decided by the highest coloured role, so you rarely need cosmetic roles near the top anyway.
Several bots? Keep them together
If you run more than one bot, group their roles in one block. A ticket bot placed below a reward role, or a moderation bot below a colour role, creates gaps that only show up when something fails at the worst moment. One block, positioned once, avoids this.
What this means for MagnificBot
MagnificBot is invited without Administrator, with the specific permissions its modules use. Like any bot, it's bound by the hierarchy: role panels and level-up role rewards only work for roles below the MagnificBot role, and /timeout, /kick and /ban only work on members whose highest role is below it. After inviting it, take ten seconds to drag its role above your reward, self-assign and colour roles.
The server manager module in the dashboard lets you review roles and edit their permissions without opening Discord's settings, but the same rule applies there: the bot can only change roles below its own. If you're moving several bots' jobs into one, our guide on replacing multiple Discord bots with one covers the rest of the setup.
FAQ
Why does my bot say "Missing Permissions" when it has Manage Roles?
The role it's trying to manage, or the member it's acting on, is at or above the bot's highest role. Move the bot's role higher.
Does giving a bot Administrator fix role hierarchy errors?
No. Administrator grants permissions but doesn't let a bot manage roles above its own position.
Can I delete the bot's own role?
Not while the bot is in the server. You can move it and adjust its permissions, but you can't delete it or assign it to anyone else.
Should the bot be above my moderators?
It depends on whether you want automated sanctions to affect moderators. Either is fine as long as you choose on purpose.
Ready to set up roles the right way? Invite MagnificBot from magnificbot.com, then place its role above the roles it should manage.
Experimenta o MagnificBot grátis
Todos os módulos incluídos, configurados num painel web. Sem cartão e sem data de fim.
Adicionar ao Discord — é grátis