hourden
Sign in Create accountSign up
BuyInstagramTikTokYouTubeFacebookX (Twitter)TwitchTelegramSpotifySoundCloudDiscordRedditLinkedInThreadsPinterestSnapchatRumbleWebsite trafficMobile appVKAudiomackClubhouseApple MusicBlueskyDailymotionLikeeMixcloudQuoraTumblrVimeoAll services

How to Add Roles in Discord

Creating a role takes a minute. The thing that decides whether it works is where it sits in the list.

Updated October 2026

Open server settings, go to Roles, and create a role. Give it a name, a color, and switch on the permissions it should have. Then assign it to members from the member list or by right-clicking a name.

The part people miss is the ordering. Roles sit in a list, and that list is the hierarchy.

A moderator can only time out, kick or ban members whose highest role is below theirs, so a moderator role placed too low cannot moderate anybody.

The part most guides skip

Discord's permission model is built on that ordered list, and once you see it the strange behavior stops being strange.

Every member has the permissions of every role they hold, combined. Permissions add up; they do not override each other, except in channel-level settings where an explicit deny wins.

The hierarchy decides who can act on whom. A role can only manage members and roles positioned below it. That applies to kicking, banning, timing out, changing nicknames and assigning roles.

So the three classic failures all have the same root. A moderator role created last sits at the bottom and cannot touch anyone. A bot that cannot assign a role is positioned below the role it is supposed to hand out. An admin complaining that someone could not be kicked is looking at two roles in the wrong order rather than at a missing permission.

The server owner is outside the hierarchy and can always act. Everyone else is governed by position, which is why the first thing to do after creating roles is to drag them into the order that matches the authority you intend.

Creating and assigning a role

Server settings, Roles, create role. Name it for what it is, not for a joke; roles are visible in the member list.

Color decides how the name appears, and the highest-positioned colored role wins when someone holds several.

Permissions are switches. Grant the narrow set the role needs, and avoid Administrator unless you mean it, because it overrides everything including channel denials.

Assign from the member list, from a right-click on a name, or automatically with a bot.

The hierarchy, in practice

Drag roles up and down in the Roles list. Higher means more authority.

A member's effective rank is their highest role. A moderator with a decorative role above the troublemaker's role is still fine; what matters is the top one on each side.

Bots follow the same rule. A bot can only assign roles below its own, which is the single most common support question in any Discord community.

The owner sits above everything and cannot be acted on by anybody.

Channel permissions on top

Each channel can override server-wide permissions for a role or a member.

An explicit deny at channel level beats an allow from a role, with the exception of Administrator.

The @everyone role is where defaults live. Locking a channel usually means denying view to @everyone and allowing it for one role, rather than denying it to each role in turn.

Synced categories make this manageable: set permissions on the category, and channels inside inherit them.

Permissions worth being careful with

Administrator grants everything and ignores channel denials.

Manage Roles lets a holder edit any role below their own, which is a route to escalation if given carelessly.

Manage Server, Manage Channels and Manage Webhooks are the ones that let a compromised account do lasting damage.

Mention Everyone is the one that produces the most regret in a large server, and it is often handed out with a decorative role by accident.

Self-assignable roles

Members can pick their own roles through a bot, usually with reactions or buttons, or through Discord's own onboarding questions.

Onboarding is the native route: server settings has a customization area where you define questions and the roles each answer grants.

It is better than a bot for simple cases because nothing breaks when the bot goes offline.

For anything conditional or large, a bot is still the tool, and it needs to sit above the roles it hands out.

Questions people ask about Discord roles

How do I create a role in Discord?

Server settings, Roles, create role. Set the name, color and permissions, then assign it from the member list.

Why can't my moderator kick anybody?

Their role sits below the target's highest role. Authority follows the order of the roles list, not the permission alone.

Why can't my bot assign a role?

The bot's own role is positioned below the role it is trying to give. Drag the bot's role above it.

Do permissions stack?

Yes. A member has the combined permissions of all their roles, except where a channel explicitly denies something.

What does Administrator actually do?

It grants every permission and ignores channel-level denials. Give it only to people you would trust with the server itself.

Can members choose their own roles?

Yes, through Discord's onboarding questions or a bot with reaction or button roles.

Keep reading