Configure group and rank binds

Rank configuration connects Clan Labs progression and Roblox roles to Discord roles. Group binds assign Discord roles and a nickname format based on membership in another Roblox community, with optional role assignments and nickname prefixes for each rank.

Explore Discord role sync and verification for the product workflow and demo before configuring individual binds.

Before you startCopy link to Before you start

• The connected Roblox community is active in Clan Labs.
• For role assignments, Clan Labs has Manage Roles and its highest role is above every managed role.
• For nicknames, enable Settings → Verification → Automatically update nicknames and grant Manage Nicknames. Nickname-only binds work with automatic roles disabled; the bot must still be above the member in Discord's role hierarchy.
• The community's Roblox Creator OAuth connection is operational for workflows that change Roblox ranks.
• You are an Owner or the Discord server owner.
• Group binds require a plan that includes the feature.

StepsCopy link to Steps

1. Open Manage → Ranks.
2. Find the rank card and choose Update when permitted, or View for read-only access. Configure the matching Roblox role.
3. Add the intended Discord role, prefix, and progression values shown by the form.
4. Save and repeat from lowest to highest operational rank.

Add or update a group bindCopy link to Add or update a group bind

1. Open Manage → Group Binds and choose Create Group Bind, or choose Update on an existing bind.
2. For a new bind, search the Division picker by name or ID when available. Already-bound divisions are excluded. To bind another group, choose Use another community ID and enter its Roblox community ID. If no divisions are listed or the list fails to load, enter the ID directly.
3. Choose Continue to load the community and its ranks.
4. In Membership roles, select roles for every verified member who belongs to that Roblox community. In Rank assignments, select roles for individual Roblox ranks.
5. Optionally configure Group nickname format, Nickname priority, and each rank's Nickname prefix as described below. You can leave all Discord role assignments empty when the group has a nickname format.
6. Choose Create Group Bind or Save Changes.
7. Run /update for a non-owner test member who should match, then for one who should not.

Use Refresh Ranks to reload Roblox ranks while editing. Clear all rank assignments clears every rank's Discord roles and nickname prefix, including ranks hidden by search. It keeps membership roles, the group nickname format, and priority; save to apply the change.

The division picker refreshes after a bind is created or deleted. A group bind uses another community's membership in this server; a division has its own dashboard and community configuration.

Rank cards show the rank's configured emoji and linked-role count. Open the rank to review its saved lock and progression settings. Bind cards show membership roles and assignments. These summaries do not guarantee a future rank change; permissions, entitlement, and Roblox checks still apply. Bind deletion is available only when permitted.

Locking a rank also affects manual Discord rank changes. Moving a member into or out of a locked rank requires the corresponding officer-action permission, which defaults to HICOM. See locked-rank permissions before testing the boundary.

Set a rank emojiCopy link to Set a rank emoji

1. Open Manage → Ranks, find the rank, and choose Update.
2. Under Rank Emoji, open the picker and choose one standard emoji or an available Discord custom emoji.
3. Choose Save Changes.
4. Check the rank card and a member card or profile for that rank. Supported Discord messages also show the emoji beside the rank name.

To remove it, choose Clear rank emoji and then Save Changes. An unset emoji leaves Discord rank names undecorated. The emoji is a display setting; changing it does not rename the Roblox rank or change its prefix, role binds, progression, or permissions.

If a custom emoji is unavailable or does not display, check that it still exists in Discord and try a standard emoji. If you can only choose View, ask someone with rank-editing permission to make the change.

Set group nicknames and rank prefixesCopy link to Set group nicknames and rank prefixes

Enter one Group nickname format for the whole bound group. For example, %BINDRANKPREFIX% %ROBLOXNAME% gives a member with the fictional Roblox username PixelComet482 the nickname [CMD] PixelComet482 when their external rank has the prefix [CMD], or [PVT] PixelComet482 when its prefix is [PVT]. A blank or missing prefix produces PixelComet482 with this format.

Type % in the format field to find variables. Click a suggestion, or use the arrow keys and Enter to insert it; Escape closes the suggestions. There is no nickname preview in the group-bind editor, so verify the saved format with a test member.

Prefixes are literal text: entering %ROBLOXNAME% as a prefix does not expand it into a username. The format accepts up to 256 characters and each prefix up to 64. Surrounding whitespace is trimmed, and Clan Labs limits the rendered nickname to 32 Unicode code points.

Choose which group format winsCopy link to Choose which group format wins

1. Clan Labs considers groups the member belongs to that have a non-blank group nickname format. Guest rank does not qualify.
2. The highest Nickname priority wins. Priority defaults to 0 and accepts whole numbers from 0 to 1000000.
3. Equal priorities use the lowest Roblox group ID.
4. If no eligible group format matches, Clan Labs uses the community format from Settings → Verification.

A blank group format is skipped even if that bind has a high priority or saved rank prefixes; another matching group can still win. A member does not need a configured rank assignment to use the group format. Their exact rank supplies its prefix when one is saved; a missing prefix does not make Clan Labs choose a different group.

Saving does not immediately rename members. The next member update or verification flow applies the selection again, including after an external rank change or group departure. The Bypass role, Discord server ownership, permissions, and plan entitlement still apply.

Check the resultCopy link to Check the result

An update gives members the roles matched by their connected-community rank and external group binds, removes managed roles they no longer qualify for, and reports the roles added or removed.

Review the /update result’s Roles Added, Roles Removed, and Failed Roles fields. Confirm the Discord member’s final roles match the Roblox memberships and configured binds.

If automatic nicknames are enabled, check Auto Nickname and the member's final nickname. Test a rank with a prefix, a rank without one, and a member in multiple bound groups to verify priority. See profile sync troubleshooting if the old nickname remains.

• Never bind a role with Administrator unless that exact escalation is intended and independently reviewed.
• Prefer one clear source of truth for each managed Discord role.
• Test changes on non-owner accounts.
• Re-test after renaming, deleting, or reordering Discord or Roblox roles.

Common errorsCopy link to Common errors

• A configured role is missing from the selector — it is deleted, unavailable, or above the bot.
• Unable to fetch group binds — saved binds or Roblox membership information could not be loaded; role synchronization stops for affected verified members. Retry after the service recovers.
• Assign at least one Discord role or nickname format — add a role assignment or a group format. Rank prefixes alone are not enough to save a bind.
• Reload group binds before saving; nickname settings are missing from this update. — reload the page, reopen the bind, and reapply the edit using the current form.
• A role appears in Failed Roles — check Manage Roles and hierarchy.
• A rank operation says Error - Rank check unavailable — Clan Labs could not verify current Roblox roles, so it changed nothing.
• The member receives conflicting roles — review overlapping rank and external group-bind rules.

Next, define community permissions or configure experience.