A Discord role is a set of permissions and a label you assign to members. Members can hold many roles at once. The permissions of each role combine to decide what someone can do on the server, and the highest role someone holds decides the colour they appear as in chat and the member list.
Roles are the most powerful thing about a Discord server. They are also the most over-engineered. Most servers can run cleanly with five to eight roles. Past that, you are usually solving a problem you do not have yet.
How roles work
Three things matter when you create a role:
- Permissions. The role grants or restricts specific actions: read messages, send messages, manage channels, kick members, and so on. A user's effective permissions are the union of all their roles, except for channel-specific overrides.
- Hierarchy. Roles are ordered from top to bottom in the server's Roles list. A role can only manage members or roles below itself. The owner sits above all roles by default.
- Display. The role colour, whether it shows separately in the member list (the "hoist" toggle), and whether members can mention it.
Role assignment can happen three ways: manually by a moderator, automatically by a bot in response to an action (verification, levelling up, reaction roles), or self-selected by the member through a menu.
A clean starting set
For a new community server, this is enough:
- Owner. The server creator. One person.
- Admin. Anyone you trust to change server structure. Usually one or two people, often nobody but the owner for the first six months.
- Moderator. People who can timeout, kick, and remove messages. Pick people you actually know, not strangers who volunteered in week one.
- Verified Member. The default role after someone completes onboarding. Most channels are visible only to this role.
- Bots. A separate role for each bot, hoisted so you can see at a glance which bots are still present.
A new server does not need pronoun roles, region roles, hobby roles, or game roles on day one. Add those when at least 50 active members are asking for them.
Permissions that need careful thought
Most permissions are obvious. A few cause subtle problems if you grant them carelessly:
- Manage Channels. Lets the holder rename, delete, and reconfigure channels. Almost never needed outside Admin.
- Mention Everyone. Members with this can ping everyone or here at any time. Even reasonable people get carried away. Reserve for announcement bots or a single trusted role.
- Manage Messages. Lets the holder delete other members' messages and pin messages. Standard for Moderator, but think before extending it.
- Manage Roles. The holder can edit any role below their own. Treat this as Admin territory only.
Reaction roles and self-selection
A self-selection menu lets members give themselves roles by clicking a reaction or button. Useful for opt-in interests (game ping roles, event reminders) and pronouns. Set these up with any modern reaction-role bot.
Limit self-selectable roles to ones that have no real permission impact. Members should be able to give themselves an "Indie Games" ping role, never an "Access to NSFW Channel" role.
Bots and integrations
Each bot you add to your server gets its own automatically generated role with whatever permissions it asked for during invite. After adding a bot, check its role and remove permissions it does not actually need. A music bot does not need Manage Messages.
Place bot roles near the bottom of the hierarchy unless the bot specifically needs to assign roles. A bot above your Moderator role can do anything your moderators can.
Common mistakes
- Granting Administrator to a bot or member out of convenience. Administrator overrides all denials. Use specific permissions instead.
- Too many hoisted roles. The member list becomes a wall of colour with no signal in it.
- Roles that exist for one person's vanity title. They cost nothing in performance but clutter the role list and confuse new joiners.
- Channel permissions overriding role permissions in ways nobody documented. Six months later, nobody remembers why the announcements channel allows one role to post but not another. Write the reason in the channel topic.
When to redesign
If you find yourself adding a new role every other week, or moderators are unsure what permissions a given role has, the role structure has drifted. Spend an hour with a notepad listing what each role is for. Anything you cannot justify in one sentence either merges with another role or gets deleted.
Soulstack runs a Discord bot with role automation, verification, and self-selection menus if you want a single integration instead of three.