Verification
A gate new members pass before they can see the server.
A verification gate stops the cheapest kind of raid: fifty fresh accounts joining at once and posting the same link. It does not stop somebody determined. It stops volume, which is what raids are made of.
How it fits together
- 1Make a role - call it Member - and give it the permissions a normal member needs. This is the role verification hands out.
- 2Take those permissions away from @everyone, and make your channels visible to Member instead. This is the step people miss: if @everyone can still see the server, the gate is a door in an open field.
- 3Make a channel new arrivals can see. It should contain your rules and nothing else, and @everyone needs to be able to read it.
- 4Run /setup_verify with that role, that channel, and whether you want a CAPTCHA.
- 5Test it with a second account, or ask somebody. Getting this wrong locks out every new member and you find out from a DM two days later.
| Option | What it means |
|---|---|
role | What they get when they pass. Must be below the Arklynn role, or the bot cannot hand it out. |
channel | Where the verify panel is posted. Visible to @everyone. |
captcha_enabled | On: they solve an image before the role is handed out. Off: one button. Turn it on if you are being raided, leave it off otherwise - it is friction for every genuine member too. |
The Arklynn role has to sit above the verify role. If it does not, the button works, the bot tries, Discord refuses, and the member sees an error with no way to fix it themselves.
From the website
The Verification module holds the same three settings, plus a Post verify panel button - useful when the original message was deleted and you want a new one without reconfiguring anything.