Verification

How to Make a Verify Channel and Verify Button in Discord

A Discord verify channel is visible only to unverified members. Passing its button or captcha removes their Unverified role. You need the Unverified role, permission overwrites that hide the server from it and show it the verify channel, and a bot that removes the role. Security Bot creates the role and channel with two commands and posts the button.

By Sina, Founder, Security BotUpdated (published )9 min read

How a verify channel works

The trick is permissions, not the button. New members receive an Unverified role. Every channel carries a permission overwrite that denies that role View Channel, and one channel, the verify channel, has an overwrite that allows it.

When the member verifies, the role is removed and those overwrites stop applying to them. The verify channel vanishes, and the channels their remaining roles can see appear.

That is also why the channel disappears after verification without any extra setup. The member simply stops matching the only role that was allowed to see it. Role order plays no part in what the member sees. Discord applies channel overwrites regardless of where the roles sit in the list.

Step 1: Create the Unverified role

  1. Open Server Settings > Roles and click Create Role. Name it Unverified.
  2. Leave its permissions in the Permissions tab switched off. Role permissions can only grant access. They cannot take away what @everyone already has, so the restrictions go on the channels in the next step.
  3. Keep the role below Security Bot's role so the bot can add and remove it. Its position relative to your member roles does not matter.

If you use Security Bot, /verification setup_role creates the role and adds the View Channel denial for it on every channel in one step: text, voice, announcement, forum, stage, and media.

Step 2: Create the verify channel

  1. Create a text channel named #verify (or #verification).
  2. Open Edit Channel > Permissions and add the Unverified role. Allow View Channel and Read Message History. Deny Send Messages unless members answer a captcha in the channel. With Security Bot's Captcha code type they run /verify there, so also allow Use Application Commands. Security Bot's own setup allows Send Messages too in that mode.
  3. For @everyone on this channel, deny View Channel so verified members do not see it either.
  4. On every other channel, make sure Unverified cannot see it: deny View Channel to Unverified, or deny it to @everyone and allow it only for your member role. A channel copies its category's permissions only while it is synced, so a channel with its own overwrites needs checking on its own.

Step 3: Add the verify button

Discord does not have a native verify button. A bot posts it. With Security Bot, set the verification type to One-click verification on the dashboard and the button appears in the verify channel. Pressing it removes Unverified and adds your Verified role if you set one.

If you want more than a button, switch the type to Adaptive, Captcha code, or Web check. With Captcha code, the member presses Verify, gets a code image only they can see, and answers with /verify. The web check opens a personal link and finishes in about 5 seconds. Adaptive picks one of these per member. The channel and role setup stays the same.

Full setup with Security Bot

  1. Create the Unverified role

    With Security Bot invited, run the setup command or press Create role on the Verification page. The bot creates the role and adds a channel overwrite denying it View Channel on every channel. That covers every type: text, voice, announcement, forum, stage, and media.

    Command: /verification setup_role

  2. Create the verify channel

    The bot creates a channel that the Unverified role can see and @everyone cannot.

    Command: /verification setup_channel

  3. Choose one-click verification

    On the Verification page set the type to One-click verification. Security Bot posts a message with a Verify button in the channel.

  4. Check the role order

    In Server Settings > Roles, keep Security Bot's role above Unverified and above the role you use as Verified. Then the bot can remove one and add the other. Where Unverified sits among your member roles does not affect what it can see.

  5. Enable the module

    Turn verification on. New members now get the Unverified role on join and see only the verify channel.

    Command: /verification enable

  6. Test with an alt

    Join with another account, press the button, and confirm the channel disappears and the rest of the server appears.

On Premium servers, these settings are dashboard-only. The setup commands reply with a link to the Verification page, where the same steps are buttons. Free servers can use either.

Step 4: Give new members the Unverified role automatically

A verify channel is useless if new members do not receive the Unverified role on join. Security Bot assigns it automatically while verification is enabled. The exceptions are members with Administrator and anyone ranked above its own role.

If you built the role gate by hand with another bot, configure its autorole feature to add Unverified on member join. Do not hand out any other role that is allowed into channels at the same time.

How to make the verify channel disappear after verification

Nothing extra is needed if the channel is visible only to the Unverified role. The moment the role is removed, the channel is gone for that member. If the channel stays visible, one of these is wrong:

  • @everyone can view the channel. Deny View Channel for @everyone on the verify channel.
  • A Verified or member role has an allow overwrite on the verify channel. Remove it.
  • The bot did not remove the Unverified role. Check that the bot's role sits above Unverified in the role list. Bots cannot remove roles above their own.

Worked example: a 500-member gaming server

Here is an example layout for a mid-sized community. Change the names, keep the structure.

  • Roles, top to bottom: Security Bot, Admin, Moderator, Member, Unverified, @everyone. Security Bot sits above both Member and Unverified, so it can swap them. The order of Member and Unverified makes no difference to what anyone sees.
  • Category `Start Here`: contains #verify and nothing else. Unverified is allowed View Channel and Read Message History. @everyone is denied View Channel.
  • Every other category: @everyone is denied View Channel and Member is allowed it, and the channels inside stay synced. An unverified member holds only @everyone and Unverified, so none of these channels is visible to them.
  • Verification settings: one-click verification, Verified role set to Member with /verification set_verified, and the Discord verification level at Medium as the baseline under the gate.

