Permissions the bot needs
The exact permissions in the invite link, what each one is used for, and what breaks without it.
The invite set
The invite link asks for a fixed list, not Administrator. Administrator is still the easiest choice on a server with many channel overrides, because a single denied override on a category can stop ticket creation, but it is not required.
- View Channels, Send Messages, Send Messages in Threads, Read Message History
- Posting panels, catalogs, welcome messages and replying in tickets.
- Embed Links, Attach Files
- Every embed, invoice image and transcript file.
- Add Reactions, Use External Emojis
- Reaction goals and the emoji on buttons.
- Manage Messages
- /clear, deleting spam, editing posted panels and catalog messages.
- Manage Channels
- Creating, renaming, locking and deleting ticket channels.
- Manage Roles
- Granting the verify role and winner roles. The bot role must also sit above those roles.
- Manage Threads
- Ticket threads and thread cleanup.
- Create and Manage Expressions
- /addemoji.
- View Audit Log
- Anti-nuke needs it to see who deleted a channel or banned someone.
- Kick Members, Ban Members, Moderate Members
- Anti-nuke and anti-spam actions (kick, ban, timeout).
Role position
Discord only lets a bot manage roles below its own highest role. If verification does not grant the role or a winner role is not given, move the bot's role above them in Server Settings → Roles.
Channel overrides
A permission granted at server level can be denied on a category or channel. The most common failure is a ticket category where @everyone is denied View Channel and the bot role is not explicitly allowed. The setup checklist and the log channel report these as "missing permission" with the channel name.
The Permissions Calculator tool on the website builds an invite link with a custom set if you want to trim it further.