Discord Role Hierarchy Explained: Why Your Moderator Can't Ban (and How to Fix Role Order)

Your moderator can't ban or kick because their role sits below the target's role in your server's role list. In Discord, a role can only act on roles positioned underneath it — so drag the Moderator role above the roles it needs to manage in Server Settings → Roles, and the same fix applies to your bot's role.

This single mechanic — role position — quietly breaks moderation on more servers than any permission toggle. You can hand someone the Ban Members permission and they'll still get a flat "Missing Permissions" error if their role is in the wrong spot. Here's exactly what role hierarchy controls, why it blocks bans and kicks, and how to put your roles in the right order.

What role hierarchy actually controls in Discord

Open Server Settings → Roles. You'll see a vertical list of roles, with @everyone pinned at the bottom. That vertical order is your hierarchy. The role at the top is the most powerful; the role at the bottom is the weakest. This is not cosmetic — Discord reads the list literally.

Role position controls three things:

• Who can moderate whom. A member can only ban, kick, timeout, or remove the roles of members whose highest role sits below their own highest role.
• Who can manage which roles. With Manage Roles, you can only assign, edit, or delete roles that are below your highest role — never your own role or anything above it.
• Display color and ordering. The highest role in the list that has a color and "display separately" wins for a member's name color and sidebar grouping. (Useful, but not the part that breaks moderation.)

Permissions decide what an action is. Hierarchy decides who you're allowed to do it to. You need both to line up. If you've been chasing the wrong checkbox, our guide on why Discord permissions don't work even when they look correct covers the overwrite side of the same problem.

The golden rule: you can only act on roles below your own

Memorize this one sentence and most "missing permissions" mysteries solve themselves:

A role can only take action on roles positioned below it in the list.

"Action" means ban, kick, timeout, change nickname, add or remove roles, or move someone in voice. It applies to humans and bots identically. A few consequences that trip people up:

• Equal isn't enough. If your Moderator role and a Helper role are at the same position, a Moderator still can't moderate a Helper. It has to be strictly above.
• Highest role wins. Discord only checks each member's single highest role. A moderator with three roles is judged by their top one; a target with five roles is judged by their top one. Top vs. top.
• The server owner ignores all of this. The owner can act on anyone regardless of position. That's why "it works for me but not my mods" is so common — owners never feel the limit.
• Administrator does not bypass hierarchy. A common myth. Admin grants every permission, but a member with Administrator still cannot ban someone whose highest role sits above theirs. Position beats the Administrator flag.

Why your moderator can't ban (the bot or mod sits too low)

There are really only two versions of this problem, and they have the same cause.

Case 1: A human moderator can't ban. Your Moderator role has Ban Members checked, but clicking Ban does nothing or throws an error. Almost always, the person they're trying to ban has a role that sits at or above the Moderator role. Maybe the troublemaker holds a cosmetic "VIP" or "Booster" role you placed near the top of the list for color reasons. That color choice just made them unbannable by your mods. Move Moderator above VIP, or move VIP down, and the ban works.

Case 2: Your bot can't ban, kick, or assign roles. Bots obey the exact same rule. When you invite a bot, Discord drops its integration role somewhere in the list — often lower than you'd expect. If your AI or moderation bot's role sits below the members it's supposed to act on, every auto-ban, auto-kick, auto-mute, and auto-role silently fails. The bot has the permission; it just lacks the position. This is the single most common reason a Discord bot won't assign roles or won't enforce moderation.

In both cases the permission is a red herring. The fix is reordering, not re-checking boxes.

Where the bot's role needs to sit relative to members

Put your bot's role above every role it must manage — and that usually means above almost everything except the owner-only top roles.

Concretely:

• A moderation bot that bans rule-breakers must sit above all member, regular, and cosmetic roles — anyone it might need to ban or mute.
• A bot that hands out level rewards or reaction roles must sit above every role it assigns.
• It's normal and safe for a trusted bot to sit near the top of the list, just under your owner/admin roles. It can only ever act on what's beneath it, so a high position is not a security risk by itself.

The one trap: if you grant a level-reward or booster role above your bot, the bot can no longer assign or remove it. People then say "the bot stopped giving out the VIP role" — because VIP crept above the bot during an unrelated reshuffle. Keep the bot's role above anything it touches and that whole class of bug disappears.

Step 1: Open Server Settings → Roles

Click your server name at the top-left, choose Server Settings, then Roles in the sidebar. You're now looking at the live hierarchy. Note where @everyone sits (bottom) and where your staff and bot roles currently land.

Step 2: Identify the role that's stuck too low

Find the role that can't perform the action — your Moderator role, or your bot's integration role. Then find the role of whoever it's failing to act on. If the actor isn't strictly above the target, that's your bug. Hover each role to confirm which one is higher; the list reads top-to-bottom as strongest-to-weakest.

Step 3: Drag the role to the correct position

