> For the complete documentation index, see [llms.txt](https://merithic.gitbook.io/merithic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://merithic.gitbook.io/merithic-docs/integrations/discord-verification.md).

# Discord verification

Also called **iVerify**. Links your members' Discord accounts to their Roblox accounts, then assigns roles based on what they own.

## What it does

Once a member verifies:

* They get a **verified role**
* Their nickname can be set from their Roblox username
* They get **product roles** for anything they own from your studio

Someone who buys later gets their product role automatically, without re-verifying.

## Setting it up

1. Install **Discord Verification** from **Integrations**.
2. Link your Discord server under **Studio → Bot**.
3. Configure the roles in the integration's settings:

| Setting               | What it does                                           |
| --------------------- | ------------------------------------------------------ |
| **Verified role**     | Given to everyone who verifies                         |
| **Remove role**       | Optional; removed on verify, e.g. an "Unverified" role |
| **Nickname template** | `{robloxName}` and `{robloxId}` are substituted        |
| **Product roles**     | Map a product to a role for its owners                 |

## How members verify

They run `/verify`, or use your verify panel. They prove their Roblox account (Roblox login or a bio code), and roles apply immediately.

The link is global: verify once, recognised in every server running the integration.

## Syncing existing members

You don't normally need to sync by hand. Roles are applied automatically when:

* someone buys or is granted a product,
* you install or enable the integration, and
* you change its settings.

`/iverify-sync` is still there if you want to force a pass over every current member, for example after fixing a role hierarchy problem.

{% hint style="warning" %}
If roles fail to apply, it's almost always **role hierarchy**. Drag the bot's role **above** the roles it manages in Server Settings → Roles, and make sure it has Manage Roles and Manage Nicknames.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://merithic.gitbook.io/merithic-docs/integrations/discord-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.