Access Control

Discord Whitelist for Trusted Staff, Bots, and Channels

Security Bot's whitelist exempts trusted roles, users, and channels from specific protection triggers, for all actions or per action. Your admin team and utility bots keep working, while anti-nuke, Beast Mode, and the invite link filter stay on for everyone else.

  • Three whitelist types: users, roles, and channels.
  • Whitelist for all actions or per action, such as ban, channel delete, bot add, or invite links.
  • No entry limit on any plan. The dashboard holds up to 100 users per category.

Discord Whitelist Bot

Security Bot for Discord servers

Types
Users, roles, channels
Scope
All actions or per action
Entries
No limit; 100 users per category in the dashboard

Last reviewed 2026-10-12

Whitelist coverage

Discord Whitelist Bot features

Role whitelist

Exempt everyone with a role from one action or all actions. The recommended way to cover an admin team: change the role, not twenty user entries.

User whitelist

Exempt a single member, for example the owner's alt account or a trusted co-owner who does not hold the admin role.

Channel whitelist

Exempt a channel from the checks that run on messages posted in it, such as invite links in a partnership channel. Premium adds channel categories for webhook creation, @everyone mentions, anti-spam, and channel renames.

Why whitelists keep protection on

The wrong response to a false positive is to turn a trigger off. Whitelists let you keep anti-nuke, Beast Mode, and the invite link filter enabled. You exempt only the role, user, or channel that needs to do the thing the trigger watches. Everyone else stays covered.

Whitelisting by role is easier to maintain and easier to audit. Whitelisting for a specific action is safer than an exemption for all actions. Your admin role can be allowed to delete channels without also being allowed to add bots.

How whitelist categories work

Each entry belongs to a category. That is either an All category for users, roles, or channels, or a per-action one such as Roles: Ban, Roles: Channel-Delete, Users: Bot-Add, or Channels: Invite-Link.

Per-action categories cover ban, kick, channel create or delete, role create or delete, bot add, dangerous permissions, administrator roles, prune, and invite links, plus the Premium triggers.

A user whitelisted for channel delete can clean up channels without hitting that limit. They still count toward the ban limit.

Whitelist on free and Premium

The whitelist works on every plan with no entry limit. The dashboard holds up to 100 users per category, while /whitelist add_user on the free tier has no cap.

Free servers get categories for the ten free anti-nuke triggers and the invite link filter. Premium adds categories for its extra triggers, such as webhook creation, @everyone mentions, vanity changes, and renames, plus a channel category for anti-spam.

On Premium, the whitelist is managed in the dashboard, and the whitelist commands reply with a dashboard link.

Recommended whitelist setup by server type

A small community needs only a few entries. Whitelist your admin role for channel delete and channel create, since restructuring is the one bulk action a small team performs. Add the one bot that creates channels, such as a ticket bot, as a user entry for channel create only.

If you run a partners channel, add it to Channels: Invite-Link so the invite link filter leaves those invites alone. Leave ban, kick, and bot add with no entries at all. On a small server, nobody needs to do those in bulk.

A public gaming server with an active staff team and several utility bots needs more entries and more discipline. Whitelist the admin role for channel and role actions only, never for ban or bot add. Senior moderators get no entries, since the anti-nuke limits are sized for their normal work.

Add your leveling bot for the administrator roles action if a reward role carries administrative permissions. Add your ticket bot for channel create. Add any other moderation bot for the ban action if it bans in bulk alongside Security Bot, because its bans count toward your ban limit.

A server network or a community past ten thousand members runs staff tiers, and the whitelist should mirror them. Two or three admins hold channel and role actions through their role. Senior moderators and moderators hold nothing and moderate through Security Bot's per-user command permissions.

Review after every staff change. A former admin who keeps the role keeps the exemption until you remove one or the other.

A worked example on the free tier

Picture a community server with an Admin role, a ticket bot, and a partners channel. Three commands cover it.

Run /whitelist add_role with the Admin role and the category Roles: Channel-Delete, so admins can clean up categories without hitting the channel delete limit.

Run /whitelist add_user with the ticket bot and Users: Channel-Create, so it can open a channel per ticket on a busy day.

Run /whitelist add_channel with #partners and Channels: Invite-Link, so partner invites posted there are not deleted.

Everything else stays at the defaults. An admin who suddenly bans five people still reaches the ban limit, and anyone who adds a bot still hits Anti Bot Add.

Now test it. Have an admin delete three test channels and confirm no User Warning or User Punished entry appears in the security log. Have a member without an entry post an invite in general chat and confirm it is deleted.

Open the Beast Mode page and check whether Allow whitelist bypass is on. If it is, the admin role is also skipped while Beast Mode is active, which you may or may not want.

Finish with /whitelist view_roles, view_users, and view_channels so you can see exactly what is exempt and why.

Common whitelist mistakes and how to fix them

The mistake that causes the most damage is a Roles: All entry for the whole staff role. It feels convenient, but it means one phished moderator turns anti-nuke off for themselves. Replace it with per-action entries for the actions that role performs in bulk.

The second is whitelisting a bot for all actions because it kept tripping a limit. If that bot is compromised or malicious, it can now do anything. Whitelist it for the one action it performs. Keep its role below Security Bot's, so the exemption is the only thing protecting it, not hierarchy.