Grab the role by the handle (or the role name) and drag it upward, dropping it above every role it needs to manage. For a moderator, that's above all member and cosmetic roles. For a bot, that's above everything it bans, mutes, or assigns. On mobile, long-press and drag, or use the reorder arrows. Discord saves the new order immediately — there's no separate save button on desktop.

Step 4: Re-test the exact action that failed

Don't assume. Try the real ban, kick, or role assignment that broke. If it works, you're done. If it still fails, the action is now genuinely a permission gap rather than hierarchy — jump to how to set up Discord roles and permissions and confirm the Ban Members or Manage Roles permission is actually checked on the role (and not overridden by a channel-level overwrite).

How to reorder roles correctly in Server Settings

A clean, drama-free hierarchy from top to bottom usually looks like this:

1. Owner / Admin — full control, top of the stack.
2. Senior staff bots (anti-raid, moderation, AI builder) — high enough to act on everyone below.
3. Head Moderator / Admin team — humans who manage staff and members.
4. Moderator / Helper — above all members and cosmetic roles.
5. Utility bots (leveling, reaction roles) — above every role they assign.
6. Booster / VIP / cosmetic roles — color and perks, no power.
7. Members / verified roles.
8. @everyone — locked at the bottom.

The principle: anyone (or any bot) with power sits above everyone they have power over. Cosmetic and reward roles, however shiny, belong below your enforcement roles. For the full breakdown of permissions to pair with this order, our complete Discord permissions guide for 2026 walks through every toggle.

Common hierarchy mistakes that silently break moderation

• Cosmetic roles placed too high. A pretty "VIP" role near the top makes its holders unbannable by mods and bots. Keep cosmetics low.
• Bot role left wherever Discord dropped it. New bots often land mid-list. If you never move it up, half its automations quietly fail.
• Assuming Administrator overrides position. It doesn't. Admins still can't touch roles above their own.
• Equal-rank staff roles. Two staff roles at the same height can't moderate each other — sometimes that's intended, often it's an accident.
• Reward roles above the leveling bot. The bot can't grant what sits above it, so level-up rewards just stop appearing.
• Fixing the permission instead of the position. You re-check Ban Members five times and nothing changes, because the problem was never the permission.

None of these throw a helpful error. Discord just returns "Missing Permissions," which sends people hunting in entirely the wrong menu.

How AI server builders set up a sane hierarchy automatically

Ordering roles by hand is fiddly, and the cost of one wrong drag is silent broken moderation weeks later. This is one area where letting a bot lay out the structure first genuinely saves grief.

PeakBot's AI Server Builder generates a complete server — channels, categories, roles, permissions, and automations — from a plain-English description in under 60 seconds, and it places roles in a working hierarchy from the start: staff above members, cosmetics below enforcement, and its own role positioned high enough to actually moderate. It's the only Discord bot that builds fully custom server structures from natural language rather than dropping in a fixed preset template, so your hierarchy matches your server instead of a generic one. The AI Server Builder is a Pro feature ($8.25/month, or $69/year per server); PeakBot also ships 30+ features free with no time limit, including AI moderation, XP and leveling, tickets, and unlimited reaction roles.

PeakBot replaces MEE6, Carl-bot, Dyno, and TidyCord with one bot, and it currently powers 500+ Discord communities. To be fair to the alternatives: Carl-bot ($7.99/mo premium) has long been a favorite for granular reaction-role setups, Dyno ($4.99/mo premium) is the cheap, dependable moderation workhorse, and MEE6 ($11.95/mo premium) remains the most recognizable name for leveling. PeakBot's edge is doing the whole stack — including a sane role hierarchy out of the box — in one place. You can line them up yourself on the bot comparison page.

Whichever route you take, the rule never changes: power flows top-down, and a role can only act on what sits beneath it.

FAQ

Why can't my moderator ban someone even though they have Ban Members?

Because the target has a role positioned at or above the moderator's highest role. Ban Members grants the permission, but Discord's hierarchy still blocks the action unless the moderator's role sits strictly above the target's highest role. Move the Moderator role up in Server Settings → Roles.

Does the Administrator permission ignore role hierarchy?

No. Administrator grants every permission, but a member with Administrator still cannot ban, kick, or manage anyone whose highest role sits above their own. Only the server owner is exempt from hierarchy.

Where should my bot's role go in the role list?

Above every role it needs to act on. A moderation bot belongs above all members and cosmetic roles so it can ban and mute them; a leveling or reaction-role bot must sit above every role it assigns. A high position is safe because a role can only ever act on roles beneath it.

Why did my bot stop giving out a reward role?

The reward role was likely moved above the bot's role. A bot can only assign roles positioned below its own, so drag the bot's role back above the reward role in Server Settings → Roles and the automation will work again.

How is role hierarchy different from channel permissions?

Hierarchy is server-wide and decides who can act on whom based on role position. Channel permission overwrites are per-channel and decide what a role can do inside that specific channel. A correct hierarchy with a bad channel overwrite still fails — see our guide on why Discord permissions don't work.