Security

Verification and captcha

Publish the verification panel and configure roles, attempts and the new member experience.

On this page
Dashboard → Protection → Verification and captcha

In pictures

Verification panel configuration
Verification panel configurationOriginal image

Before you begin

Use captcha.manage. The bot must see the channel, send its panel and manage the relevant roles. These roles must be below Spider and not managed by an integration.

Step by step

  1. Create pending and verified roles, then configure their channel access in Discord.

  2. Open Protection → Verification. Select Image captcha or Discord Activity when available.

  3. Choose the panel channel, roles before and after verification and the maximum number of attempts.

  4. Adjust the available challenge, expiry and fallback settings, then enable and save.

  5. Publish or republish the panel. Test with a member account: opening the challenge, completing it and accessing channels.

Individual challenge

The challenge is temporary and tied to the member. Respect attempt and expiry limits: a public panel is not a shared server-wide code. Image captcha uses the offered private flow; the Activity opens a puzzle inside Discord.

Roles do not define channel access by themselves

Spider adds or removes configured roles. Category and channel permissions determine what each role can see. Check @everyone and other roles so pending members do not retain unintended access.

History and staff intervention

Review verification history and role errors. Where staff can manually verify a member, their permissions still apply. After verification, interactive onboarding can introduce the server and interest roles.

Questions and solutions

The captcha succeeds but channels remain hidden

Check the verified role, its position below Spider, category permissions and explicit denies on other roles. Then review any recorded role assignment error.

Activity mode is unavailable

Use the image captcha offered by the dashboard. Activity availability is managed by Spider; report unavailability to Spider support.

All documentation