Security
Verification
Rule acceptance, account age, explainable risk signals and manual review.
AvailableAlways free
Verification
Example recreation of what the bot does in Discord: the names, the server and the numbers are made up.
What it does
Newcomers press “Verify me” and accept your rules before they can see the server. If an account looks off, like a default avatar or a name almost identical to others that just joined, it goes to review and your staff decides.
- Optional captcha with three difficulty levels
- Explained risk score: account age, avatar, similar names, raid and history
- New-account filter: kick, ban, timeout, quarantine, review or log only
- Observation mode: approves everyone and records what it would have decided
- Optional alt-account detection on the web, with a notice shown first
Commands
Type / in Discord and they show up by themselves. Verification has 20:
| Command | What it does | Who can use it |
|---|---|---|
/newaccounts setdaysDashboard | Minimum account age (1 hour to 365 days) | Staff By default, anyone with the permission: Manage Server. |
/newaccounts setactionDashboard | What happens to recent accounts | Staff By default, anyone with the permission: Manage Server. |
/newaccounts setchannelDashboard | Log channel | Staff By default, anyone with the permission: Manage Server. |
/newaccounts settingsDashboard | Show the configuration | Staff By default, anyone with the permission: Manage Server. |
/newaccounts resetsettingsDashboard | Reset the filter settings (the bypass list is kept) | Staff By default, anyone with the permission: Manage Server. |
/newaccounts toggleDashboard | Turn the filter on or off | Staff By default, anyone with the permission: Manage Server. |
/newaccounts bypass | Allow a specific account to join while the filter is active | Staff By default, anyone with the permission: Manage Server. |
/newaccounts disallow | Remove an account from the bypass list | Staff By default, anyone with the permission: Manage Server. |
/newaccounts allowed | List the bypass entries | Staff By default, anyone with the permission: Manage Server. |
/newaccounts recent | Current members whose account is younger than N days | Staff By default, anyone with the permission: Manage Server. |
/newaccounts nopfp | Members using the default avatar | Staff By default, anyone with the permission: Manage Server. |
/newaccounts history | Accounts the filter acted on | Staff By default, anyone with the permission: Manage Server. |
/whois | Account facts and explainable risk signals | Staff By default, anyone with the permission: Timeout Members. |
/verification setupDashboard | Roles and channels | Staff By default, anyone with the permission: Manage Server. |
/verification publish | Post the verification panel | Staff By default, anyone with the permission: Manage Server. |
/verification rulesDashboard | Edit the rules text | Staff By default, anyone with the permission: Manage Server. |
/verification modeDashboard | Observation, captcha, confirmation and risk threshold | Staff By default, anyone with the permission: Manage Server. |
/verification toggleDashboard | Turn verification on or off | Staff By default, anyone with the permission: Manage Server. |
/verification queue | Pending manual reviews | Staff By default, anyone with the permission: Manage Server. |
/verification status | Configuration checks | Staff By default, anyone with the permission: Manage Server. |
“Who can use it” is each command’s default permission. Administrators can change it in Discord: Server Settings → Integrations → Garita.
Commands marked “Dashboard” set up the same thing as a dashboard page. Discord hides them until you turn on “Setup commands in Discord” in the server settings, inside the dashboard.
Safe by default
Before Verification does anything in your server, all of this holds:
By default, its staff commands ask whoever runs them for a Discord permission: Manage Server, Timeout Members.
Garita checks its own permissions before it switches on and before every action. For Verification it needs: Manage Roles, Send Messages, Embed Links. Its optional features also ask for: Kick Members, Ban Members. They are checked when used, not before.
It respects the role order: Garita does not act on a member or touch a role that is level with its own role or above it.
It refuses to hand out a role that carries dangerous permissions, such as mentioning @everyone, kicking or managing the server.
It starts switched off: it does nothing in your server until you turn it on.
Changing its settings in the dashboard is reserved for your team’s administrators and asks for confirmation.
It is on record: what it does is written to Garita’s audit log.
Two reasons to use it
Brand-new account filter
Choose how old a Discord account must be to get in, and what happens if it isn’t: remove it, time it out or review it by hand.
Decisions that can be explained
Each risk signal is stored with its reason and your team sees it when reviewing. Account age is treated as a signal, not as proof.
Live demo
A simulated server in your browser, focused on this feature. It starts by itself when you get here; then you can try it yourself.
moderatorsStaff only: settings and reviews.
The staff channel. In this sandbox the new-account filter is already on and acting (a new server starts in observation mode) and reports to . Alt-account detection is on as well; Roko was banned 3 days ago. Change the minimum or the action and see what happens to each account.
A simulation in your browser: it does not connect to Discord or store anything. The server “Club Aurora”, its members (Nora, Mateo, Luna…) and their numbers are examples; the replies use the same texts and the same rules as the bot.
How it works
Set the roles and channels with /verification setup and post the message with the button using /verification publish, or do it in the dashboard.
Choose the rules, whether people confirm with a button or by typing a phrase, the captcha, and the risk level from which a case goes to manual review.
The member presses “Verify me”, accepts and gets the role; doubtful cases reach your team with their reasons and buttons to approve or reject.
Frequently asked questions
Does verification store my IP or device fingerprint?
Normal verification in Discord collects no IP or fingerprint. Only alt-account detection, which each server turns on deliberately, works on the web after a notice and stores codes only, not the plain IP; they are deleted after 30 days by default (90 at most).
How many tries does the captcha allow?
Three tries and five minutes per image. You answer in a form and it is not case-sensitive; asking for a new captcha replaces the previous one.
Is Verification free?
Yes, and it will stay that way: Verification is part of Garita’s security, which is free on every plan.
See the plansWhich permissions does Verification need?
In Discord, Garita needs: Manage Roles, Send Messages, Embed Links. Only for its optional features: Kick Members, Ban Members.
Which permissions each feature needsDoes it work in my language?
Garita answers in 10 languages: Español, English, Français, Deutsch, Português (Brasil), Türkçe, Русский, 한국어, 繁體中文, العربية.
Can I bring my settings from another bot?
Yes. The migration assistant looks in your server for what your previous bot left behind and offers to copy it to Verification. You choose what gets applied.
How migration worksSet up your server with Garita. The essentials are free.
One bot for your community’s security, moderation and everyday life.

