Verification

Keep bots and raiders out by requiring new members to verify before they can see your server. Two modes: a simple button, or a web page with a Cloudflare Turnstile challenge.

Set it up

1. 1Open Verification and flip it on.
2. 2Pick the verified role members get once they pass.
3. 3Choose the mode — button, or Turnstile web verification for stronger protection.

Turnstile flow

With Turnstile on, members get a personal link to a QREATE page, solve a quick challenge, and the role is granted automatically. You can also set reminders and auto-kick for members who never verify.

Recommended protected-server flow

1. 1Give new members a locked-down gate role or no member role.
2. 2Show a public rules panel with a Verify button or instructions.
3. 3Require Turnstile for public/high-risk servers.
4. 4Grant the verified role after successful verification.
5. 5Send a welcome message only after verification if you want a clean onboarding sequence.

Anti-alt settings

• Warn - staff gets alerted but the member can continue.
• Block - verification is stopped when QREATE sees a matching risk signal.
• VPN/proxy checks - depend on platform configuration and should fail gracefully if unavailable.

Low-risk community:
Mode: Button
Verified role: @Member
Reminders: off

Public server:
Mode: Turnstile
Alt action: warn or block
VPN action: warn
Auto-kick unverified: 24-72h

Help members who get stuck

Open any member from the Members page to see a Verification panel showing exactly where they are in your flow — joined, stuck before agreeing to the rules, sent a link but not verified yet, or done. The steps adapt to how your server is set up (gate role, trigger role, or a verify panel). The most common place people get stuck is before agreeing to the rules.

• Remind about verification — DMs that member a nudge matched to their stage: how to agree to the rules, or their verification link again. It reuses their existing link, so it won't reset any auto-kick timer or clash with automatic reminders.
• Customize the wording: the paintbrush next to the button opens a panel where you can write your own reminder text per stage. Use {user}, {server}, {rulesChannel} and {link}; leave a box blank to keep the default message.
• {rulesChannel} points at whatever you pick under Channel for the {rulesChannel} tag. That is a separate setting from the rules panel channel on purpose: changing the panel channel moves the panel itself, while this one only changes what the tag says. If members agree to your rules through Discord's own rules screening, point the tag there and leave the panel where it is.
• Verify manually — grants the verified role (and any extra roles) on the spot, as if they'd agreed and passed. Use it only for people you trust: it skips the real check, and it's recorded as a manual approval (separate from members who passed the automated check) so your audit trail stays honest.