Discord Permissions Explained: Roles, Categories, Overrides
Published 20 Nov 2026
Also available in: Deutsch · Español · Français · Português
"Why can new members see the staff channel?" "Why can't my moderators post in #announcements?" Nearly every permission headache on Discord comes from the same place: not knowing in which order Discord combines role permissions and channel overrides. Once you understand the model, which is simpler than it looks, you can predict exactly what any member can do in any channel.
Two layers: server roles and channel overrides
Discord permissions live in two places.
1. Role permissions (server-wide). In Server Settings → Roles, each role has a list of permissions that apply everywhere by default. Every member has the @everyone role, plus whatever roles you assign. A member's base permissions are the combination of all their roles: if any of their roles grants a permission, they have it.
2. Channel and category overrides. In a channel's or category's settings, under Permissions, you can adjust permissions for specific roles or members in that place only. That's how you make a private channel or a read-only announcements channel.
The three states of an override
Each permission in an override has three positions:
- Allow (green check): explicitly grant it here.
- Neutral (grey slash): don't change anything; use whatever the roles say.
- Deny (red cross): explicitly remove it here.
Neutral is the most important and the most forgotten. Most overrides should be neutral, with only the permissions you actually want to change set to allow or deny.
The order Discord resolves permissions
This is the part worth memorising. For a given member in a given channel, Discord works through these steps:
- Start with the member's server-wide permissions from all their roles combined.
- If they have Administrator, stop: they can do everything everywhere. (The server owner can too.)
- Apply the channel's @everyone override.
- Apply the role overrides for the roles the member has. If one of their roles is denied a permission and another is allowed it, allow wins.
- Apply any member-specific override. This beats everything above.
Two consequences surprise people:
- Role position doesn't matter for overrides. A role higher in the list doesn't beat a lower role in a channel override. Allow simply beats deny among role overrides.
- Deny @everyone + allow a role is the standard pattern for private channels, and it works precisely because the role override is applied after the @everyone one.
Where role hierarchy does matter
The order of roles in Server Settings controls other things:
- which roles a member (or bot) can manage, assign or edit: only roles below their own highest role;
- which members they can kick, ban or time out: only those whose highest role is below theirs;
- name colour and sidebar grouping: the highest coloured or separately displayed role wins.
So hierarchy is about power over other roles and members, not about channel access.
Categories and sync
Channels inside a category can be synced to it, meaning they use the category's overrides. Change the category, and every synced channel follows. As soon as you edit a synced channel's permissions individually, it stops being synced, and Discord will show that in the channel settings. You can re-sync later.
A good habit: set privacy at the category level, keep channels synced, and only break sync for the exceptions (like a read-only rules channel inside a public category).
Permissions to hand out carefully
| Permission | Why it's sensitive |
|---|---|
| Administrator | Bypasses every override; equivalent to full control |
| Manage Server | Change server settings, including safety settings |
| Manage Roles | Edit or assign roles below their own, including their permissions |
| Manage Channels | Create, delete and change channels and their overrides |
| Ban / Kick Members | Remove people from the server |
| Mention @everyone, @here and All Roles | Ping the whole server |
| Manage Webhooks | Post messages under any name and avatar |
Bots rarely need Administrator. Give them the specific permissions their features use.
Debugging "who can see what"
When something isn't behaving:
- Open Server Settings → Roles and use View Server As Role to see the server through that role's eyes.
- Check the channel's overrides from top to bottom: @everyone, then roles, then members.
- Look for a member-specific override you forgot about. They're the usual hidden culprit.
- Check whether the channel is still synced with its category.
Managing permissions with MagnificBot
MagnificBot's server manager module lets you handle all of this from the web dashboard: create and edit channels, categories and roles with every Discord permission available, set permissions per role on each channel, hide categories, and sync channels with their category. Before anything is applied, you get a preview of the changes, and you can take a backup of your server structure first, which is reassuring when you're reorganising dozens of channels.
The bot itself doesn't ask for Administrator when you invite it. And if you want helpers to manage the bot without touching Discord permissions, panel roles (Admin, Moderator, Support, Designer, Reader) control dashboard access separately. It's all in the free plan, and our MEE6 vs Dyno vs Carl-bot comparison shows how it fits alongside other bots.
FAQ
Does a higher role override a lower role's channel permissions?
No. In channel overrides, allow beats deny regardless of role position. Only member-specific overrides take priority over role overrides.
Why can a member still see a channel I denied?
They may have another role that's allowed, a member-specific override, or Administrator.
What does syncing a channel to its category do?
It makes the channel use the category's permission overrides, so changes to the category apply to it automatically.
Should I give my bot Administrator?
It's rarely necessary. Grant the specific permissions it needs instead.
Want to restructure permissions without fear of breaking things? Log in at app.magnificbot.com, back up your server, and use the server manager.
Prueba MagnificBot gratis
Todos los módulos incluidos y configurados desde un panel web. Sin tarjeta y sin fecha de caducidad.
Añadir a Discord — es gratis