Manage ranks and group binds

Rank actions change a member’s role in the connected Roblox community. Binds translate Roblox group and rank information into Discord roles or nickname behaviour.

For an overview of staff actions and automated progression, explore Roblox group ranking.

Change a Roblox rankCopy link to Change a Roblox rank

Staff can use a member profile or Discord commands:

• /promote moves a member to the next eligible configured rank.
• /demote moves a member to the previous eligible configured rank.
• /changerank selects a permitted destination rank.

Before the change, Clan Labs checks the target, staff requirement, rank boundaries, blacklist and suspension state, community entitlement, and current Roblox group data. The Roblox Creator OAuth connection must be operational and the authorizing account must retain the required community permissions.

The default requirement is Officer for ordinary member rank changes and HICOM when the target is treated as an officer. Owners can customise this in Settings → Permissions.

If Clan Labs shows Error - Rank check unavailable, no rank change was made. Wait for the dependent service to recover, then check the current Roblox rank before retrying.

Locked-rank permissionsCopy link to Locked-rank permissions

Discord checks both the member's current rank and the destination rank. For /promote, /demote, and /changerank, a locked rank at either end requires the corresponding officer-action permission, which defaults to HICOM. Owners can customise each action's requirement in Settings → Permissions; the dedicated locked-rank bypass can also satisfy this check.

For example, an Officer who can promote an ordinary member cannot promote them into a locked destination under the default permissions. A general community-permissions bypass alone does not bypass the locked-rank check. Other hierarchy, suspension, blacklist, and Roblox checks still apply.

If the response says Insufficient Permission, review both ranks and the requirement for the specific action before retrying. Ask authorised staff to make the change when needed.

Review rank and bind configurationCopy link to Review rank and bind configuration

In Ranks or Group Binds, use search to find the configuration card. Choose Update when permitted or View for read-only access. Cards summarize linked roles and assignments. Open a rank to review its lock and progression settings; saved configuration does not guarantee that an operation will pass its permission and Roblox checks.

Follow Configure group and rank binds for setup.

Configured rank emojis appear on Dashboard rank and member cards, member profiles, and supported Discord rank messages. They decorate the rank name without changing Roblox ranks or permissions. To choose or remove one, follow Set a rank emoji.

Apply role and rank bindsCopy link to Apply role and rank binds

Rank binds map particular ranks from a connected Roblox group to Discord behaviour. Group binds can apply rules based on membership in an additional Roblox group. Premium includes group binds; availability is shown by the Clan Labs plan comparison.

After changing bind settings:

1. Run /update for a test member or use Apps → Update User.
2. Read the separate Auto Roles and Nickname results.
3. Check any listed Roles Added, Roles Removed, or Failed Roles.
4. Confirm that unrelated roles were not affected.

Clan Labs only manages roles represented by the active configuration. Discord still enforces its hierarchy: the Clan Labs bot’s highest role must be above every role it needs to assign or remove.

Apply group nicknamesCopy link to Apply group nicknames

A group bind can supply one nickname format for its members and an optional prefix for each external Roblox rank. Nickname-only binds do not need Discord role assignments. Enable automatic nicknames in Settings → Verification and give the bot Manage Nicknames.

When several groups match, the highest nickname priority wins, then the lowest Roblox group ID. Binds without a format are skipped; if none qualifies, the community format is used. Prefixes alone do not override that format. See group nickname setup for variables and examples.

Changes apply on the next member update or verification flow. After a member changes external rank or leaves a bound group, run /update or Apps → Update User and inspect Auto Nickname and their actual Discord nickname. A failed bind or required Roblox lookup preserves the old nickname; see profile sync troubleshooting.

Keep owner-level Roblox roles out of routine staff actions. Check member IDs and the connected account's access, audit binds before bulk updates, and inspect the actual Roblox rank before retrying a timed-out write.

For configuration, see Group and rank binds. For failures, use Rank change fails or Discord role does not update.