💬 Lesson 14: Roles & Permissions
This is the most important skill in Act II. Roles and permissions decide who can do what in your server — who moderates, who posts where, who sees a hidden channel. Get the model right and everything downstream (moderation, private channels, bots) becomes easy. Get it fuzzy and you'll fight your own server. We'll go slow and concrete, using the PracticalAce roles as our worked example. It's all Free.
📚 What You'll Learn
By the end of this lesson, you will be able to:
- Explain what a role is and how @everyone acts as the base role
- Order roles into a hierarchy and predict what "higher manages lower" means in practice
- Tell a server-wide permission apart from a per-channel override (allow / deny / neutral)
- Explain why Administrator bypasses everything — and why you hand it out carefully
In This Lesson
What Is a Role?
A role is a named group with a color and a set of permissions. You assign roles to members, and each member's abilities are the sum of the roles they carry. Instead of setting powers person-by-person, you set them once on a role — "Moderator" — and hand that role to whoever should have it.
Roles do two jobs at once:
- Permissions — what a member can do (delete messages, kick people, mention everyone, and so on).
- Cosmetics & grouping — a color for the member's name, and an optional listing in the member sidebar. A "color role" might grant no powers at all — it just makes a name blue or gold.
You create and edit roles in Server Settings ▸ Roles (the exact label can shift over time, and mobile lays it out a little differently). For PracticalAce, we'll build a simple, common ladder:
| Role | Who has it | Rough powers |
|---|---|---|
| Owner | You (the creator) | Everything. The owner is above all roles by definition and can't be out-ranked. |
| Admin | A tiny circle of total trust | Nearly everything (often the Administrator permission — handle with care). |
| Mod | Your moderators | Manage Messages, Timeout/Kick, maybe Ban — enough to keep order, not to reshape the server. |
| Member | Regular trusted members | Chat, react, join voice — the normal community abilities. |
| Muted (optional) | Someone being cooled down | A role whose overrides deny sending messages in channels. |
🧠 Mindset
Permissions feel intimidating because they look like a giant wall of toggles. They're not a test of memory — they're a system with three ideas: roles carry powers, higher roles outrank lower ones, and channels can fine-tune the rules. Learn those three and every toggle makes sense. When something behaves unexpectedly, it's almost always one of the three at work — not you being "bad at this."
@everyone & the Hierarchy
@everyone is the base role
Every server has a built-in role called @everyone. It applies to all members and
sets the baseline of what an ordinary person can do. Every other role you create adds
powers on top of that baseline. So a smart pattern is: keep @everyone sensible-but-limited, then
grant extra abilities through roles like Mod and Admin.
💡 Definition: @everyone
@everyone is the default role held by every member. Think of it as the floor: whatever
@everyone can do, everyone can do. (It's also the mention that pings the whole server
— a power you'll usually restrict, since you rarely want any member pinging everyone.)
Order matters: the hierarchy
In the Roles list, roles sit in a vertical hierarchy — higher in the list means higher authority. This ranking decides two crucial things:
- Who can manage whom. A role can only manage (kick, ban, edit roles of, timeout) members whose highest role is below its own. A Mod can act on a Member, but not on an Admin or another Mod above them.
- Name color. When a member has several colored roles, the highest one that has a color wins and shows on their name.
⚠️ Important — the classic gotcha: If your moderator "can't ban someone," it's almost always hierarchy. The target has a role at or above the Mod's highest role, so Discord refuses the action. Fix it by ordering roles correctly: Admin above Mod above Member. You can only act on people below you.
Here's the PracticalAce ladder. Higher roles manage everyone beneath them; nobody can act upward:
Figure 1 — A simple role hierarchy. Authority flows downward: each role can manage those below it and never those above it. (Positions in Discord's Roles list; labels are our example names.)
Server Permissions vs Channel Overrides
This is the part that trips up nearly everyone, so let's make it click. Permissions come from two layers:
- Server-wide role permissions — set on the role itself (Server Settings ▸ Roles). These apply everywhere in the server by default.
- Per-channel overrides — set on an individual channel (edit the channel ▸ Permissions). These adjust the rules just for that one channel, on top of the role permissions.
Allow, Deny, Neutral
In a channel's permission overrides, each permission for each role (or member) has three states:
| Override state | Symbol you'll see | What it means |
|---|---|---|
| Allow | Green check | Grant this permission here, even if the role lacks it server-wide. |
| Neutral (inherit) | Grey slash | Don't decide here — fall back to the role's server-wide setting. |
| Deny | Red X | Block this permission here, even if the role has it server-wide. |
The two most useful patterns fall right out of this:
- A private (mods-only) channel: in that channel, deny "View Channel"
for
@everyone, then allow "View Channel" for the Mod role. Now only mods can see it — the base role is blocked, and one role is granted back in. - A muted member: give the Muted role a channel override (or category override) that denies "Send Messages." Wherever that override reaches, they can read but not post.
How the layers combine
Discord resolves a member's power in a channel roughly like this: start from @everyone, add the
permissions from all their roles, then apply the channel's overrides — deny beats allow when
they collide at the same level, and a channel's explicit allow/deny outranks the plain server-wide setting.
One giant exception sits above all of it, which we'll meet next: Administrator.
Figure 2 — Permission = base role, plus each role's powers, adjusted by channel overrides. Deny beats allow, and Administrator (next section) skips the whole chain.
Here's what a mods-only channel looks like in the sidebar — regular members simply never see it, while a little lock hints at its restricted access:
Figure 3 — A private mods-only channel (simplified mock-up, not a real screenshot). Members without the Mod role don't see it at all. The lock icon is illustrative.
✅ Tip: set it on the category, sync the channels
Remember category permission-syncing from Lesson 13? Put your Staff channels in a Staff category, set the "only Mod can view" override once on the category, and sync the channels to it. Every channel you add there inherits the rule automatically — far less fiddly than editing each channel.
Key Permissions & the Administrator Trap
There are many permissions, but a handful do most of the work. You don't need to memorize them — just recognize what they let someone do so you can assign them thoughtfully.
| Permission | Lets the role… | Typically for |
|---|---|---|
| Manage Channels | Create, edit, delete, and reorder channels | Admin (rarely Mod) |
| Manage Roles | Create/edit roles and assign them (only ones below their own) | Admin |
| Manage Messages | Delete or pin others' messages | Mod |
| Timeout Members (Moderate Members) | Temporarily mute a member across the server | Mod — the gentle first tool (Lesson 15) |
| Kick / Ban Members | Remove someone (kick) or block them from returning (ban) | Mod / Admin |
| Mention @everyone | Ping the whole server with @everyone / @here | Admin / trusted roles only |
| Administrator | Everything — bypasses all other permissions and overrides | You and total-trust admins only |
🚨 The Administrator trap
Administrator overrides everything. A role with Administrator ignores every other permission setting and every channel override — including a "deny" you carefully placed. Give someone the Administrator permission and they can see every private channel, manage every role below them, and change almost anything in the server. It is not a convenient "trusted member" badge. Hand it only to people you'd trust with the whole server, and prefer building a Mod role with the specific permissions it needs instead. When in doubt, don't grant Administrator.
⚠️ Watch out: two hierarchy realities
First, even an Administrator can't act on the Owner, and can't manage roles positioned above their own — hierarchy still constrains who they can target. Second, for a Mod to be able to act on troublemakers, the Mod role must sit above the roles those members hold. If your "Member" role accidentally sits above "Mod," moderation quietly breaks. Order the list carefully.
🛠️ How To: Roles & a Mods-Only Channel
Build a working permission setup
What you'll do: Create a Mod role and a Member role with sensible powers, order them correctly, and make a private mods-only channel using overrides. Do this in your own server.
Step by step
- In Server Settings ▸ Roles, create a Member role (name color optional). Leave it with normal chatting abilities.
- Create a Mod role. Turn on Manage Messages and Timeout Members (and optionally Kick). Leave Administrator OFF.
- Drag Mod above Member in the roles list so hierarchy is correct.
- Make a new text channel called mod-chat (a Staff category is ideal).
- Edit that channel ▸ Permissions: deny "View Channel" for
@everyone, then allow "View Channel" for Mod. - Test it: check that a non-mod account (or a friend) can't see mod-chat, while a Mod can.
💡 Tip
Can't find channel overrides? Hover the channel, click its gear/edit, and choose "Permissions." Add
@everyone and the Mod role to the list, then toggle each permission to the green check
(allow), grey slash (neutral), or red X (deny). If mods still can't ban later, check the roles list
order — Mod must sit above the people they need to act on. On mobile these panels look
different but hold the same options.
📓 Learning Journal
Keep adding to your Learning Journal — a note in Discord, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:
- Key concepts you learned
- Things that clicked for you
- Questions or confusion points to revisit
- Ideas you want to try
- Your progress and how you feel about learning this
✍️ This lesson's prompt: Write your server's role ladder from top to bottom, and next to each role list the two or three powers it should have. Then explain, in your own words, the difference between a server-wide permission and a channel override — and why you'd never casually hand out Administrator.
📝 Lesson Summary
🎓 Key Takeaways
- A role is a named group with a color and permissions; a member's power is the sum of their roles.
- @everyone is the base role — the floor everyone stands on; other roles add powers on top.
- Hierarchy means higher roles manage lower ones; a mod can't action someone at or above their own role.
- Permissions come from server-wide role settings plus channel overrides (allow / deny / neutral); deny beats allow.
- Administrator bypasses everything — give it only to total-trust people; otherwise build a scoped Mod role.
🎉 What You've Accomplished
You just learned the model that everything else in Act II depends on. You can build a role ladder, keep
@everyone sensible, layer channel overrides to hide or open a channel, and you know the two
traps — hierarchy and Administrator — that catch almost every new owner. Moderation, private channels, and
bots will now feel like variations on what you already understand.
❓ Common Questions at This Stage
Why can't my mod ban someone?
Hierarchy. A role can only act on members whose highest role is below it. If the target has a role at or above your Mod role — or if Member accidentally sits above Mod in the list — Discord blocks the action. Reorder the roles so Mod is above the people it must manage.
What's the difference between a server permission and a channel override?
A server permission (set on the role) applies everywhere by default. A channel override (set on one channel) adjusts the rule just for that channel — allow, deny, or neutral. Overrides let you open or lock a single channel without changing the role everywhere.
Is Administrator safe to hand out?
No — treat it as "co-owner." Administrator ignores every other permission and channel override, so an admin can see all private channels and change almost anything. For helpers, create a Mod role with the specific permissions they need (Manage Messages, Timeout, maybe Kick) and leave Administrator off.
🔭 Looking Ahead
In Lesson 15, you'll put these roles to work with Discord's built-in moderation tools — AutoMod, verification levels, timeouts, kicks, and bans — all free, and all relying on the permission model you just mastered.
📚 Additional Resources
- Glossary — every term in plain language
- Quick-Reference Cheat Sheet — includes a permissions quick-map
- Discord Support — official help articles on roles and permissions
- Discord.com — the official home page
🌟 Encouragement for the Journey
Roles and permissions scare off a lot of would-be server owners — and you just walked straight through the hardest concept in Act II. Everything from here builds on what you now understand. Take a breath: you've got the keys to the whole system.