Two quieter mistakes build up over time. First, nobody reviews the list. Former staff keep exemptions through a role they still hold, and bots you uninstalled months ago still have entries.

Fix it with a monthly pass through the Whitelists page or the view commands, and a rule that staff changes include a whitelist check.

Second, some servers whitelist instead of fixing limits. If every admin trips the channel delete limit, the limit is too low for your team. Raise it a little first, then exempt only the people who really need more.

How the whitelist interacts with the rest of the stack

Anti-nuke is the main consumer. A whitelisted account is skipped for the actions it is exempt from and counted for everything else.

The invite link filter reads user, role, and channel entries for invite links. On Premium, Threat Link Guard and Mature Link Guard skip users, roles, and channels in the All categories.

Beast Mode reads user and role entries only while Allow whitelist bypass is on. It is set on the Beast Mode page. An All entry combined with that toggle removes the last layer meant to catch a compromised staff account.

Anti-raid and verification never consult the whitelist. They score and gate new joins only, and an existing member's exemptions have nothing to do with that.

Moderation commands are different. The cap on /ban, /softban, and /kick ignores the whitelist. To give a lead moderator more bot bans, raise the anti-nuke ban limit instead.

The Whitelists page and the whitelist commands are open to the server owner and to Administrators ranked above Security Bot. With the bot's role at the top, that is usually only the owner. Share a summary in the staff channel so exemptions are not hidden from the team.

Keep the security log open the first week after adding entries. Confirm the false positives you were fixing have stopped.

Setup

How to set up Discord Whitelist Bot

Steps that list a command can also be done in Discord. On Premium, settings commands such as /setlimit and /whitelist reply with a dashboard link instead.

  1. Step 1: Open Whitelists under Access

    The dashboard shows roles, users, and channels with one card per category. It is open to the server owner and Administrators ranked above Security Bot.

  2. Step 2: Add your admin role for the actions it needs

    Prefer per-action entries over Roles: All. Most admin teams need channel and role actions, not ban or bot add.

    Command: /whitelist add_role role:@Admin category:Roles: Channel-Delete

  3. Step 3: Add utility bots

    Whitelist bots that legitimately create channels or roles for the specific action they perform. On Premium, a bot that creates webhooks can be exempted by adding its channel to Channels: Webhook-Create.

  4. Step 4: Whitelist partner channels

    Exempt a channel where invites are expected so the invite link filter does not delete them.

    Command: /whitelist add_channel channel:#partners category:Channels: Invite-Link

  5. Step 5: Review the list monthly

    Remove entries for staff who left. Check with the view commands or the Whitelists page.

    Command: /whitelist view_roles

Command reference

Discord Whitelist Bot commands

Slash commands you can run in Discord. Moderation commands work on every plan; on Premium, settings commands reply with a dashboard link instead.

CommandWhat it does
/whitelist add_user user category
Exempt a member from one action, such as Users: Bot-Add, or from all actions with Users: All.
/whitelist remove_user user category
Remove a member's exemption.
/whitelist add_role role category
Exempt a role from one action, such as Roles: Channel-Delete, or from all actions with Roles: All.
/whitelist remove_role role category
Remove a role's exemption.
/whitelist add_channel channel category
Exempt a text channel, for example from the invite link filter with Channels: Invite-Link.
/whitelist remove_channel channel category
Remove a channel's exemption.
/whitelist view_users category
List the users whitelisted in a category.
/whitelist view_roles category
List the roles whitelisted in a category.
/whitelist view_channels category
List the channels whitelisted in a category.

Questions

Discord Whitelist Bot FAQ

Common questions about Discord Whitelist Bot use cases, coverage, and setup.

Should I whitelist users or roles?

Roles. They are easier to manage and audit. Use user entries only for individuals who do not share a role.

Does a whitelisted admin bypass everything?

Only the actions you whitelisted. An All entry bypasses every anti-nuke check, so prefer per-action entries.

How many whitelist entries do I get?

There is no entry limit on any plan. The dashboard holds up to 100 users per category. For more, whitelist a role and give it to them.

Does the whitelist apply to Beast Mode?

Only when Allow whitelist bypass is enabled on the Beast Mode page.

Can I whitelist a channel for invite links?

Yes. Add the channel to Channels: Invite-Link and the invite link filter ignores invites posted there.

Do bots need whitelist entries?

Only bots that perform a protected action in bulk, such as a ticket bot creating channels. Add the bot as a user entry for that one action and keep its role below Security Bot's.

Can other admins see the whitelist?

The Whitelists page and the whitelist commands need Administrator and a role above Security Bot's role. If Security Bot's role is at the top, only the server owner can view and change the list. Share a summary in the staff channel so exemptions are not hidden from the team.

Does whitelisting raise the ban limit for moderation commands?

No. /ban, /softban, and /kick through Security Bot are capped at the anti-nuke ban and kick limits regardless of the whitelist. Raise the limit if a moderator needs more.

Whitelist

Ready to protect your Discord server with Security Bot?

Add Security Bot to your server to get started with Discord Whitelist Bot. Anti-raid, anti-spam, and the other Premium modules run on a separate bot; the Premium page explains how to add it.