Roblox identity verification: the backend landed
Servers can now verify that a Discord account belongs to a Roblox account — guild-scoped configuration, a member-facing verification flow that stores no Roblox tokens, and an audit trail for every role write.
The verification backend shipped on 12 November 2026. It connects a member's Discord account to their Roblox account so a server can assign its Verified and Unverified roles automatically.
What it stores — and deliberately doesn't
Verification stores identity, not credentials: the Roblox link and its status lifecycle, with no Roblox OAuth tokens held or logged. Configuration (the Verified and Unverified roles, the assign-unverified flag) is per server and Manage-Guild-gated; members see their own verification status only.
Role writes go through the bot token with a bounded retry, and every write is audited. If a role write partially fails, the record says so instead of pretending it succeeded. The dashboard's Verification settings area is the place to configure it; the member-facing status page lives in each server's workspace.