The Clan Labs bot is missing required permissions

SymptomCopy link to Symptom

A command shows Warning - Missing Discord permissions, says I am missing the … permission!, cannot send a response, or fails a role, nickname, channel, thread, invite, or event operation.

Most likely causesCopy link to Most likely causes

• The bot was invited without the current official permission set.
• Its server role or a channel override denies the named permission.
• A channel, category, or thread is private to the bot.
• The bot role was moved below a role it must manage.
• The bot was removed or is not ready in the server.

Diagnostic checksCopy link to Diagnostic checks

1. Copy the exact permission named in the response.
2. In Server Settings → Roles, inspect the Clan Labs bot role.
3. Check category and channel overrides for the command and delivery channel.
4. Confirm the bot appears online or installed in the correct server.
5. For role actions, compare role order as well as permission toggles.

ResolutionCopy link to Resolution

Use the official Clan Labs invite flow to restore the supported permissions, or grant the named permission to the existing bot role. The official invite requests Administrator for reliable operation. If your server uses granular controls, ensure the bot can manage roles and nicknames and perform its configured channel, message, thread, embed, attachment, mention, emoji, reaction, and invite workflows.

Move the bot role above managed roles without placing it above roles it does not need to control.

When to retryCopy link to When to retry

Retry after Discord saves the role and channel changes. Use a harmless /help or test-member /update before repeating a high-impact action.

Contact supportCopy link to Contact support

Contact Clan Labs support if Discord shows the named permission as allowed at every role and channel layer but the current bot still reports it missing.

Include this informationCopy link to Include this information

Include the server and channel IDs, command, exact permission message, bot role position, timestamp, and redacted screenshots of permission overrides. Never send a bot token.