6 min read · Published 2026-09-29 · Updated 2026-11-01 · Perminator
The order of roles in Server Settings is not cosmetic. It is the rule that decides who is allowed to act on whom. Most "why can't my moderator do this?" and "why did my moderator just do that?" questions come down to the role hierarchy. This guide explains the rules and shows how to design a hierarchy that behaves predictably.
Position is power
Roles in a server form a single ordered list, from the top role down to @everyone at the bottom. Dragging a role up or down changes its position. A member's effective rank is the position of their highest role, regardless of how many lower roles they hold.
The server owner sits outside the list entirely. The owner can act on every role and every member, and nobody can act on the owner.
The core rule: you can only manage what is below you
Discord enforces a consistent rule across almost every management action. A member can only affect roles and members that sit below their own highest role. In practice that means:
With Manage Roles, you can edit or assign only roles positioned below your highest role.
You cannot grant a permission to a role unless you hold that permission yourself.
You can only kick, ban, or time out members whose highest role is below yours.
You cannot move a role above your own highest role, nor reorder roles that are above you.
Why equal rank does not help
Two moderators who share the same top role cannot kick or ban each other, because neither is below the other. That is usually what you want: peers cannot discipline peers. It also means that if you give every staff member the same "Moderator" role and nothing else, a rogue moderator cannot be removed by another moderator. You need a higher role, such as "Senior Moderator" or "Admin", whose members can act on the lower tier.
Administrator does not break the hierarchy
A common misunderstanding is that Administrator lets you do anything. It grants every permission flag, but it does not lift the hierarchy rule. An administrator whose top role sits below another role still cannot edit that role or discipline its members. Only the owner has no ceiling.
Placing your bot role
Bots receive their own managed role when they join, and the same rules apply to them. A bot can only assign, edit, or moderate against roles below its role. If your reaction-role bot is placed beneath the role it is supposed to hand out, it will silently fail.
Place each bot role high enough to do its job and no higher. A moderation bot needs to sit above the members it disciplines; a music bot can sit near the bottom. Never place a bot above your owner-level staff roles unless you are comfortable with that bot's code and its permissions, because anyone who can control the bot can effectively act with its rank.
Designing a clean hierarchy
A reliable pattern for a mid-sized server looks like this, from top to bottom:
Owner (a person, not a role) — rarely used day to day.
Admin — a very small group trusted with server-wide settings.
Bots with elevated rank — only the moderation and role-management bots.
Senior Moderator — can discipline moderators and adjust lower roles.
Moderator — kicks, timeouts, and message cleanup within a defined scope.
Helper or Trial Moderator — limited tools while building trust.
Cosmetic and community roles — colors, pronouns, interests.
@everyone.
When the hierarchy is not enough
Position tells you who can act on whom, but not what actions each role may take. A Moderator who holds Manage Roles can still delete every role beneath them. To separate "may assign the Verified role" from "may delete roles" you need finer-grained permissions than Discord provides natively. A role order that stays inside Discord's own flags is written out in the staff ladder . Splitting those flags further is the gap Perminator exists to fill.
