Skip to content
Guide

Dangerous Discord permissions, and what each one can do

The most dangerous Discord permission is Administrator, which grants every other permission and ignores every channel override. Close behind are Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Kick Members, Ban Members and Timeout Members, which hand over control of the server or its members. None of them belong on @everyone, and each one belongs on as few roles as possible.

By Digital DenUpdated November 5, 20267 min read

The master key

Administrator

Administrator turns on every permission at once and bypasses every channel override, including the ones that hide private channels. A member with it can delete channels, ban everyone, give themselves any role and undo almost any safeguard you set up. Only the server owner is above it.

  • Keep it to two roles or fewer, and only on roles held by people you trust completely.
  • Never put it on @everyone, or on a role that onboarding or a reaction role hands out.
  • Be wary of bots that ask for it. A compromised bot with Administrator can do anything.

Critical on @everyone

Takeover permissions

Each of these hands over control of the server, its channels or its members. On a trusted staff role they are normal. On @everyone, or a role half the server has, any one of them is enough to wreck a server.

Manage Server
Change the server's name and settings, see every invite, add apps and bots, and edit AutoMod rules.
Manage Roles
Create, edit and delete roles below their own highest role, give them to members, and change the permissions on channels they can see.
Manage Channels
Create, edit and delete channels.
Manage Webhooks
Create, edit and delete webhooks. Anyone with a webhook's link can post in its channel under any name and picture.
Kick Members
Remove members from the server. They can rejoin with another invite.
Ban Members
Permanently ban members and delete their recent message history.
Timeout Members
Stop members from sending messages, reacting, or speaking in voice for a set time.

Manage Roles has a ceiling

Discord only lets someone with Manage Roles edit roles below their own highest role, and never grant a permission they do not have. That is why the order of roles in Server SettingsRoles matters: keep staff roles above member roles, and bot roles where they need to be.

In an EvaluBot audit, a takeover permission on @everyone, Administrator included, costs 20 points. Other roles holding Manage Server, Manage Roles, Manage Channels or Manage Webhooks cost 5 points each, up to 15, unless they are admin or bot roles. How the score works.

Critical on @everyone

Mention @everyone, @here and All Roles

This lets someone ping every member at once. It is what turns one compromised account into a scam link in every member's notifications. Keep it on staff roles that post announcements, and off @everyone, where it costs 15 points in an audit.

High on @everyone

Elevated permissions

These are everyday moderation and management tools. Staff roles need some of them, which is why EvaluBot never scores them on staff roles. On @everyone they let any member delete messages, move people around voice or read the audit log, and each one costs 4 points, up to 12.

Manage Expressions
Edit or delete the server's custom emoji, stickers and soundboard sounds.
Manage Nicknames
Change other members' nicknames.
Manage Messages
Delete other members' messages.
Manage Threads and Posts
Rename, close, lock and delete threads and forum posts, and see private threads.
Manage Events
Edit and cancel the server's events.
Mute Members
Mute other members in voice channels.
Deafen Members
Deafen other members in voice channels.
Move Members
Move members between voice channels, or disconnect them.
View Audit Log
Read the record of who changed what in the server.
View Server Insights
See the server's analytics.
Priority Speaker
Be heard over others in voice, which lowers everyone else's volume.
Bypass Slowmode
Post as often as they like in channels with slowmode on.

Worth a look

Risky @everyone defaults

Discord turns some permissions on for @everyone by default. None of them is a takeover, but each one is worth a deliberate decision rather than a default.

Create Public Threads
Lets anyone post under a read-only channel through a thread.
Use External Apps
Lets apps members added to their own account post responses everyone can see.
Create Events
Lets anyone create server events.
Create Expressions
Lets anyone upload custom emoji, stickers and sounds.
Send Text-to-Speech Messages
Lets anyone send messages read aloud to people viewing the channel with text-to-speech on.
Use External Sounds
Lets anyone play soundboard sounds from other servers.
Set Voice Channel Status
Lets anyone change the status shown on a voice channel.

Create Public Threads is the one that most often catches servers out. See how to stop threads in read-only channels.

How to review your roles

  1. 1Start with @everyone in Server SettingsRolesDefault Permissions, and turn off anything above basic member permissions.
  2. 2Open each other role and look for the permissions above. Ask whether that role really uses each one, and replace Administrator with the specific permissions it needs.
  3. 3Use View Server As Role to see the server exactly as a role's members do.
  4. 4Check your bots' roles too. Each bot brings its own permissions, and Digital Den's Discord permissions calculator can decode the permissions number from any bot's invite link.

On a big server that is a lot of clicking. An EvaluBot audit maps 23 sensitive permissions to every role that holds them, with human and bot member counts and who last changed each privileged role, and its permission alerts tell you the moment someone hands one out. To lock the server down further, see how to protect a Discord server from nukes.

FAQ

What is the most dangerous Discord permission?

Administrator. It grants every other permission and bypasses every channel override, so anyone holding it, including a compromised account or bot, can do anything in the server.

Which permissions should @everyone never have?

Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Kick Members, Ban Members, Timeout Members, and Mention @everyone, @here and All Roles. Any of them on @everyone hands that power to every member.

How many roles should have Administrator?

As few as possible, and no more than two. EvaluBot deducts 4 points for every role with Administrator beyond two, up to 16, because each one is another path to a full takeover.

Is Manage Roles dangerous?

Yes. Someone with Manage Roles can edit and hand out every role below their own highest role, and change channel permissions. Discord stops them granting permissions they do not have, but it is still a takeover permission on @everyone or the wrong role.

Should bots have Administrator?

Rarely. A bot with Administrator can do anything if it is compromised or misbehaves. Give bots only the permissions they need. EvaluBot itself asks for Administrator, because from 16 November 2026 Discord hides from a bot every channel it cannot view; its audits and alerts only read, and its permissions page has links with fewer permissions.

See who holds what, in one command.

EvaluBot maps 23 sensitive permissions to every role in your server and scores the setup out of 100. The audit only reads, and never changes a thing.

Join the Discord servers already running EvaluBot.

Running a busy server? Premium gives it 15 audits a month, every risky change as an alert, fix plans and more. See Premium