To set up verification with Security Bot, start by creating the role new members are held in. Then drag Security Bot's role above that role in Server Settings > Roles. Lock every category so the held role can see only one verification channel, then run Security Bot's verification setup in that channel to post the panel. When this fails, the cause is usually Discord's permission rules rather than the bot: the bot's role sits too low, or another role has an "allow" that overrides your lock.
Checked on each bot's own site or docs on 3 November 2026. We make PeakBot. Nobody paid to be in this post.
This guide covers Security Bot, the security and verification bot whose verification commands start with /verification. Some other bots have almost the same name, and search summaries sometimes give their instructions as if they were Security Bot's. If a guide tells you to use a command that doesn't come up when you type / in your server, it was probably written for a different bot. Security Bot's command names and options have changed over time, so check its own documentation or dashboard for the exact commands. Everything on the Discord side below works the same whichever bot you use.
Before you start: pick a model
There are two ways to gate a server. Choose one before you change any permissions:
- Unverified-role model. The bot gives each new member an "Unverified" role when they join. That role is denied View Channel everywhere except the verification channel. When the member passes the check, the bot removes the role.
- Verified-role model. @everyone can't see anything except the verification channel. When a member passes the check, the bot gives them a "Verified" role, and only that role can see the rest of the server.
The Verified-role model is harder to break. If you create a channel and forget to lock it, unverified people still can't see it, because @everyone has no access by default. The Unverified-role model is easier to add to a server that already exists, but you have to lock every new channel yourself. Find out which model Security Bot's setup expects and build your roles to match.
Steps in Discord
-
Invite Security Bot with the permissions it needs. It needs Manage Roles to add or remove the role. In the verification channel it also needs View Channel, Send Messages and Embed Links to post its panel. If your server requires two-factor authentication for moderation, Discord's permissions documentation says the bot's owner account must have 2FA turned on before the bot can use Manage Roles. You can't fix that from your end, but it explains some failures that otherwise make no sense.
-
Create the role. Go to Server Settings > Roles > Create Role. Name it "Unverified" or "Verified", depending on your model. Leave all of its server-wide permissions off. All of its access will come from channel settings.
-
Fix the role order. Still in Server Settings > Roles, drag Security Bot's role above the Unverified or Verified role. A bot can only give or remove roles that sit below its own highest role. If the bot's role is below the verification role, the panel can look like it works while members never get through.
-
Lock your categories. For each category, open Edit Category > Permissions.
- Unverified-role model: add the Unverified role and set View Channel to the red X.
- Verified-role model: set View Channel for @everyone to the red X, then add the Verified role and set View Channel to the green check.
Next, open each channel inside the category. If Discord says its permissions aren't synced with the category, click "Sync Now".
-
Look for allows that override the lock. Most guides skip this step. Discord applies channel overwrites in a fixed order: @everyone deny, @everyone allow, role deny, role allow, member deny, member allow. These do not follow role position. If a member has the Unverified role (denied) plus any other role that allows View Channel in that channel, the allow wins, however the roles are ordered. That means some guides are wrong when they say putting Unverified higher in the list makes it restrict access. Check for auto roles from other bots, roles given by Discord Onboarding, and old "Member" roles that have explicit allows on channels.
-
Set up the verification channel. Create a channel such as #verify. Let the gated role (or @everyone, in the Verified-role model) view it and read message history, but turn off Send Messages so the channel only shows the bot's panel. Make sure Security Bot itself can view the channel, send messages and embed links there.
-
Run Security Bot's verification setup. Use Security Bot's verification commands or its dashboard, following its own documentation. Point it at the role from step 2 and the channel from step 6, pick one of the check types it offers, and post the panel. The current docs also describe a fallback page for members who can't use the panel and a command for verifying someone by hand. Note where both are before you need them.
-
Set Discord's own Verification Level. Go to Server Settings > Safety Setup. The levels are None, Low (verified email), Medium (verified email and an account older than 5 minutes), High (Medium plus 10 minutes in the server) and Highest (verified phone). Older guides call one of these "Moderate" and put it under a "Moderation" menu. The level is now called Medium, and Discord's safety page puts it under Safety Setup. Medium works well alongside a bot check because it stops brand-new throwaway accounts before they reach your panel.
-
Go through it with a second account. Join on an alt and confirm three things: you see only #verify, the check works, and the whole server appears afterwards. Doing this on your own account tells you nothing, because the server owner and anyone with Administrator ignore channel overwrites.
Common failures and fixes
Unverified members can see channels. Work through these in order. Does the member have another role that allows View Channel in that channel (step 5)? Is the channel out of sync with its category? In the Unverified-role model, was the channel created after setup? Do they have a role with Administrator?
The bot won't add or remove the role. Either its role sits below the verification role (step 3), or it doesn't have Manage Roles. At the channel level the Discord app calls this permission "Manage Permissions", so a channel-level deny can catch you out. Also check the 2FA rule from step 1.
The panel button does nothing or shows an error. The bot can't see the channel, can't send messages there, or is offline. Open the channel's permissions and check Security Bot's role directly.
New channels leak. This is an Unverified-role model problem. Either create new channels inside a locked category and keep them synced, or switch to the Verified-role model.
Two bots fight over the role. If another bot gives out an auto role on join, or also runs verification, the two can undo each other's changes. Give verification to one bot only. For more on choosing an approach, see our verification bot setup guide and our post on stopping bots and scam DMs with a verification gate.
How PeakBot does it
We make PeakBot, so read this section as one option among several. If Security Bot already works for you, there's no need to switch.
PeakBot's verification is set up on the web dashboard, and there is no setup command for it. Go to peakbot.pro, choose your server, and open Verification in the sidebar. From there you can:
- post a panel with a button
- add optional questions members answer before they get in
- choose an unverified role and a verified role, so either model above works
- turn on an auto-kick for anyone who never verifies, so half-joined accounts don't pile up
Verification is available on the free plan. The Discord rules above still apply to it: PeakBot's role has to sit above the roles it manages, and allow overwrites on other roles can still expose channels.
Next to it, the Security page deals with raids rather than single joins. It has join-rate and account-age limits, a quarantine role, auto-unlock, a whitelist and a threat log. The welcome, roles and verification wiki page and the security and backups page explain each setting.
PeakBot doesn't have a captcha image check. If that's what you want, read our captcha verification guide.
Frequently Asked Questions
Why can my unverified members still see all my channels?
Usually another role they have allows View Channel on those channels. Channel overwrites don't follow role order, so any role allow beats a role deny. Also check that those channels are synced with their locked category and that nobody has Administrator.
Why won't Security Bot remove the unverified role?
Security Bot's highest role must sit above the Unverified role in Server Settings > Roles, and the bot needs Manage Roles. If your server requires 2FA for moderation, the bot's owner account also needs 2FA.
Do I need to redo verification every time I make a new channel?
In the Unverified-role model, yes. Every new channel has to be locked, or created inside a locked category and synced. In the Verified-role model, new channels stay hidden from @everyone by default, so nothing leaks.
What if someone can't complete the check?
Make sure there's a manual route. A moderator can right-click the member, open Roles, and add the Verified role or remove the Unverified one by hand. Put a pinned message in #verify that says who to contact.
Which Discord verification level should I use with the bot?
Medium suits most public servers. It requires a verified email and an account older than 5 minutes, which stops the newest throwaway accounts. High adds a 10-minute wait in the server. Highest requires a verified phone, which blocks more raiders but also turns away some real people.
Can I use Security Bot alongside Discord Onboarding or another verification bot?
You can use Onboarding, but make sure the roles it assigns don't allow View Channel in your gated channels. Two verification bots working on the same roles usually conflict, so pick one.
