Make Discord verification clear for your members.

Connect verification to your own Discord application

Connect your bot in the Guardcord dashboard, invite it to your server and enable verification in the server settings. Configure the callback URL shown in the setup guide. Choose the channel where the bot can publish your verification message, and make sure new members can reach that channel.

If you assign a verified role, the bot needs Manage Roles and its role must sit above the role it assigns. Test with a permitted account before applying a restrictive channel layout to everyone. A verification message alone does not prove that the entire onboarding flow works.

Choose checks that fit your community

Server settings support an account-age requirement, optional CAPTCHA and community-specific firewall rules. Optional alt detection uses correlation signals that your team can review; a linked account or shared network is not proof of abuse. Review exemptions for households and legitimate returning members before taking an action.

Optional network protection and telemetry need their own configuration and consent where applicable. Availability depends on your plan and enabled settings. A verification flow reduces some onboarding friction and risk, but cannot guarantee that every account belongs to a trustworthy person.

Review the page before publishing

Use the server's verification page builder to edit the layout, text and appearance, preview the draft and publish the version you want members to see. Keep the community name and recovery permission understandable. Custom verification links and supported custom domains can help members recognize the destination.

Avoid asking for extra account information without explaining its purpose. Where optional Discord scopes are requested, members receive a separate consent choice. Protecting a community should not require members to guess what an authorization screen allows.

Follow verification outcomes in the dashboard

The member list helps your team review authorization health and verification outcomes. Use server-specific team permissions so staff only see communities they are allowed to manage. Link your onboarding message to the privacy page so members can find the withdrawal flow after verification.