How Discord permissions work
Permissions come from two places. Role permissions, set in Server Settings → Roles, apply across the whole server: a member gets everything that @everyone and any of their roles allow. Overrides, set on a category or channel, then adjust that for specific roles or members. Each override is either ✕ deny, / inherit (no change) or ✓ allow.
The order Discord applies them
- Server permissions from @everyone and all of the member's roles, added together.
- @everyone overrides on the channel: denies, then allows.
- Role overrides: all of the member's role denies at once, then all of their role allows at once.
- Member overrides for that specific person: deny, then allow.
Later steps win. Two consequences catch people out:
- Between roles, an allow beats a deny. If one of a member's roles denies Send Messages on a channel and another allows it, they can send, whatever the order of those roles in the list.
- Role order doesn't change channel permissions. It decides who can manage whom: members can only kick, ban or change nicknames of people whose highest role is below theirs, and can only edit or assign roles below their own.
Rules that override everything else
- The server owner always has every permission.
- Administrator grants every permission and ignores all channel overrides.
- Without View Channel, nothing else in that channel applies. Without Send Messages, mentioning @everyone, attaching files, embedding links and text-to-speech don't apply either.
- Threads follow their channel's permissions, except that posting in them needs Send Messages in Threads.
- A timed-out member keeps only View Channel and Read Message History until the timeout ends.
Check why someone can or can't do something
Copy what you see in Discord for one member and one channel. The checker walks through the order above and shows which setting decides the result. Nothing is saved or sent anywhere.
Decided by: server permissions.
- Server permissions@everyone or one of their roles allows it in Server Settings → Roles.Allowed
- @everyone overrideInherit: no change.–
- Role overridesNeither role overrides it: no change.–
- Member overrideInherit: no change.–
Assumes they can see the channel: without View Channel nothing else applies there. Without Send Messages, they also can't mention @everyone, attach files, embed links or send text-to-speech there.
Every Discord permission, explained
What each permission does, how risky it is, whether it can be set per channel and who usually needs it. High-risk permissions are Manage Channels, Manage Roles, Manage Webhooks, Manage Server, Kick Members, Ban Members, Mention @everyone, @here, and All Roles, Administrator.
All 51 permissions
General server
View Channels
See a channel: read its messages, or see and join a voice channel. Shown as View Channel in channel settings.
Usually for: Everyone. Leave on for @everyone at server level and hide private areas by denying it on their category.
Manage Channels
Create, edit and delete channels. On a single channel it allows editing or deleting that channel.
Usually for: Admins. Admins only. Deleted channels and their messages can't be restored.
Manage Roles
Create and edit roles below your own highest role, and assign them. You can only grant permissions you have yourself. Shown as Manage Permissions in channel settings, where it lets someone edit that channel's overrides.
Usually for: Admins. One or two trusted admins. Anyone with it can give roles below theirs to any account, including their own alts.
Create Expressions
Upload custom emoji, stickers and soundboard sounds, and edit or delete the ones you uploaded.
Usually for: Trusted members. Fine for trusted members if you want community-made emoji and sounds.
Manage Expressions
Edit or delete any custom emoji, sticker or soundboard sound, whoever uploaded it.
Usually for: Moderators. Staff who curate the server's emoji and sounds.
View Audit Log†
Read the Audit Log: who changed settings, roles and channels, and moderation actions such as bans.
Usually for: Moderators. Give to all staff. It lets them check what happened before acting.
View Server Insights
Open Server Insights, the analytics Discord offers to eligible Community servers.
Usually for: Admins. Only matters if your server has Insights; give it to whoever plans growth.
Manage Webhooks
Create, edit and delete webhooks, which post messages under any name and avatar.
Usually for: Admins. Admins only. A leaked webhook URL lets anyone post into that channel.
Manage Server
Change the server's name, icon and settings, manage integrations, and see invite information.
Usually for: Admins. Owner and one or two admins. It controls settings that affect every member.
Membership
Create Invite
Create invite links to the server.
Usually for: Members. Turn off for @everyone if you want to control who invites and where links are posted.
Change Nickname
Change your own nickname in this server.
Usually for: Members. Usually on. Turn off if impersonation of staff becomes a problem.
Manage Nicknames
Change other members' nicknames, for members below you in the role list.
Usually for: Moderators. Moderators, for fixing offensive or impersonating names.
Kick Members
Remove members from the server. They can rejoin with a valid invite. Only works on members below you in the role list.
Usually for: Moderators. Experienced moderators, as part of a written escalation process.
Ban Members
Ban members so they can't rejoin, optionally deleting their recent messages. Only works on members below you.
Usually for: Moderators. Senior moderators. Bans can be undone, but deleted messages can't.
Timeout Members
Time a member out. While timed out they keep only View Channel and Read Message History, so they can read but not send, react or speak.
Usually for: Moderators. The first moderation tool to give. Timeouts don't restrict the owner or anyone with Administrator.
Text
Send Messages
Send messages in text channels and create posts in forum channels. It doesn't cover replying inside threads.
Usually for: Everyone. On for normal chat; deny it on read-only channels such as rules and announcements.
Send Messages in Threads
Send messages inside threads and forum posts.
Usually for: Everyone. Leave on where you want discussion under posts, including read-only announcement channels.
Create Public Threads
Start threads that everyone who can see the channel can open.
Usually for: Members. Useful in busy channels; deny it where threads would scatter discussion.
Create Private Threads
Start invite-only threads. Private threads are available on servers at Boost Level 2.
Usually for: Members. Handy for support or small-group planning; staff with Manage Threads can still see them.
Embed Links
Show previews (embeds) for links you post.
Usually for: Members. Turn off for brand-new members if link spam is a problem.
Attach Files
Upload images and files.
Usually for: Members. Common target for spam and shock images; consider granting it to a Member role rather than @everyone.
Add Reactions
Add new reactions. Without it, members can still click reactions already on a message.
Usually for: Everyone. On almost everywhere; useful on read-only channels so members can acknowledge posts.
Use External Emoji
Use custom emoji from other servers (requires Nitro).
Usually for: Members. Harmless in most servers.
Use External Stickers
Use stickers from other servers (requires Nitro).
Usually for: Members. Harmless in most servers.
Mention @everyone, @here, and All Roles
Ping everyone, everyone online, or any role, including roles that are set not to be mentionable.
Usually for: Moderators. Staff who post announcements. Never on @everyone: one message can notify the whole server.
Manage Messages
Delete other members' messages and remove their reactions.
Usually for: Moderators. Core moderator permission. Scope it to a category for helpers who look after one area.
Pin Messages
Pin and unpin messages. It's a separate toggle from Manage Messages.
Usually for: Trusted members. Give to event hosts or helpers who maintain pinned info without letting them delete messages.
Bypass Slowmode
Post without waiting for a channel's slowmode timer.
Usually for: Moderators. Staff, so they can respond during busy moments.
Manage Threads
Rename, close, lock and delete threads and forum posts, set their slowmode, and view all private threads.
Usually for: Moderators. Moderators and helpers who keep forums tidy. It reveals private threads, so not for regular members.
Read Message History
See messages sent before you opened the channel.
Usually for: Everyone. Leave on. Without it a channel looks empty to people who join later.
Send Text-to-Speech Messages
Send /tts messages that are read aloud to people with text-to-speech enabled.
Usually for: Nobody by default. Usually off; it's easy to misuse.
Send Voice Messages
Record and send voice messages.
Usually for: Members. Optional. Harder for AutoMod to filter than text.
Create Polls
Create polls in messages.
Usually for: Members. Fine for members; deny in channels where polls would be noise.
Voice
Connect
Join voice and Stage channels.
Usually for: Everyone. Deny on private voice rooms the same way you'd deny View Channel on text.
Speak
Talk in voice channels.
Usually for: Everyone. Deny for @everyone in listen-only rooms and allow it for a speaker role.
Video
Turn on a camera or go live (screen share) in voice channels.
Usually for: Members. Consider limiting to a Member role in large public servers.
Use Soundboard
Play soundboard sounds in voice channels.
Usually for: Members. Turn off in study or focus rooms.
Use External Sounds†
Play soundboard sounds from other servers.
Usually for: Members. Optional; off if you want only your server's sounds.
Use Voice Activity
Talk using voice activity detection. Without it, members must use push-to-talk.
Usually for: Everyone. Deny in big rooms to force push-to-talk and cut background noise.
Priority Speaker
Lower other people's volume while you speak, when using the priority speaker keybind.
Usually for: Moderators. Event hosts and coaches who need to be heard.
Mute Members
Server-mute other members in voice.
Usually for: Moderators. Voice moderators. Timeout is better for anything longer than the moment.
Deafen Members†
Server-deafen other members so they can't hear the channel.
Usually for: Moderators. Rarely needed; voice moderators only.
Move Members
Move members between voice channels, or disconnect them.
Usually for: Moderators. Voice moderators and event hosts.
Set Voice Channel Status†
Set the short status text shown on a voice channel.
Usually for: Members. Fine for members; staff can clear inappropriate statuses.
Events and Stage
Request to Speak
Ask to speak in a Stage channel. Stage moderators accept or dismiss the request.
Usually for: Everyone. Leave on for audiences; deny it if you don't take audience questions.
Create Events
Create scheduled events, and edit or delete your own.
Usually for: Trusted members. Event hosts, or members if you run a community calendar.
Manage Events
Edit and delete anyone's scheduled events.
Usually for: Moderators. Staff who look after the calendar.
Apps
Use Application Commands
Use slash commands and context menu commands from apps and bots.
Usually for: Members. On where members use bots; deny in channels where bot commands would clutter chat.
Use Activities†
Start and join Activities (apps such as games) in voice and text channels.
Usually for: Members. Optional; turn off in focus or support spaces.
Use External Apps†
Let apps a member installed to their own account post public replies here. When off, those apps still work but only the member sees the reply.
Usually for: Members. Consider turning off in public channels if user-installed apps post spam.
Advanced
Administrator
Grants every permission and ignores all channel overrides.
Usually for: Nobody by default. Keep it off every role. The owner already has full access; give staff the specific permissions they need.
† Discord's Help Center doesn't name this permission, so the label in your app may be worded slightly differently. 2FA-sensitive permissions are the ones covered by the server's 2FA requirement for moderation. Servers that use Server Subscriptions also have a permission for viewing their subscription insights.
Common permission setups
Exact overrides for the channels most servers need. ✕ is deny, ✓ is allow; anything not listed stays on inherit.
Read-only channel
Members can read and react; only staff post. Use it for rules, announcements and info channels.
Edit Channel → Permissions- @everyone
- Send Messages ✕ · Create Public Threads ✕ · Add Reactions ✓ (optional)
- Staff role
- Send Messages ✓
Check: View Server As Role for Member: you should be able to read and react but not send messages.
Private staff category
Staff channels that members can't see at all.
Edit Category → Permissions, then keep each channel synced- @everyone
- View Channel ✕
- Moderator and Admin roles
- View Channel ✓
Check: View Server As Role for Member: the whole category should disappear.
Channel unlocked by a role
Interest, game or subject channels that appear once someone picks a role.
Edit Category (or Channel) → Permissions- @everyone
- View Channel ✕
- Interest role (e.g. Minecraft)
- View Channel ✓
Check: Give yourself the role on a test account and confirm the channel appears, then remove it.
Listen-only voice room
Anyone can join and listen; only speakers talk. A Stage channel does this with requests to speak if your server has Community.
Edit Channel → Permissions (voice channel)- @everyone
- Connect ✓ · Speak ✕
- Speaker or Host role
- Speak ✓ · Priority Speaker ✓ (optional)
Check: Join as Member and confirm you're muted; join as a host and speak.
Announcements with discussion in threads
Only staff post, but members can discuss each post in a thread.
Edit Channel → Permissions- @everyone
- Send Messages ✕ · Send Messages in Threads ✓ · Create Public Threads ✕
- Staff role
- Send Messages ✓ · Create Public Threads ✓
Check: Staff open a thread on an announcement; a Member account should be able to reply in it.
Emergency lockdown during a raid
Stop new messages quickly while staff clean up.
Edit Category → Permissions on your public categories- @everyone
- Send Messages ✕ · Send Messages in Threads ✕ · Add Reactions ✕
- Staff role
- Send Messages ✓
Check: Also pause invites from Server Settings → Invites. Reverse the overrides when it's over, and announce it.
Planning which channels to create first? Discord channel ideas marks which channels are read-only, role-gated or staff-only for 12 types of server.
Troubleshooting permission problems
Someone can't see a channel
They lack View Channel there. Check the category and channel overrides for @everyone and for each of their roles; a channel that isn't synced keeps its own overrides when you change the category.
A member can still post in a read-only channel
One of their roles allows Send Messages on that channel or category (allows beat denies between roles), they have a member override, or a role gives them Administrator.
Members can read posts but can't reply in threads
Threads need Send Messages in Threads, which is separate from Send Messages. Allow it on the channel.
A moderator can't kick, ban or rename someone
The target's highest role is equal to or above the moderator's. Move the moderator role higher, or have someone above the target act.
A bot can't give a role
The bot's highest role must be above the role it assigns, and it needs Manage Roles. Drag the bot's role above the roles it manages.
Changing a category didn't change one of its channels
That channel isn't synced. Open its permissions and press Sync Now, or edit it directly.
New members see nothing after joining
@everyone may be denied View Channel everywhere. Keep your rules, announcements and main chat visible to @everyone and gate only extra areas.
Permission mistakes to avoid
- Administrator as a shortcut
It can't be limited and ignores every override. Grant the specific permissions instead.
- Mention @everyone left on @everyone
Anyone can then ping the whole server. Keep it with staff who post announcements.
- Denying View Channel at server level
New members see nothing. Hide areas with category overrides instead.
- Fixing problems channel by channel
Each edit un-syncs a channel. Fix the category and re-sync.
- Moderation permissions on cosmetic roles
Colour, interest and ping roles should have no permissions at all.
- Bots above staff
A compromised bot could act on your moderators. Keep bots below staff and above only the roles they assign.
Discord permissions FAQ
What is the difference between server and channel permissions?
Server permissions are set on roles in Server Settings → Roles and apply everywhere. Channel and category permissions are overrides: for one channel or category they allow (✓), deny (✕) or inherit (/) a permission for a role or member, on top of the server permissions.
If one of my roles denies a permission and another allows it, which wins?
The allow wins. On a channel, Discord applies all of a member's role denies together, then all of their role allows together, so any role that allows a permission there beats any role that denies it, whatever their order in the role list. A member-specific override is applied last and beats both.
Does the role order affect permissions?
Not for working out what someone can do in a channel. Role order decides who can manage whom: you can only kick, ban or change nicknames of members whose highest role is below yours, and you can only edit or assign roles below your own highest role.
Why can a member still post in a channel I made read-only?
Usually because one of their roles allows Send Messages on that channel or category, because they have a member-specific override, or because a role gives them Administrator, which ignores all overrides. Check with View Server As Role and look at every role they hold.
Which permissions should moderators have?
Start with Manage Messages, Timeout Members, View Audit Log and Manage Threads, then add Kick Members, Ban Members and voice tools as your process needs them. Keep Manage Roles, Manage Server and Administrator for the owner and one or two admins.
Which permissions need two-factor authentication?
If you turn on the server's 2FA requirement for moderation, it applies to Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Manage Expressions, Manage Messages, Manage Threads, Kick Members and Ban Members (and, on servers that use them, Server Subscriptions insights).