Fixing Permission Problems

Most permission problems come from one of three places. The bot's role, an override on a channel or category, or the order of your roles.

What the bot asks for

The invite link asks for these permissions. Leave them on unless you know you don't use the feature.

• Manage Channels and Manage Roles create ticket channels and keep them private.
• View Channels, Send Messages, Embed Links and Read Message History post panels, ticket messages and transcripts.
• Attach Files sends transcripts and any files in your panel messages.
• Create Private Threads, Send Messages in Threads and Manage Threads run thread tickets. Create Public Threads covers public threads.
• Manage Webhooks shows the staff member's name on dashboard and live chat replies. Without it, replies still arrive under the bot's name.
• Manage Messages, Add Reactions, Use External Emoji and Use Application Commands cover message cleanup, reactions, emoji and slash commands.

Server-wide and channel overrides

Discord checks the bot's role first, then the overrides on the channel and its category. An override that denies a permission beats the role, so the bot can have a permission in Server Settings and still be blocked in one channel.

Why categories matter

Ticket channels are created inside the panel's category. Discord only lets the bot give out permissions it holds both server-wide and in that category. If the category denies one, tickets open without it, or don't open at all.

Role order

The bot can only assign roles that sit below its highest role. If a role change fails, drag the bot's role higher in Server Settings → Roles. Administrator skips every check on this page.

• For a server-wide permission, open Server Settings → Roles, pick the bot's role and turn the permission on.
• For a channel or category, open its settings, go to Permissions, add the bot's role and allow the permission.
• Press Check again on the dashboard to confirm the fix.