Configure Discord bot permissions

The applications.commands installation scope registers Clan Labs commands. Discord server permissions let the bot manage configured roles and nicknames and deliver verification, welcome, event, and audit messages. Discord still enforces its role hierarchy even when the bot has broad server permissions.

Before you startCopy link to Before you start

• The official Clan Labs bot is installed.
• You can manage the server’s roles and channel permissions.
• You know which roles and channels Clan Labs will use.

StepsCopy link to Steps

1. Open Server Settings → Roles.
2. Select the Clan Labs role and retain the permissions granted by the official invite.
3. Move the Clan Labs role above every rank, verification, medal, qualification, and group-bind role it must assign or remove.
4. Keep it below owner-only or administrative roles it should not manage.
5. In each configured text channel, allow Clan Labs to view the channel, send messages, send in threads when used, embed links, attach files, add reactions, and use external emoji.
6. Keep Manage Roles and Manage Nicknames available for /update and role synchronisation.
7. Save Discord’s changes.

The official invite requests the bot and applications.commands scopes, Administrator, and these individual permissions:

• Manage Server, Manage Roles, and Manage Channels;
• Create Invite and Manage Nicknames;
• View Channels, Send Messages, Send Messages in Threads, and Manage Messages;
• Embed Links and Attach Files; and
• Mention Everyone, Use External Emojis, and Add Reactions.

If your organisation removes Administrator, preserve every granular permission above and verify that channel overrides do not remove the permissions required by an enabled workflow.

Check the resultCopy link to Check the result

Commands run without Warning - Missing Discord permissions. /update can add and remove configured roles and can update a non-owner member’s nickname.

1. Run /update for a test member below the bot in the member hierarchy.
2. Confirm Auto Roles: Success and Auto Nickname: Success, or Disabled for settings you intentionally turned off.
3. Send a test verification panel or perform a low-risk action that creates an audit delivery.
4. Confirm the bot can post and embed in the selected channel.

User authorization for command synchronizationCopy link to User authorization for command synchronization

Updating managed command permissions also needs authorization from the signed-in Discord user. It is separate from the bot's installation scopes and server permissions. If asked to Reconnect Discord, refresh that sign-in and confirm the user has Manage Server and Manage Roles. Follow Configure community permissions.

• Do not move the bot above roles it never needs to manage.
• Review role permissions before binding them; Clan Labs assigns the role as configured, including any permissions it already carries.
• Avoid binding Administrator roles.
• Re-test after changing the bot role, channel overwrites, or server ownership.

Common errorsCopy link to Common errors

• I am missing the [permission] permission! — grant the named permission at the server or channel level.
• Failed Roles in an update result — move the target roles below the bot and check Manage Roles.
• Auto Nickname: Failed — grant Manage Nicknames, check member hierarchy, and remember the Discord server owner’s nickname cannot be changed by the bot.
• A stored channel is unavailable — select a current text-capable channel in Clan Labs settings.

Next, connect the Roblox community or configure verification.