How to Whitelist Bots, Users, and Channels in Discord Without Losing Protection
A whitelist in Discord security is a list of roles, users, or channels that a protection rule ignores. Discord itself has no whitelist feature. It comes from the security bot. In Security Bot you can whitelist per action (ban, kick, channel delete, bot add, and so on) or for everything. The right habit is per action, by role, reviewed monthly.
What whitelisting actually does
Anti-nuke counts dangerous actions per user and punishes the account when its count reaches a limit. A whitelisted account is skipped for the actions it is whitelisted for.
The invite link filter ignores channels, users, and roles whitelisted for Invite-Link. Beast Mode skips whitelisted users and roles only if you turn that option on. On Premium, anti-spam ignores channels in the Channels: Spam category, and Threat Link Guard and Mature Link Guard skip anyone or any channel in the All categories.
Anti-raid and verification do not use the whitelist at all. They apply to new joins.
Whitelisting is how you fix a false positive without turning a trigger off. Turning the trigger off removes protection for everyone. Whitelisting removes it for one role, one bot, or one channel.
Three whitelist types
| Type | Use it for | Example |
|---|---|---|
| Role | Your staff team | Admin role exempt from channel create and delete |
| User | One account without a shared role, or a bot | Ticket bot exempt from channel create |
| Channel | Places where a normally blocked action is expected | Partners channel exempt from the invite link rule |
Whitelist categories
Each entry goes into a category named after its type and action, such as Roles: Ban or Users: Bot-Add. The free categories cover the free triggers:
- All (Roles: All, Users: All, Channels: All): skips every check of that kind. Use it almost never.
- Ban, Kick: for an admin who must run native ban waves. This does not raise the cap on the bot's
/banand/kickcommands. - Channel-Delete, Channel-Create: for admins who restructure and bots that make channels.
- Role-Delete, Role-Create: for admins and bots that manage event or reward roles.
- Bot-Add: for the one admin allowed to add bots.
- Role-Update and Role-Add: Role-Update covers dangerous permission edits on roles. Role-Add covers handing out roles with moderation permissions. Be careful here.
- Prune and Invite-Link: for the rare account that prunes members, and for users, roles, or channels where invites are expected.
Premium adds categories for its extra triggers, such as Mention, Vanity, Server Rename, Channel Rename, Role Rename, Emoji Delete, Invite Delete, Channels: Webhook-Create, and Channels: Spam.
The one rule
Whitelist for the action, not the person. An admin whitelisted only for channel actions who gets phished can still be stopped by the ban limit.
What Discord gives you and what the whitelist adds
Discord has no whitelist because it has nothing to whitelist from. Native permissions are all or nothing: a role either has Manage Channels or it does not, with no limit on how many channels it may delete. Security Bot adds the limits, and the whitelist is the release valve for them.
Two kinds of account are exempt automatically: the server owner and anyone whose highest role sits above Security Bot's role. Do not use hierarchy as a whitelist. Keep the bot's role at the top so every staff account is covered, then exempt the actions you need one entry at a time. The trust page explains why role position matters more than the Administrator permission itself.
Whitelisting a bot
Bots are users to anti-nuke. A ticket bot that creates a channel per ticket will hit the channel create limit on a busy day. A leveling bot that hands out reward roles may trip Anti Admin Role Assign if a reward role carries a moderation permission.
Whitelist the bot's account for that one action. Keep the bot's role below Security Bot's so the exemption is the only thing protecting it, not hierarchy.
List what needs exemptions
Write down each role, bot, and channel that legitimately performs a protected action: the admin role deleting channels, a ticket bot creating channels, a partners channel with invites.
Whitelist roles per action
Exempt the admin role for channel and role actions only, not globally. Every whitelist command needs a category.
Command:
/whitelist add_role role:@Admin category:Roles: Channel-DeleteWhitelist utility bots
Exempt each bot for the one action it performs, for example a ticket bot for channel create.
Command:
/whitelist add_user user:@TicketBot category:Users: Channel-CreateWhitelist channels where invites belong
Exempt your partnerships channel from the invite link rule.
Command:
/whitelist add_channel channel:#partners category:Channels: Invite-LinkDecide on Beast Mode
On the Beast Mode page, leave Allow whitelist bypass off unless you are confident no whitelisted account could be the compromised one.
Review monthly
Remove entries for staff who left and bots you uninstalled. Each view command shows one category at a time.
Command:
/whitelist view_roles category:Roles: Channel-Delete
An example: a 3,000-member gaming server
This is an illustration. Say the server has:
- An Admin role held by three people.
- A Moderator role held by ten.
- A ticket bot that opens and closes a channel per ticket.
- A leveling bot that hands out reward roles.
- A partners channel where other servers post invites.
This is the whitelist that keeps every trigger on.
| Entry | Type | Categories | Why |
|---|---|---|---|
| @Admin | Role | Roles: Channel-Create, Roles: Channel-Delete | Admins restructure categories; the ban and kick limits still apply to them |
| @Admin | Role | Roles: Role-Create, Roles: Role-Delete | Admins manage reward and event roles |
| @TicketBot | User | Users: Channel-Create, Users: Channel-Delete | Opens and closes a channel per ticket, dozens per day |
| @LevelBot | User | Users: Role-Add | Only if a reward role carries a moderation permission; otherwise skip it |
| #partners | Channel | Channels: Invite-Link | Partner invites are expected here and nowhere else |
Notice what is missing. Nobody is whitelisted for Ban or Kick, so a phished admin who starts banning natively is punished when the count reaches the limit. Nobody is whitelisted for Bot-Add, so the owner adds bots and anyone below Security Bot who tries is punished on the first attempt.
The Moderator role has no entry at all. Moderators ban through Security Bot's moderation commands, which are capped at the ban and kick limits, and never touch channel or role limits in normal work.
Recommended whitelists by server type
Small community, under 500 members
One or two admins, no utility bots, everyone knows each other. You probably need no whitelist at all. Let the default limits do their job and only add an entry when the security log shows a trigger firing on routine work. If the owner does all the restructuring, nothing needs an entry, because the owner is always exempt.
Public gaming server
Ticket bots, temporary voice channel bots, and event roles are the usual sources of false positives. Whitelist each bot for the action it performs and the admin role for channel and role actions. Leave ban and kick on the limits, and pair the whitelist with verification so new accounts face a check before they reach your channels.
Crypto, NFT, or marketplace server
These servers are often attacked through their staff, so the whitelist should be as short as possible. No All entries, no Ban or Kick entries, and no Allow whitelist bypass on Beast Mode. Give one person Bot-Add and nobody else, and review the list weekly rather than monthly.
Commands and dashboard
Every whitelist entry can be managed from the Whitelists page under Access in the dashboard. On free servers you can also use the /whitelist commands: add_user, remove_user, add_role, remove_role, add_channel, remove_channel, and view_users, view_roles, view_channels.
Every one of them takes a required category. The add and remove commands also take the target, for example /whitelist add_role role:@Admin category:Roles: Channel-Delete. The view commands show one category, for example /whitelist view_roles category:Roles: Channel-Delete.
On Premium, settings are managed on the dashboard only, so the commands reply with a dashboard link.
There is no limit on the number of entries on any plan. The dashboard accepts up to 100 users per category, though the /whitelist add_user command has no such cap. A role is the better tool past that point anyway. Managing the whitelist needs Administrator and a role above Security Bot's, so with the bot's role at the top, that is usually only the owner.
How the whitelist fits with the other modules
- Anti-nuke is the main consumer. Every entry maps to one of its action categories, and a whitelisted account skips the count for that action only. See the anti-nuke page for the full trigger list.
- Beast Mode ignores the whitelist unless Allow whitelist bypass is on. With it off, a whitelisted admin's actions still add points, and while Beast Mode is active a whitelisted admin who deletes a channel is punished like anyone else.
- Anti Invite Link uses the Invite-Link categories. A channel whitelisted there can host invites; every other channel still has them deleted.
- AutoMod mostly does not use the whitelist. Each AutoMod preset has its own exempt roles and channels, set on the preset itself. The two bot-managed link guards, Threat Link Guard and Mature Link Guard, also skip users, roles, and channels in the All categories.
- Moderation commands have their own cap. While the Anti Ban and Anti Kick triggers are on,
/ban,/softban, and/kick(and/banidon Premium) are allowed up to the ban or kick limit per moderator per 10 minutes. The whitelist does not raise it. To allow more bot bans, raise the limit. - Anti-raid and verification never consult the whitelist. They act on new joins, and your staff are not new joins.
Mistakes that turn a whitelist into a hole
- An All entry for the whole staff role. One phished moderator and anti-nuke is off for them.
- Whitelisting a bot in Users: All. If the bot is compromised or malicious, it can do anything.
- Never reviewing. Former staff keep their exemptions through the role they still have.
- Whitelisting the whole team to dodge a limit. Whitelist the specific bot or role that performs an action in bulk, for that action only. If everyone on the team trips the channel delete limit in normal work, the limit is too low for your server: raise it a little instead of adding every staff role.
Troubleshooting
I whitelisted a role and the member was still punished
Check which action fired in the security log. Entries are per action, so a role whitelisted for Channel-Delete is still counted for Role-Delete. Open the Whitelists page, or run /whitelist view_roles with the category of the trigger that fired, to check the role's exemptions and add the missing one. If the punishment came from Beast Mode, Allow whitelist bypass is off and the whitelist did not apply.
The ticket bot keeps tripping a trigger
Most ticket bots create a channel when a ticket opens and delete it when it closes, which is two actions. Whitelisting the bot for Channel-Create alone leaves Channel-Delete counting. Add both. The same applies to bots that create and delete roles for events.
A whitelisted moderator still cannot run more /ban commands
The cap on /ban, /softban, and /kick ignores the whitelist. The command is refused until the 10-minute counter resets. Raise the ban or kick limit on the Anti-Nuke page if your team needs more.
A monthly review routine
Whitelists drift. Staff leave and keep the role for a while, bots get replaced, and a partners channel gets renamed and repurposed. Put fifteen minutes on the calendar once a month and go through the list.
- Open the Whitelists page under Access, or run
/whitelist view_users,/whitelist view_roles, and/whitelist view_channelsfor each category you use, and note every entry. - Compare user entries against the current staff list and Server Settings, Integrations. Remove anyone who left and any bot you uninstalled.
- Open the security log and look for triggers that fired on staff doing normal work. If one role or bot keeps firing a trigger, add an entry for it and that action. Raise the limit only if the whole team's normal volume is above it.
- Check role membership. A whitelisted role that now has thirty members is no longer a small exemption.
- Confirm Allow whitelist bypass on the Beast Mode page is still set the way you decided.
Glance at the security log weekly and do the full review monthly. The written security checklist has the rest of the quarterly review.
Do this with Security Bot
Discord Whitelist Bot: Exempt the people, roles, and channels you trust from specific protections without turning them off.
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.
Frequently asked questions
How do I whitelist a bot in Discord?
Discord has no native whitelist. In Security Bot, add the bot as a user entry for the specific action it performs, for example /whitelist add_user user:@TicketBot category:Users: Channel-Create, or on the Whitelists page.
Should I whitelist my admins globally?
No. Whitelist the admin role for the actions it performs in bulk, such as channel and role changes, so ban limits still protect against a compromised admin.
How many whitelist entries can I have?
There is no overall entry limit on any plan. The dashboard accepts up to 100 users per category. For more people than that, whitelist a role instead.
Does the whitelist affect Beast Mode?
Only if Allow whitelist bypass is enabled on the Beast Mode page.
Can I whitelist a channel for links?
For invite links, yes. Add the channel to the Channels: Invite-Link category and Anti Invite Link ignores invites posted there. Other links are handled by AutoMod rules, which have their own channel exemptions.
Does the whitelist exempt someone from AutoMod?
Mostly no. AutoMod presets have their own exempt roles and channels, set per preset. Only Threat Link Guard and Mature Link Guard also skip entries in the All categories. The whitelist covers anti-nuke, the invite link filter, anti-spam channels on Premium, and optionally Beast Mode.
Do I need to whitelist the server owner?
No. The owner and anyone with a role above Security Bot's role are exempt from every trigger automatically. That is why the bot's role should sit above all staff roles.
How this guide was made: drafted with AI assistance, then checked against Security Bot's source code and Discord's official help articles. Spotted something out of date? Tell us in the support server.