Configure community permissions

What this doesCopy link to What this does

Community permissions control which Discord members can view or perform Clan Labs actions. Levels inherit downward: Owner satisfies HICOM, Supervisor, Officer, and Member requirements.

PrerequisitesCopy link to Prerequisites

• Staff members are present in the connected Discord server.
• Any Discord roles used as permission subjects already exist.
• You meet the community’s Settings permission requirement.

Setup stepsCopy link to Setup steps

1. Open Settings → Permissions.
2. Review the level rail: Owner, HICOM, Supervisor, Officer, and Member.
3. Add specific Discord users or roles to the appropriate assignable levels.
4. Review action requirements such as warning, blacklist, experience, quota, medal, qualification, pending join, event hosting, suspension, user updates, and audit-log viewing.
5. Raise or lower each requirement only to match the community’s responsibility model.
6. Save the configuration.
7. 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, Open Cloud credentials, community transfer, reset or deletion, and audit rollback.

Expected resultCopy link to Expected 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.

Verify that it worksCopy link to Verify that it works

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.

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.

Security practicesCopy link to Security practices

• 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.

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