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 command, which lets you
choose from four panel styles. Each style trades off friction against
strictness — a lighter panel is faster for genuine members but easier for a
bot to pass; a stricter panel filters more aggressively but adds friction
for everyone.
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 a stricter option.
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.