Discord verification
Members press a Discord button, pass the browser challenge, and receive the configured role.
VeroRequest accessVero verifies Discord members with short-lived links, browser challenges, traffic-risk checks, optional Roblox proof, and operator audit trails.
Vero covers the verification path, the guild-owner workflow, and the operator controls behind it. The product stays small, auditable, and focused on access decisions.
Members press a Discord button, pass the browser challenge, and receive the configured role.
Enable Roblox OAuth when a guild needs linked Roblox ownership and account-age rules.
VPNs, proxies, Tor exits, hosting networks, repeat abuse, and active locks are blocked before roles change.
Guild owners configure roles, channels, rejoin behavior, account age, and message publishing.
System operators get audit trails, session detail, health checks, allowlisting, and scoped security locks.
Server admins get member, session, and audit data without raw IPs or proxy provider payloads.
The dashboard shows who verified, what failed, and which policy stopped a session. Raw IPs, user agents, provider JSON, lock tooling, and system-wide correlation stay restricted to named operators.
Members, role settings, sanitized session status, onboarding, and per-guild audit.
Raw session detail, IP-scoped locks, allowlisting, admin grants, health, and full audit.
No. The guild dashboard shows useful verification outcomes while raw IPs, user agents, and provider payloads stay in the system console.
The member presses the Discord verify button again. Verification links are single-use and expire quickly by design.
No. Each guild can run Discord-only verification or add Roblox OAuth and Roblox account-age checks.
Vero is invite-only. Request access in Discord, add the bot, and a system operator allowlists the guild.