Configure staff permissions

Assign staff access in Settings → Permissions. For the level hierarchy and default action requirements, see the Permission reference.

Before you startCopy link to Before you start

• Staff members are present in the connected Discord server.
• Any Discord roles used as permission subjects already exist.
• You are an Owner or the Discord server owner.
• Your Discord sign-in authorizes command-permission updates, and your Discord account has Manage Server and Manage Roles for synchronization.

StepsCopy link to Steps

1. Open Settings → Permissions.
2. Review the level rail: Owner, HICOM, Supervisor, Officer, and Member.
3. Add verified users directly as Owners. Only the Discord server owner can change Owners.
4. Add Discord users or roles to HICOM, Supervisor, or Officer. Discord roles cannot be assigned to Owner.
5. Review action requirements such as warning, blacklist, experience, quota, medal, qualification, pending join, event hosting, suspension, user updates, and audit-log viewing.
6. Raise or lower each requirement only to match the community’s responsibility model.
7. Save the configuration.
8. Ask one test user at each level to reopen the dashboard and run an appropriate command.

The Discord server owner is Super Owner automatically. That boundary cannot be assigned from this page and is required for setup, Roblox connection management, community transfer, export, reset or deletion, and audit rollback.

Synchronize Discord commandsCopy link to Synchronize Discord commands

Saving staff level assignments applies managed slash-command permissions in Discord before saving the new assignments. If Discord rejects the update, refresh and inspect the saved configuration before trying again.

Initial setup, a transfer, a privacy request, or an eligible rollback can leave synchronization pending. When Discord command permissions need to be synchronized appears:

1. Choose Sync Discord commands.
2. If asked to reconnect, sign out and back in with Discord or use Reconnect Discord where offered.
3. Authorize command-permission updates and confirm your Discord account has Manage Server and Manage Roles.
4. Wait for synchronization to finish, then test with a staff account.

The sync covers permission-locked top-level slash commands. It does not mirror every configurable subcommand or context-menu requirement. For example, the base visibility requirement for /pendingjoin and /qualification is Officer, while their operational actions default to HICOM. Clan Labs checks each action again when it runs.

Check the resultCopy link to Check the result

Staff see the community and only the navigation or actions available to their effective level and plan. Discord commands reject insufficient access with Warning - Insufficient Permission and the required level.

Use a non-owner account to test one read and one write action. Confirm a user below the configured level cannot act, while a user at that level can. Remove the test grant and confirm access is withdrawn.

• Grant named users or narrow staff roles, not @everyone.
• Use the lowest level that supports the task.
• Review role membership in Discord as carefully as the Clan Labs requirement.
• Revoke old staff access promptly and audit sensitive changes.

Common errorsCopy link to Common errors

• A user sees the community but an action is missing — visibility and write permission are separate.
• You must be [Level]+ to use this command! — change the user’s level or the action requirement deliberately.
• A role grant does not apply — confirm the user is still in the connected Discord server and holds the role.
• Access changed after a transfer — staff absent from the destination regain stored access only after joining it; the destination owner becomes Super Owner.

Synchronization errorsCopy link to Synchronization errors

If some command updates completed before an error, use the sync control to reconcile the saved settings. Do not assume every Discord command changed together.

Next, configure experience, quotas, or audit-log delivery.