Skip to content
Clan LabsDocs
API referenceWebsite Open dashboard
Get startedDashboardDiscord botRoblox & Open CloudTroubleshooting
Documentation
Overview
  • Introduction
  • What is Clan Labs?
  • Core concepts
  • Requirements
  • Plans and availability
  • Quick start
Getting Started
  • Create or sign in
  • Add the Discord bot
  • Start setup with /setup
  • Select a Discord server
  • Connect a Roblox community
  • Confirm ownership
  • Choose a subscription
  • Configure Open Cloud
  • Complete setup
  • Recommended next steps
Setup Guides
  • Discord bot permissions
  • Roblox community connection
  • Roblox Open Cloud
  • Verification
  • Group and rank binds
  • Community permissions
  • Experience
  • Quotas
  • Welcome messages
  • Audit-log delivery
  • Events
  • Subscriptions
  • API keys
  • Divisions
Feature Guides
  • Member management
  • Profiles
  • Linked Roblox accounts
  • Experience and quotas
  • Ranks and group binds
  • Warnings
  • Suspensions
  • Blacklists
  • Medals and qualifications
  • Events and attendance
  • Audit logs and rollback
  • Analytics
  • Community permissions
  • Discord commands and actions
  • Pending join reviews
  • Custom bot branding
  • Discord server transfers
  • Privacy and account controls
  • Subscriptions and billing
Troubleshooting
  • Troubleshooting overview
  • Discord server is missing
  • Roblox community not found
  • Ownership cannot be confirmed
  • Bot permissions are missing
  • Discord role does not update
  • Role is above the bot
  • Verification fails
  • Open Cloud errors
  • Rank change fails
  • Profile does not sync
  • Command is unavailable
  • Action is not permitted
  • Subscription access is missing
  • Temporary service problem
API referenceClan Labs websiteOpen dashboard Support
Overview
  • Introduction
  • What is Clan Labs?
  • Core concepts
  • Requirements
  • Plans and availability
  • Quick start
Getting Started
  • Create or sign in
  • Add the Discord bot
  • Start setup with /setup
  • Select a Discord server
  • Connect a Roblox community
  • Confirm ownership
  • Choose a subscription
  • Configure Open Cloud
  • Complete setup
  • Recommended next steps
Setup Guides
  • Discord bot permissions
  • Roblox community connection
  • Roblox Open Cloud
  • Verification
  • Group and rank binds
  • Community permissions
  • Experience
  • Quotas
  • Welcome messages
  • Audit-log delivery
  • Events
  • Subscriptions
  • API keys
  • Divisions
Feature Guides
  • Member management
  • Profiles
  • Linked Roblox accounts
  • Experience and quotas
  • Ranks and group binds
  • Warnings
  • Suspensions
  • Blacklists
  • Medals and qualifications
  • Events and attendance
  • Audit logs and rollback
  • Analytics
  • Community permissions
  • Discord commands and actions
  • Pending join reviews
  • Custom bot branding
  • Discord server transfers
  • Privacy and account controls
  • Subscriptions and billing
Troubleshooting
  • Troubleshooting overview
  • Discord server is missing
  • Roblox community not found
  • Ownership cannot be confirmed
  • Bot permissions are missing
  • Discord role does not update
  • Role is above the bot
  • Verification fails
  • Open Cloud errors
  • Rank change fails
  • Profile does not sync
  • Command is unavailable
  • Action is not permitted
  • Subscription access is missing
  • Temporary service problem
  1. Docs
  2. /
  3. Feature Guides
Feature Guides

Understand community permissions

Use Clan Labs permission levels and per-action requirements to give staff the access they need.

Last updated 3 September 2026

Clan Labs permissions control actions inside one community. They are separate from Discord’s native server permissions and Roblox group roles, although an action may require all three systems to allow it.

Permission levels

Clan Labs uses an inherited hierarchy, from highest to lowest:

  1. SuperOwner — the Discord server owner. This level is determined from Discord ownership.
  2. Owner
  3. HICOM
  4. Supervisor
  5. Officer
  6. Member

A requirement includes the levels above it. For example, an action set to Officer can also be performed by Supervisor, HICOM, Owner, and SuperOwner.

Default action requirements

Community owners can customise the configuration. The current defaults include:

ActionDefault minimum
View audit logsMember
Warn, change experience or quota, award a medal, host, update usersOfficer
Promote, demote, or set the rank of a regular memberOfficer
Blacklist, suspend, change qualifications, review pending joinsHICOM
Change the rank of an officer-level targetHICOM
Set absolute experience or quota totals, broad medal awardsOwner

Settings, Open Cloud credentials, Discord server transfers, community reset or deletion, and audit rollback have additional owner safeguards. Clan Labs reserves the most sensitive of these for the Discord server owner even if a custom action requirement is lower.

Assign staff access

  1. Open Settings → Community Permissions.
  2. Review how Discord roles or members map to Clan Labs levels.
  3. Assign the lowest level that covers the person’s work.
  4. Set each action requirement deliberately.
  5. Save and test with a non-owner staff account.
  6. Review the resulting audit entry.

Avoid using a shared staff account. Individual identities make audit records useful and allow access to be revoked cleanly.

Why an action can still fail

Passing the Clan Labs permission check is only one condition. Discord role hierarchy, missing bot permissions, Roblox Open Cloud, feature entitlement, trial restrictions, subscription state, target rank, or an active moderation restriction can still stop the action.

If Discord reports Warning - Insufficient Permission, it can also state the required level, such as You must be HICOM+. Ask an Owner to review the one action requirement; do not request blanket Owner access by default.

For configuration steps, see Configure community permissions. For diagnosis, follow Action is not permitted.

PreviousAnalyticsNext Discord commands and actions
On this page
  1. Permission levels
  2. Default action requirements
  3. Assign staff access
  4. Why an action can still fail