To set up a verification bot, first make your member channels private in Discord and give a Verified role permission to see them. Keep a verification channel visible to newcomers, then configure the bot to give members the Verified role when they complete verification. In PeakBot, use the Verification page in the web dashboard to set up a button panel, optional questions, and unverified and verified roles.
Set up the access rules in Discord first
A verification panel only works as an access gate if your channel permissions support it. If newcomers can already read and write in your member channels, assigning a Verified role changes their label without controlling access.
Decide what someone should see before verifying: usually a welcome or rules channel and a verification channel. Keep the route short and explain what happens after they press the button.
1. Create a Verified role
In Discord, open your server menu, go to Server Settings → Roles, and create a role named Verified. The name is your choice, but something literal makes permission problems easier to understand.
Treat this as an access role. It does not need Administrator, Manage Server, or moderation permissions. Its job is to let an ordinary member see the community channels.
You can also create an Unverified role if you want a visible distinction between members who have completed verification and those who have not. Do not rely on that label alone to keep channels private. The underlying access permissions must work even before a newcomer receives a role.
2. Gate your member channels
For a category containing member channels, open Edit Category → Permissions. Deny View Channel for @everyone, then allow View Channel for your Verified role.
Check the channels inside the category too. A channel with its own permission overrides may behave differently from its category. Use category-synced permissions where you want the same access rules throughout.
Repeat this for other areas that should require verification. Pay particular attention to channels outside categories and channels with unusual overrides.
Also review any roles automatically given to newcomers. A role that grants access to member areas can undermine your verification gate. Keep cosmetic or interest roles separate from the decision about who can enter.
3. Leave a clear entrance visible
Create a channel such as #verify outside the gated member area, or give it an explicit permission setup that allows newcomers to view it. Keep any rules they need to read visible as well.
The verification channel should answer three questions:
- What must the member do?
- What access will that action unlock?
- Where can they get help if access does not appear?
For example: “Read the rules, then use the verification button below to unlock the community channels. If you cannot continue, contact a moderator.” Only include a help route that newcomers can actually use.
Keep unrelated conversation out of the entrance. A visible panel and a short explanation are more useful than a long welcome message that buries the next action.
4. Arrange the bot's role and permissions
When you add your chosen bot, check its position in Server Settings → Roles. A bot assigning roles needs Manage Roles, and its highest role must sit above the roles it needs to manage.
For this setup, place its role above Verified and Unverified. Also make sure it can access the verification channel and post the panel there.
Do not use Administrator as a shortcut for a role-order problem. Role hierarchy and channel access are separate things to inspect when a panel appears but members do not receive the intended access.
Finish the setup in PeakBot
PeakBot provides a verification panel with a button, optional questions, unverified and verified roles, and an auto-kick for members who never verify. We make PeakBot.
The dashboard path is peakbot.pro → your server → Verification. Verification is configured in the web dashboard, not through a setup command. Use the PeakBot wiki for its documentation.
5. Connect the verification roles
Open Verification for your server and configure the verified role to match the Verified role you created in Discord. Configure the unverified role if you are using one.
The distinction matters: the role selected in the dashboard must be the same role that has access to your member channels. Two similarly named roles can make the setup look correct while granting the wrong permissions.
Before continuing, compare the role selection with your Discord category permissions. The dashboard controls the verification workflow; Discord permissions determine what the resulting role can access.
6. Configure and publish the panel
Set up the verification button panel for your visible verification channel. PeakBot also supports optional questions. Use them when an answer serves a clear purpose for joining your community.
Keep any questions relevant and easy to understand. Avoid asking newcomers for personal information just to unlock ordinary community channels. A question about your server's expectations is easier to justify than collecting unrelated details.
Use the dashboard's preview before posting the panel. Check the wording, the destination channel, and whether the instructions make sense to someone seeing your server for the first time.
A button is an entry step, not proof of someone's identity or intentions. Continue to apply your community rules after members receive access.
7. Decide whether to use auto-kick
PeakBot can automatically kick members who never verify. Decide whether removing incomplete joins helps your community before enabling that behavior.
Some people join while busy, read the rules later, or need help understanding the instructions. Explain any removal policy in the entrance channel so it does not come as a surprise.
Auto-kick is not required to make your private channels private. The permissions you configured earlier provide that boundary. Use removal as a separate membership decision.
8. Review the complete access path
Check the intended before-and-after state: a newcomer should see the entrance, and a verified member should gain access to the member area. Review both text and voice channel permissions.
Do not judge visibility only from an administrator account, which can see areas ordinary members cannot. Inspect the permissions attached to the roles involved.
If access is wrong, follow the chain in order: visible entrance, correct dashboard role selection, bot role hierarchy, then category and channel permissions. Changing unrelated settings at once makes the cause harder to identify.
Frequently Asked Questions
Why can members see channels before verifying?
Look for access granted through @everyone, another role given on arrival, or a channel-specific permission override. Hiding a category is not enough if individual channels use different permissions. Verification needs to be the step that grants access, so remove unintended access paths.
Why does a member have the Verified role but still see no channels?
Confirm that the role receiving access in Discord is exactly the role selected in PeakBot. Then inspect the affected category and channel permissions. A role name alone does not grant access; the relevant permissions must be attached to that role.
What is the PeakBot verification setup command?
There is no setup command. Open your server in the PeakBot dashboard and select Verification. Configure the panel and roles there, and review the preview before posting.
Can I add questions to PeakBot verification?
Yes. PeakBot verification supports optional questions alongside its button panel. Keep questions focused on what a new member needs to understand or provide to join your community. Do not assume that answering a question establishes someone's real-world identity.
Does verification replace moderation or raid protection?
No. Verification controls the entry path, while moderation handles behavior and security controls address other threats. PeakBot lists Auto Moderation and Security separately from Verification. Configure those according to your server's needs rather than expecting a verification button to manage every safety problem.
