Skip to main content

Discord Roles and Permissions

By Groupsgyani Admin 4 min read

On this page
  1. How Discord roles and permissions fit together
  2. The role order decides who can act on whom
  3. Why Administrator is the permission to avoid
  4. Granting moderation powers one at a time
  5. Overrides: tightening a channel without breaking it
  6. Painting yourself into a corner
  7. If you only do one thing

Discord roles and permissions come down to one rule and one trap. The rule: roles are ranked, and people can only act on roles below their own highest one. The trap: the Administrator permission unlocks everything else, so a moderator who gets it can do far more than you meant them to.

Short answer: Build roles from the top down, give moderators individual powers like Kick Members and Timeout Members, and keep Administrator for yourself.

How Discord roles and permissions fit together

A role is a label with a bundle of permissions attached. Every member automatically has the @everyone role, which acts as the server's defaults. Anything else, such as Moderator or Member, sits on top of that.

Permissions layer in three steps, according to Discord's support article on roles and permissions: server defaults first, then overrides on a category, then overrides on an individual channel. The most specific layer wins for the channel in question.

A member's name colour comes from their highest role. That is a quick way to see the ranking at work, since the colour you see is the role that counts.

The role order decides who can act on whom

Members can only act on roles below their own highest role. A moderator cannot kick someone ranked above them, however many permissions they hold. Manage Roles follows the same logic and has a second limit: it cannot grant a permission the granter does not have.

So the order of your role list is a security decision. In Server Settings, open Roles and drag them into place. A sensible shape from top to bottom looks like this.

  • Owner or admin. You, and almost nobody else.
  • Moderator. Enough power to keep the peace, nothing about the server itself.
  • Trusted member. A cosmetic or lightly privileged role for regulars, such as the right to share links.
  • @everyone. The floor. Anything you grant here, every new arrival gets.

Anyone can arrive through an invite link, as Discord's help on joining a server describes. Keep @everyone modest.

Why Administrator is the permission to avoid

Administrator effectively unlocks every other permission. Tick it on a role and the individual boxes stop mattering.

The usual story goes like this. A moderator cannot pin a message. You are tired and it is late, so you tick Administrator, and the problem vanishes. So does the safety net you built. That person can now change roles, edit channels and remove other members, and a compromised account with that role can do the same.

The same goes for bots. When a bot asks for Administrator on its invite screen, read it twice, and ask whether the bot needs it or the developer just found it easier.

Granting moderation powers one at a time

Everything a moderator normally needs can be granted individually. These are the ones worth knowing.

  • Kick Members. Removes someone, who can come back with a fresh invite.
  • Ban Members. Removes someone and keeps them out. Hand it to fewer people than Kick.
  • Timeout Members. Silences a person for a set time, which is gentler than a kick and often enough.
  • Manage Messages. Deleting and pinning other people's messages. This is the one most moderators actually need.
  • Manage Roles. Lets someone hand out roles below their own. Powerful, so give it last, and remember it cannot give away what the granter lacks.

Overrides: tightening a channel without breaking it

Say you want a staff-only channel. Open the channel's settings, go to Permissions, deny viewing for @everyone, then allow it for your Moderator role. The channel disappears for ordinary members and stays open for staff.

The same works on a whole category, and every channel inside inherits it unless that channel overrides it. For a gaming server with a separate area for each game, a category per game keeps the setup tidy. You can see how others organise this in the gaming community servers.

Painting yourself into a corner

Most lockouts are quiet mistakes. Deny something to @everyone on a category and forget to allow it for your Moderator role, and your moderators lose it with everyone else. Put the Moderator role above a role you later need to manage, and you cannot manage it from a moderator account.

Test after every change. Make a throwaway account, or use Discord's option to view the server as a role, and check what each level can see and do.

If your server's own staff are the problem, our post on what a report can and cannot do covers where to take it.

If you only do one thing

Open Server Settings, then Roles, and look for Administrator. On mobile, tap the server name, then Settings, then Roles. If any role other than yours has it, untick it and grant the specific powers instead.

When your server is ready for members, you can submit its invite link, or browse the Discord servers hub for ideas on how similar servers are run.