Discord roles and permissions explained

Most permission problems come from three rules. Once you know them, you can set up any server.

Rule 1: @everyone is the baseline

Every member has the @everyone role. Its permissions are what a brand-new member can do. Give @everyone only safe basics: view channels, send messages, read history, add reactions, connect and speak in voice. Everything else goes on specific roles.

Rule 2: role permissions add up

At the server level, a member gets every permission from every role they have. There’s no “deny” at the server level; if any role allows it, they have it. Administrator grants everything and skips all channel overrides, so give it to as few people as possible.

Rule 3: channel overrides win, in order

Each channel can allow (green check) or deny (red X) permissions for specific roles or members. Discord applies them in this order, each step overriding the last:

1. The member’s server-wide permissions from all their roles.
2. The channel’s @everyone override.
3. All role overrides for that channel, combined (an allow from any role beats a deny from another role at this step).
4. An override for that specific member.

So to make a staff-only channel: deny View Channel for @everyone on that channel, and allow it for the Staff role.

Role hierarchy

Roles are ordered in Server Settings, Roles. A member can only manage, kick, ban, or assign roles that are below their own highest role. Keep your bots’ roles above the roles they need to manage, and keep moderator roles above member roles.

A safe starter setup

• Owner: you.
• Admin: Manage Server, Manage Roles, Manage Channels. Avoid Administrator unless needed.
• Moderator: Kick, Ban, Timeout Members, Manage Messages, View Audit Log.
• Member / interest roles: no extra permissions, used to unlock channels.
• Bots: only what each bot uses. Build exact invite links with the permissions calculator.

Turn on Require 2FA for moderator actions in Safety Setup so a stolen moderator account can’t wreck the server.