Quick Start
Create a main community, connect Roblox, and verify your first member.
Last updatedFollow these steps to create a main community. To attach a child community instead, use Set up divisions.
Before you start
You must own the Discord server, have the intended Roblox owner account verified in Clan Labs, and have an eligible subscription option. Administrator or Manage Server permission does not replace Discord ownership. Each Discord server can connect to only one Clan Labs community.
1. Sign in and add the bot
Open the dashboard and sign in with Discord. Verify your Roblox account if prompted.
Use the official bot invitation from the website, dashboard, or /invite. Select your server and approve the permissions. Move the Clan Labs role above the roles it must manage, keeping protected administrator roles above it. See Add the Discord bot for details.
You can create the community before installing the bot, but Discord commands, role updates, nicknames, and messages need it installed.
2. Open setup and select Discord
Open Communities → Set up community. You can also run /setup in Discord and choose Set up in dashboard. Only the server owner can continue.
Choose Main Community, then search for and select your Discord server.
- Already connected or Owner access required: select an unconnected server you own.
- Server missing: choose Refresh servers. Use Reconnect Discord if requested, signing in with the same account.
- Discord servers are temporarily unavailable or Discord could not be refreshed: retry in place after the service recovers.
- Bot missing: choose Add Clan Labs bot or install it after creation. A failed bot-installation check does not block setup.
Clan Labs retains incomplete setup drafts for a limited period. Review your selections when resuming after checkout or closing the modal.
3. Select the Roblox community
Search by community name or numeric Roblox Community ID. Check the ID and select an eligible, unconfigured community.
If Owner access required appears, open your account controls, verify and select the intended owner account, then refresh the community step. Membership alone does not satisfy the ownership check. Never supply a Roblox password, cookie, or session token to bypass it.
If the community remains unavailable, see Roblox community not found or Ownership cannot be confirmed.
4. Choose a subscription
Under Use an existing subscription, select an active, unbound plan and check its product and billing variant. Trial plans are labelled Trial. A plan in its binding cooldown shows when it becomes eligible again.
To purchase, compare the offered plans, review the price and billing schedule, complete hosted checkout, and return to the saved setup. Wait for fulfilment and confirm the new subscription is selected.
If payment completed but processing is pending, use the finalisation panel's retry action. Do not purchase again.
For later changes, see Subscriptions and billing.
5. Review and create
Check Main Community, the Roblox community name and numeric ID, Discord server and ID, Setup account and ID, and the selected plan and billing variant. Go back if any detail is wrong.
Choose the final create action once and keep the modal open. Do not start another setup in a second tab. When [Community name] is ready appears, open management.
If activation is pending, setup has completed but Discord command registration may take up to five minutes. Wait, then try /help or /verify. Install the bot first if you skipped it.
6. Connect Roblox
Open Settings → Roblox Cloud as the Discord server owner. Complete fresh Discord verification if requested, choose Connect Roblox, and authorize the intended account and community on Roblox.
Back in Clan Labs, check that Connected Roblox account shows Active. This authorization enables Roblox operations; it is separate from the member account verified during setup. The authorizing account must retain access to manage roles and pending joins.
If connection is unavailable or needs reauthorization, follow Connect Roblox Cloud. Use a temporary key only when the dashboard offers that form.
7. Check the first member
Run /verify with a test member, select the account for this community, then run /update. Auto Roles and Auto Nickname should report Success, or Disabled for features you have not enabled. Confirm the intended profile and any audit entries produced by supported test actions.
Before delegating staff access, configure permissions and complete Sync Discord commands if shown.
Optional configuration
Choose only what your community needs:
- Verification and rank binds for automatic roles and nicknames.
- Welcome messages, audit delivery, and events for Discord channels and activities.
- Experience and quotas for progression.
- API keys for external integrations; begin with read-only access.
Test each enabled workflow with a non-owner member before broad rollout. If a step fails, start with its message in Troubleshooting.