A new member joins, receives Unverified, and sees one channel with the verify message and its button. They press it, Unverified is removed, Member is added, and the rest of the server appears. The setup guide walks through the rest of the bot in the same order.

Which prompt should the channel use?

ServerVerify channel contentWhy
Small community, under 1,000 membersOne-click button, or Adaptive on RelaxedReal members want little friction; accounts that only post never get in
Public gaming or fan server, 1,000 to 20,000Adaptive on BalancedEstablished members get straight in; new accounts read and type a code
Crypto, NFT, marketplace, or 20,000+ publicAdaptive on Strict, or the web check, with VPN and alt blockingRisky joins get a browser check that can block VPNs and repeat devices

Switching later is a dashboard change, not a rebuild. The role and channel stay the same. Security Bot updates the Unverified overwrite on the verify channel and the prompt posted in it.

If you built the channel by hand and switch to Captcha code, make sure Unverified can use application commands in #verify so members can run /verify. Test with an alt. The captcha guide covers the code length and timeout settings.

Troubleshooting the verify button

  • The button does nothing. Check that Security Bot is online and that its role is above Unverified. If the role order is wrong the bot cannot remove the role, and the press fails from the member's point of view.
  • Members cannot see the button. Unverified needs Read Message History on #verify. Without it the channel looks empty.
  • Members verify but stay locked out. A category or channel denies View Channel to @everyone without an allow for the role they now hold. Compare what a verified alt sees with what a moderator sees.
  • Nobody gets a Verified role. You have not set one. Run /verification set_verified and pick the role, or rely on @everyone being able to see channels once Unverified is gone.
  • New channels are visible to unverified members. Run /verification update_role after each channel you add, of any type. The bot adds the Unverified denial to channels that do not have it yet.
  • Everything is tangled. /verification reset deletes the Unverified role and the verify channel and turns verification off. Run the two setup commands again for a clean gate.

What a verify channel does not do

The gate stops accounts from posting. It does not stop them from joining, and a person behind an account presses a button as easily as you do. Other layers cover those gaps:

  • Discord's own Raid Protection (Server Settings > Safety Setup > Raid Protection and CAPTCHA) detects join raids and sends Activity Alerts. On Premium, Security Bot's anti-raid adds join scoring by account age, join speed, and missing avatar. It times out or bans the accounts that joined during the raid, and locks the channels you choose.
  • AutoMod presets on Premium catch scam links and mention spam from anyone who verifies and then misbehaves.
  • Anti-nuke limits what a compromised moderator can do, which no verification setup touches.

Verification passes are not written to a log channel, but web check denials and possible alt accounts go to the security log. Anti-raid posts its channel lock to the security log, and anti-nuke posts its warnings and punishments there. Assign that channel on the Logging page.

Doing this on Discord mobile

Every step works on mobile. Roles are under Server Settings > Roles. Channel permissions are under the channel's Edit Channel > Permissions screen. Security Bot's dashboard at securitybot.gg is mobile-friendly, and the slash commands run from the mobile app like any other command.

Verify channel checklist

  • Unverified role exists and sits below Security Bot's role.
  • Every channel except #verify denies View Channel to Unverified (or to @everyone, with an allow for members).
  • #verify allows Unverified, and @everyone cannot view it.
  • New members receive Unverified on join and no other role that is allowed into channels.
  • Passing verification removes Unverified (and adds Verified if used).
  • Run /verification update_role after adding new channels of any type.

Do this with Security Bot

Discord Verification Bot: Gate new members with Adaptive Verification, an image captcha, a no-click web check, one button, a passcode, or an allowlist.

Security Bot is a Discord verification bot that keeps new members behind an Unverified role until they pass. Adaptive Verification picks the check per member: low-risk accounts get straight in, others get an image captcha or a 5-second web check. When joins spike, it raises the bar on its own. Passing removes the role and can add your Verified role.

Frequently asked questions

How do I make a verify button on Discord?

A bot has to post it. With Security Bot, set the verification type to One-click verification and the button appears in your verify channel.

How do I make an Unverified role in Discord?

Create a role named Unverified with no permissions, and keep it below your bot's role. Use channel overwrites to deny it View Channel on every channel except the verify channel. Security Bot does this with /verification setup_role.

Why can unverified members still see my channels?

A channel allows View Channel to @everyone or to another role the member holds, or the channel has its own overwrites and no longer follows a category that denies it. Role order does not affect this. Check the overwrites.

How do I make the verification channel disappear after verification?

Allow View Channel on it only for the Unverified role and deny it for @everyone. When the role is removed, the channel disappears.

Can I do this on mobile?

Yes. Roles and channel permissions are available in the mobile app, and Security Bot commands and dashboard work on mobile.

Can I use a reaction instead of a button?

Reaction-role bots can remove Unverified on a reaction, but a script adds a reaction as easily as a person. A button is cleaner, and a captcha or web check raises the cost more. All of them use the same channel setup.

Should unverified members be able to send messages in the verify channel?

Only for a captcha that is answered in the channel. With Security Bot's Captcha code and Adaptive types, members may run /verify there, so the bot allows Send Messages and Use Application Commands. For one-click and the web check, deny Send Messages so the channel stays clean.

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.