Understanding Discord Permissions: Server, Roles and Channels
General Discord knowledge: how roles, server permissions and channel permissions work together, how to build private channels and what to do when someone sees a channel but cannot write in it.
Last checked for accuracy: 21 October 2026
This page explains how permissions work in Discord in general. It is general Discord knowledge and applies to every server, with or without Kage.
At a glance
| Question | Answer |
|---|---|
| Where do permissions come from? | From a member's roles. All roles add up. |
| What is @everyone? | A role everyone has. Its permissions are the baseline for all. |
| What do channel permissions do? | They change the server permissions for that channel or category only. |
| Who wins in a conflict? | A channel rule beats the server permission. A rule for a single person beats rules for roles. |
| And Administrator? | Whoever has it is exempt from all channel rules. |
| Building a private channel | @everyone may not View Channel, the wanted role may. |
Server permissions and roles
Every member has one or more roles. Each role carries permissions such as Send Messages or Kick Members. If a role has a permission, the member has it. Several roles add up. The order of roles still matters: a role can only manage roles and members that are below its highest role in the list. This also applies to bots.
Channel permissions and categories
On top of role permissions you can set rules per channel or category. For every permission there are three states: allow, deny or "not set" (the server permission still applies). Rules set on a category are taken over by the channels inside it as long as their permissions are synced. If someone changes a channel's permissions individually, it is no longer synced with the category.
Building a private channel
- Open the channel settings, section Permissions.
- Choose @everyone and deny View Channel.
- Add the role that should see the channel and allow View Channel (and Send Messages if needed).
- Do not forget the role of bots that should write there, such as Kage.
How to combine this with Kage is described in Private areas for specific roles.
Typical problems
| Problem | Usually caused by | What helps |
|---|---|---|
| Someone sees the channel but cannot write | Send Messages is denied in the channel or category for that person's role, or they only have @everyone with a deny | Check the channel permissions of the person's roles, remove the deny or grant the role |
| Someone does not see a channel | View Channel is denied or not allowed | Allow the role in the channel, check @everyone |
| The bot cannot assign a role | Its role is below the target role or it lacks Manage Roles | Drag the bot's role up in the list |
| The bot sends nothing to a channel | The bot lacks View Channel or Send Messages there | Allow the bot's role in the channel permissions |
| A change has no effect | A deny for the person themselves or a higher channel rule overrides it | Go through all rules of the channel |
Why the bot should not be "Administrator"
Administrator bypasses all channel rules and can do everything. That is convenient but risky. Give a bot exactly the permissions it needs. How Kage handles this is described in Which permissions does Kage need?.
Keep reading
More questions? Ask Kage AIAI
Describe what you need – Kage AI picks out the right guide and gives you the sources.
Try Kage on your server
Sign in with Discord, invite the bot and set up the modules in the dashboard. The Basic plan is free forever.