When you add a ticket bot, Discord shows a long list of permissions. A common reaction is to untick half of them just in case, or the opposite — give the bot Administrator and move on. The first breaks tickets in odd places, the second hands the bot far more than it needs.
Below we go through every permission Discord Tickets asks for when you invite it: what it’s for, what stops working without it, the most common problems and how to check the bot’s role quickly.
How Discord works out bot permissions
Three things decide what the bot can do in a given channel:
- The bot’s role. When you invite the bot, Discord creates a role named after it with the permissions you approved. Those apply server-wide.
- Category and channel permissions. These can take away what the role grants. If a category denies View Channel to
@everyoneand the bot’s role has no explicit allow, the bot can’t see that category. - The bot can only grant what it has. That’s a Discord rule: the bot can’t let a ticket opener attach files if it can’t attach files itself.
The third point explains why the list includes permissions the bot doesn’t seem to use on its own.
Every permission, one by one
| Permission | Why the bot needs it |
|---|---|
| View Channels | See the ticket category, panel channel and log channel. Without it the bot can’t work there |
| Manage Channels | Create ticket channels and delete them on close if that’s enabled |
| Manage Roles | Set permissions on the ticket channel and give out the ticket ban role |
| Manage Threads | Handle tickets in Private thread mode |
| Create Private Threads | Open a ticket as a private thread |
| Send Messages in Threads | Post the welcome message and replies inside the thread |
| Send Messages | Publish panels, welcome messages and log entries |
| Embed Links | Publish embeds and grant this permission inside tickets |
| Attach Files | Let the opener and staff attach screenshots |
| Add Reactions | Part of the basic set for working with messages |
| Read Message History | Let the opener and staff see the conversation in a ticket |
| Manage Messages | Give staff message management inside tickets |
| Pin Messages | Pin the welcome message at the top of the ticket |
Channels and access
Manage Channels lets the bot create new ticket channels in the chosen category and, with Delete the channel on close turned on, delete them.
Manage Roles sounds scary, but in Discord it covers both roles and per-channel permissions. The bot uses it in two places. First, to set up the ticket channel so only the opener and the topic’s admin roles can see it. Second, for /ticket ban: the bot gives the member the ticket ban role from your settings and removes it on its own when the time runs out.
Mind the role hierarchy: in Discord, a bot can only assign roles that sit below its own role. If the ban role is above the bot’s role, the bot can’t give it out. We cover limits, cooldowns and bans in detail in protecting tickets from spam.
Threads
Manage Threads, Create Private Threads and Send Messages in Threads power Private thread mode: the bot creates the thread, posts the welcome message and locks it on close. Keep them even if all your panels use channels right now: the mode is a panel setting, and you’ll need them the day you switch. For how the two modes differ, see ticket channels vs private threads.
Messages
Send Messages and Embed Links are the foundation: without them the bot can’t properly publish panels, welcome messages and log entries.
Attach Files, Read Message History and Manage Messages work through the only-grant-what-you-have rule. The opener and staff need message history, files and links in a ticket, and staff also need message management. If the bot lacks these, it can’t open them up in the ticket channel.
Pin Messages is a new, separate permission — more on that below.
Common problems
The bot can’t see a category or channel
The classic case: someone made the ticket category private — denied View Channel to @everyone, allowed the staff role, and forgot the bot’s role.
Starting November 16, 2026, this bites harder. Discord hides channels the bot can’t view from that bot: it gets them under the name ___hidden___ with no details, and the API list of server channels leaves them out. For the bot, that channel effectively doesn’t exist.
The fix: in the category or channel permissions, add the bot’s role and allow View Channel. Check every place the bot works: the ticket category, the panel channel, the log channel and, in thread mode, the parent channel.
The welcome message isn’t pinned
Since 2026, pinning requires its own Pin Messages permission. Manage Messages no longer lets anyone pin. If the bot’s role doesn’t have it, or a category denies it to the bot, the welcome message stays unpinned.
Turn on Pin Messages for the bot’s role. If you don’t need the pin, you can simply switch off Pin the first message in the panel. The same goes for your staff: if they used to pin through Manage Messages, they now need the new permission too.
The bot won’t give out the ban role
Check three things: the bot has Manage Roles, the bot’s role sits above the ban role in the list, and the role is set under Ticket-banned roles in Settings.
Members can’t attach files or see history in a ticket
Most likely someone removed Attach Files or Read Message History from the bot’s role, or a category denies them to the bot. The bot can’t grant a permission in the ticket channel that it doesn’t have. Give it back to the bot’s role.
How to check the bot’s role
- Open Server Settings → Roles and find the role named after the bot. Make sure all 13 permissions from the table are on.
- Open the ticket category’s settings → Permissions. If
@everyonehas denies there, add the bot’s role and explicitly allow viewing and the message permissions. Repeat for the panel channel, the log channel and the thread parent channel. - In the role list, drag the bot’s role above the ticket ban role.
- Open a test ticket from a second account: the welcome message is pinned, files attach, and the log channel has a new entry.
Tip. Don’t give the bot Administrator for peace of mind. The set above covers every feature, and extra permissions are just extra risk if something goes wrong.
When you add the bot with the Add bot to server button, Discord offers the full set right away — just don’t untick anything. The docs walk through it step by step, and the ban role is set up in the server settings section. For the rest of this year’s Discord changes, see what changed in Discord in 2026.