Core concepts
Learn the Clan Labs terms used for communities, identities, permissions, integrations, subscriptions, and audits.
Last updatedThese terms appear throughout the dashboard, Discord bot, and API reference.
Identity and community terms
Discord account — the identity used to sign in to the dashboard and interact with the bot.
Verified Roblox account — a Roblox account linked through the dashboard’s Roblox sign-in flow. One Discord account can hold multiple verified Roblox accounts.
Community account link — the verified Roblox account selected for one Clan Labs community. This can differ between communities.
Roblox Community ID — Roblox’s numeric identifier for a Roblox group. It appears in Roblox community URLs and is used during setup.
Clan ID — the Clan Labs identifier used by API v2 in the X-Clan-Id header. It is shown and copyable on the Clan Labs API Keys settings page. It is an identifier, not a secret.
Main community — the primary Roblox community and Discord server configuration.
Division — a Roblox community connected below a main community. It shares the main community’s billing relationship.
Permission terms
Super Owner — the Discord server owner. This level cannot be assigned from the permissions page. Clan Labs reserves setup, community transfer, Roblox connection management, community export, deletion or reset, and audit rollback for this owner-level boundary.
Owner, HICOM, Supervisor, Officer, Member — inheriting community permission levels. A person at a higher level also satisfies lower-level requirements. Owners are verified users assigned directly by the Discord server owner. Discord users or roles can be assigned to HICOM, Supervisor, or Officer. Owners can adjust the requirement for individual actions.
Capability — a specific dashboard or command action, such as viewing audits, issuing a warning, or changing experience. Clan Labs resolves capabilities from the person’s effective community level and the configured requirement for that action.
API scope — a permission assigned to an API key, such as members.read or warnings.write. API scopes are separate from staff permission levels.
Configuration and integration terms
Rank — a Clan Labs rank configuration linked to a Roblox role and, optionally, a Discord role, prefix, experience threshold, and other progression behavior.
Group bind — a rule that adds or removes a Discord role based on membership or rank in another Roblox community.
Verification — linking Discord and Roblox identities, then applying the selected account to a community.
Roblox Creator OAuth connection — authorization from a Roblox account to manage the selected community's roles and pending joins. Clan Labs refreshes its encrypted tokens automatically. The authorizing account can differ from the verified account selected for a member.
Temporary Roblox Open Cloud key — a legacy User API key offered in some environments while Creator OAuth is unavailable. Follow the connection page's migration notice.
Discord command synchronization — applying managed top-level slash-command permissions in Discord from Clan Labs staff assignments. Each action still has its own execution-time checks.
Clan Labs API key — a secret beginning with cl_live_ that authenticates API v2 requests. It belongs to one Clan Labs community and is displayed only at creation or rotation.
Billing and availability terms
Plan — Premium or Pro. The live Clan Labs plan-comparison flow provides current prices and billing schedules.
Entitlement — the effective feature availability produced from plan, subscription status, and trial rules. A configured control may stop working if the subscription becomes paused, unpaid, expired, or outside its cancellation grace period.
Binding — attaching an active subscription to a community. After binding, the Clan Labs setup flow applies a 30-day lock before that subscription can move to another community.
History terms
Audit log — a chronological record of supported changes from Discord, the dashboard, API keys, and automated workflows.
Rollback — a guarded Pro action that reverses an eligible audit change from the previous 30 days. It is available only to the Discord server owner and only when the stored audit data and current state allow a safe reversal.
Continue with requirements before setup.