---
title: "Verification"
slug: "verification"
category: "Servers"
order: 2
description: "Configure Roblox-to-Discord verification, member roles, branding, and account-safety checks."
---

# Verification

Verification connects a Discord member with their Roblox account. CADLY uses that connection to apply server roles and nicknames, resolve ER:LC players to Discord members, and support dispatch and server automations.

This guide is for server owners configuring verification. Members only need to open the verification link or panel button, sign in to Roblox, and return to CADLY.

## Contents

| Section | What it covers |
|---|---|
| [Before you start](#before-you-start) | Permissions and role hierarchy |
| [Set up verification](#set-up-verification) | Core roles, nickname, and join settings |
| [Member flow](#member-flow) | What happens when someone verifies |
| [Panel and page](#panel-and-page) | Sending and branding the verification experience |
| [Account safety](#account-safety) | Alt-account detection and its safeguards |
| [Commands](#commands) | Refreshing and inspecting links |
| [Troubleshooting](#troubleshooting) | Common configuration problems |

## Before You Start

Enable verification from **Server Settings → Verification**. CADLY needs permission to manage the configured roles and nicknames. Place the CADLY bot role above every role it needs to add or remove; Discord will reject changes to roles at or above the bot's highest role.

Choose an onboarding model before configuring roles:

- Use a **verified role** to grant normal member access after a successful link.
- Use an **unverified role** to limit access until verification completes.
- Use an optional **on-join role** for members while CADLY checks their existing link.

You can select multiple verified, unverified, and on-join roles. Older servers that use one role per setting remain supported.

## Set Up Verification

### Core Settings

Turn on **Enable Verification**, then configure only the settings your server needs.

| Setting | Purpose |
|---|---|
| Verified roles | Roles added after a member verifies successfully. |
| Unverified roles | Roles removed after successful verification. |
| On-join roles | Roles applied while a new member has not yet been automatically verified. |
| Auto verification | Refreshes roles and nickname for members who already have a CADLY Roblox link when they join. |
| Username template | The Discord nickname CADLY applies after verification. |

The username template supports `{roblox_username}`, `{roblox_display_name}`, `{discord_username}`, and `{discord_display_name}`. CADLY shortens the resulting nickname when Discord's nickname limit requires it.

### Recommended Onboarding

For a typical server, give new members an unverified role, set one or more verified roles, and enable auto verification. Returning members with an existing CADLY link then regain their configured access automatically; new members complete the normal Roblox sign-in flow.

Auto verification does not create a Roblox connection. A member without an existing link must still verify through the panel or verification page.

## Member Flow

1. The member opens the verification panel or a CADLY verification link for the server.
2. They sign in to Roblox and approve the connection.
3. CADLY saves the Roblox-to-Discord connection.
4. CADLY applies verified roles, removes unverified roles, and updates the nickname when configured.
5. CADLY can send the configured success direct message.

The account connection belongs to the member's CADLY account, while roles and nickname rules belong to each server. A member can therefore use their linked Roblox account in more than one CADLY server without repeatedly connecting it.

If the selected Roblox account is already connected to another Discord account, CADLY asks the member to confirm moving it. Continuing removes the previous connection, links the Roblox account to the signed-in Discord account, and sends the previous account a security notice. A Roblox account linked within the last ten minutes must wait before it can be moved.

## Panel and Page

Use **Send Verification Panel** to post a verification button in the selected channel. The panel is the clearest path for members because it sends them to the correct server-specific verification page.

You can customize the panel message, success direct message, and verification-page appearance. The page supports an optional background image plus background dim, background blur, and glass blur controls. Keep custom messages short and state what members need to do; do not ask members to send Roblox credentials to staff.

## Account Safety

The **Alt Account Detection** section covers two independent checks. Both are optional and inactive until an action is selected.

| Check | Signal | Runs when | Available outcome |
|---|---|---|---|
| Match | CADLY's internal security systems identify a likely account match | A member completes verification | Nothing, staff notification, mute, kick, or ban |
| Suspicious Match | CADLY's internal security systems identify elevated account risk | A member joins the server | Nothing, staff notification, mute, kick, or ban |

Select an alert channel whenever either action is enabled. If either action is mute, also set the timeout duration.

Suspicious-account alerts include staff moderation buttons appropriate to the account's current status. Unmute and Unban are grey; Mute, Kick, and Ban are red. Each action requires the corresponding Discord moderation permission and respects role hierarchy. After a successful action, all buttons are disabled and the selected button shows the result. Mute uses your configured timeout duration.

**Match** runs when a member verifies and uses CADLY's internal security systems to identify likely alternative-account matches.

**Suspicious Match** runs when a member joins and uses CADLY's internal security systems to identify elevated account risk. Security methods, signals, and decision thresholds are intentionally not disclosed. Because this check evaluates a new join, treat kick and ban more cautiously than a confirmed Match.

## Commands

### /link update

Refreshes a member's Roblox connection, configured roles, and nickname. Members can update themselves; an administrator or member with **Manage Server** can use the optional user argument to refresh another member.

Use this after changing verification roles or a nickname template, or when a member's verification completed but their Discord state is outdated.

### /link show

Shows the linked Roblox username, display name, and user ID. The optional user argument lets staff inspect another member's link.

## Troubleshooting

### Roles are not applied

Confirm that verification is enabled, each configured role still exists, and the CADLY bot role is above all roles it must manage. Also verify that the bot has **Manage Roles** permission.

### Nickname does not update

The bot needs **Manage Nicknames** and must be above the target member in the Discord role hierarchy. Remove the nickname template if your server does not want CADLY to manage names.

### A member linked the wrong Roblox account

Have the member open **Settings > Connections**, unlink the incorrect Roblox account, and link the correct one. If the correct Roblox account is connected to another Discord account, the member must review and confirm the transfer. Then run **/link update** to apply this server's roles and nickname to the corrected account. See [Profile & Connections](/docs/profile-settings/connections) for the full account flow.

### Auto verification did not run on join

Auto verification only works for members who already have an active CADLY Roblox link. Check that **Auto Verification** is enabled and that the bot can manage the selected roles and nickname.

### ER:LC features cannot resolve players

ER:LC player resolution is available when this server has either a Bloxlink key or CADLY verification enabled. If verification was just enabled or disabled, allow up to one minute for the resolution capability cache to refresh.

## Related Guides

- [Server Settings](/docs/server-settings)
- [Dispatch & CAD](/docs/dispatch)
- [Action Engine](/docs/action-engine)