Verification
Guide members through identity verification and automatically update their access.
Verification gives members one clear path to access your server. Configure the
flow in Server settings → Verification, then send members to /verify or
add the Start Verification action to a template button.
Member journey
When a member runs /verify, Assistance shows the steps enabled for your
server and opens a guided page for them. A Roblox setup asks them to link their
Roblox account; browser, network, and CAPTCHA checks appear only when enabled.
Once the member finishes, Assistance applies the verified or unverified role you configured. Auto-nicknames apply to verified members.
Set up access
- Open Verification in your server dashboard.
- Choose the identity provider or checks members must complete.
- Enable a verified role, unverified role, or auto-nickname under Outcomes.
- Save the flow, then have a member run
/verifyto test it.
Role and nickname outcomes are unavailable until the flow includes an enabled identity provider, browser or IP check, or CAPTCHA.
Security and risk options
The verification editor includes controls for protecting high-risk flows. These settings are optional; choose the least restrictive configuration that meets your server's needs.
| Setting | What it does | Consideration |
|---|---|---|
| Browser continuity | Uses a browser identity as a verification signal. | Helps identify repeat verification from the same browser. |
| IP continuity | Uses a network signal as a soft indicator. | A network match is never sole proof of identity. |
| One account per network | Rejects a new verification when its browser or network was recently used by another Discord account. | Can block members on shared Wi-Fi, mobile networks, or VPNs; provide a moderator review path. |
| Signal retention | Sets how long hashed browser and network signals are kept, from 1 to 90 days. | Use the shortest period that supports your access policy. |
| Discord CAPTCHA | Requires a challenge before granting access. | Add it when automated or repeated verification is a concern. |
Assistance stores keyed hashes for browser and network signals, not the raw values. Expired verification signals are deleted automatically. See Risk and safety for how these indicators contribute to an advisory score and their limitations.
Auto-nickname variables
Nicknames use the same ${…} variable syntax as message templates. Variables
resolve using the member completing verification.
| Variable | Result |
|---|---|
${triggeredBy.links.roblox.username} | Roblox username |
${triggeredBy.links.roblox.displayName} | Roblox display name |
${triggeredBy.links.roblox.userId} | Roblox user ID |
${triggeredBy.displayName} | Discord display name |
${guild.slug} | Your server's Assistance slug |
For example, this template produces a Roblox display name followed by the member's Roblox username:
${triggeredBy.links.roblox.displayName} (@${triggeredBy.links.roblox.username})Use the Variables picker beside the nickname field to insert every
supported value. Legacy Bloxlink-style placeholders such as {roblox-name}
are not supported.
Discord nicknames are limited to 32 characters. Assistance shortens longer resolved values automatically.
How is this guide?