How to Disable @everyone Pings With Permissions

If you manage a Discord server, you have likely experienced the chaos of an unwanted @everyone ping. A single notification can interrupt an entire community, especially when it is sent accidentally or by a member who should not have that ability. The cause is simple: by default, certain roles are granted the “Mention @everyone, @here, and All Roles” permission. This article explains how to disable @everyone pings by adjusting server and channel permissions for specific roles.

You will learn the exact steps to remove this permission from the @everyone role, from individual user roles, and within specific channels. These methods work on both desktop and mobile versions of Discord. After following this guide, you will have full control over who can trigger mass pings, keeping your server organized and reducing notification noise.

Why @everyone Pings Happen and How Permissions Control Them

The @everyone ping is a mass notification that reaches every member in a Discord server. By default, every role has the “Mention @everyone, @here, and All Roles” permission enabled. This means any member with a role that has this permission can send a server-wide ping. For small servers this may be acceptable, but for larger communities or business servers, accidental or malicious pings can disrupt workflows and cause frustration.

Discord permissions work on a hierarchy. Server-level permissions are inherited by all channels unless overridden. The @everyone role is the base role that all members have. If you disable the mention permission on the @everyone role, no member can ping everyone by default. However, you can then grant that permission to specific roles like Moderator or Admin. This layered approach gives you granular control.

There are three main places where you can disable @everyone pings: at the server level for the @everyone role, at the server level for specific roles, and at the channel level for any role. Each method serves a different purpose. Server-level changes affect the entire server. Channel-level changes only affect that one channel. Understanding these options helps you choose the right approach for your server structure.

Steps to Disable @everyone Pings in Discord

Follow the steps below to disable @everyone pings using Discord permissions. These instructions apply to the Discord desktop app, the web version, and the mobile app. The menu layout is identical across platforms, though mobile may require tapping instead of clicking.

Method 1: Disable @everyone Pings for the @everyone Role (Server-Wide)

This method removes the ability for any member to use @everyone pings. It is the most effective way to stop all mass pings unless you explicitly grant the permission to another role.

1. Open Server Settings
   Click the server name at the top-left of the Discord window. Select Server Settings from the dropdown menu.
2. Go to the Roles tab
   In the left sidebar, click Roles. A list of all roles in the server appears.
3. Select the @everyone role
   Click on the @everyone role. This is the default role assigned to every server member.
4. Locate the Mention permission
   Scroll down to the General Permissions section. Find the permission labeled Mention @everyone, @here, and All Roles.
5. Disable the permission
   Click the green toggle switch next to the permission so it turns gray. This disables the permission for the @everyone role. The change saves automatically.

After this change, no member can use @everyone or @here pings. If you need certain members to still send mass pings, grant this permission to a specific role as described in Method 2.

Method 2: Disable @everyone Pings for a Specific Role

Use this method when you want to keep @everyone pings enabled for most members but disable them for a particular role, such as a temporary role or a restricted role.

1. Open Server Settings and go to Roles
   Follow steps 1 and 2 from Method 1.
2. Select the target role
   Click on the role you want to modify, for example, New Member or Guest.
3. Disable the Mention permission
   Scroll to the General Permissions section. Turn off Mention @everyone, @here, and All Roles.
4. Save changes if prompted
   On some Discord versions, a Save Changes button appears at the bottom. Click it to apply the permission change.

Members with this role will no longer be able to send @everyone pings, even if their other roles allow it. Permission conflicts are resolved by Discord in favor of the most permissive setting. If a member has two roles where one allows pings and the other does not, the member can still ping. To fully block pings for a member, disable the permission on all roles assigned to that member.

Method 3: Disable @everyone Pings in a Specific Channel

Channel-level permissions override server-level role permissions. Use this method to block @everyone pings in a single channel, for example, an announcements channel where only admins should ping.

1. Open the channel settings
   Right-click the channel name in the channel list. Select Edit Channel from the context menu.
2. Go to the Permissions tab
   In the left sidebar, click Permissions. You will see a list of roles and members with custom permissions for this channel.
3. Select the @everyone role or a specific role
   Click the @everyone role or the role you want to restrict. If the role is not listed, click the + icon and add it.
4. Disable the Mention permission
   Scroll to the General Permissions section. Find Mention @everyone, @here, and All Roles. Click the red X icon to set it to a disabled state. Do not leave it on the neutral gray slash — the red X means explicitly denied.
5. Save changes
   Click Save Changes at the bottom of the permissions list.

Now, even if a role has the @everyone permission at the server level, that permission is denied in this specific channel. This is useful for channels where you want to prevent any mass pings, such as a general chat or a support channel.

If @everyone Pings Still Appear After Disabling Permissions

After you disable the permission, you might still see @everyone pings in some cases. Here are the most common reasons and how to fix them.

Users with Multiple Roles Still Have the Permission

If a member belongs to two roles, and one role has the mention permission enabled, the member can still ping @everyone. Discord permissions are additive — the most permissive setting wins. To fix this, disable the mention permission on every role that the member has. Alternatively, create a dedicated role with the permission disabled and assign it to the member, then remove all other roles.

Server Boosters Retain the Permission

If your server has reached Level 1 or higher boost level, Discord automatically grants the @everyone role the mention permission in some cases. Check your server boost level by going to Server Settings > Server Boost. If boosters have the permission, you may need to manually disable it on the @everyone role as shown in Method 1. Booster-specific roles are not affected by this automatic grant.

Bots Can Still Ping @everyone

Bot accounts have their own permissions. If a bot has the mention permission, it can send @everyone pings regardless of role settings. To stop bot pings, go to Server Settings > Roles, find the bot’s role, and disable the mention permission there. Alternatively, configure the bot’s command settings to disable mass pings from within the bot’s dashboard.

Discord Permission Types for Mass Pings: Server Level vs Channel Level

Item	Server-Level Permission	Channel-Level Permission
Scope	Affects all channels in the server	Affects only the selected channel
Default state	Enabled for @everyone role	Inherited from server-level role
Override behavior	Cannot be overridden by channel settings if denied at server level	Can override server-level allowed permission by explicitly denying it
Best use case	Block all @everyone pings server-wide	Block pings in sensitive channels like announcements or support

Now you can control @everyone pings with precision. Start by disabling the permission on the @everyone role to block all mass pings. Then grant the permission only to roles that need it, such as Moderator or Admin. For channels that require extra quiet, use channel-level overrides. As an advanced tip, consider creating a role called “Ping Permitted” and assign it only to trusted members. This gives you a single role to manage rather than adjusting permissions on multiple roles.