Verification System
Verification gates new members behind a panel they need to interact with before gaining full access to the server — a common defense against bot accounts and low-effort raids.
Setting it up
Verification is configured with the /setupverify set command, which lets
you choose from four named panel styles:
| Style | Tone |
|---|---|
| 🟢 Simple | A clean green button — minimal friction |
| 🔵 Professional | A blue embed that includes a rules reminder |
| 🛡️ Security | A stricter tone with an explicit warning |
| 🎨 Fancy | Colorful, styled with your server's branding |
Pick based on your server's risk profile
A small, invite-only community usually doesn't need the strictest panel. A large public server that's been targeted by raids before will benefit from the Security style.
Alongside the panel style, /setupverify set also lets you configure:
- The role assigned on verification
- An optional log channel for verification events
- Auto-kick unverified members after a set number of minutes (up to 60), useful for clearing out accounts that never complete verification
- A custom description shown on the panel itself, if you don't want the default wording
What happens on verification
- A new member joins and is placed into an unverified state (typically with restricted permissions until they pass the panel)
- They interact with the verification panel
- Once verified, NexaBot assigns the configured "verified" role, and normal channel access applies
Where to configure it
Panel style, the unverified role, and the verified role are all set through
/setupverify or the Nexa Dashboard.