GuidesUpdated 12 October 2026
Discord ticket bot permissions, explained
Every permission a ticket bot asks for, what it is used for, and how to tell a reasonable request from one to refuse.
Why a ticket bot asks for so much
A ticket bot does work a moderator would otherwise do by hand: it creates a channel, lets exactly one member and your staff into it, posts in it, and later reads it back to save a transcript. Each of those is a separate Discord permission, which is why the list on the invite screen is longer than for a bot that only answers commands.
A reasonable request is one where every permission matches something the bot visibly does. Discord shows them all before you confirm, and you can untick any of them there.
What it needs
These are the 6 TicketCrew cannot work without, and what each is used for.
| Permission | What it is for |
|---|---|
| View Channel | See the channels your panels live in, and the tickets it creates. |
| Send Messages | Post ticket panels and reply inside tickets. |
| Embed Links | Render ticket panels and ticket headers as rich embeds. |
| Read Message History | Build transcripts and detect inactivity for auto-close. |
| Manage Channels | Create, rename, lock and delete the ticket channels themselves. |
| Manage Roles | Grant a ticket opener access to their own ticket channel. Only ever applied to channels TicketCrew created. |
Manage Roles sounds the most alarming, and is the one to understand. Discord uses it for channel permissions as well as for roles: it is how the bot lets the member who opened a ticket into that one channel. TicketCrew only applies it to channels it created.
What is optional
The bot works without these; leaving one off only loses what is described.
| Permission | What it is for |
|---|---|
| Attach Files | Attach the generated transcript when a ticket is closed. |
| Manage Messages | Pin the ticket header so it stays reachable in long tickets. |
| Administrator | Not needed. It saves letting TicketCrew into each channel by hand if your server locks them all down. Untick it on Discord’s screen if you would rather not give it. |
Should you give a bot Administrator?
Administrator overrides every other setting: a bot with it can see and change everything in the server, whatever the channel says. Most of the time a ticket bot does not need it, and the specific permissions above are the better choice.
The exception is a server that hides every channel by default. There, a bot without Administrator has to be let into each category by hand before it can create tickets in it. TicketCrew offers Administrator for that reason only, as an optional box you can untick, and never reports it as missing. Even with it, TicketCrew does not ban, kick or time out members, and blocks @everyone and @here in everything it sends.
Fixing “missing permissions”
A bot can hold a permission for the server and still be refused in one channel, because channel and category settings override the server's. When a ticket will not open or a panel will not post:
- Run
/ticketcrew permissionsin the channel where it failed. It names the permission that is missing there. - Open that channel's (or its category's) settings, then Permissions, and allow it for the bot's role.
- Check the category tickets open in, too. If the bot cannot see that category, it cannot create channels inside it.
One thing Discord insists on
A bot can only give a member a permission it has itself. If tickets open but the member cannot attach files or read history, the bot is usually missing that permission in the ticket category.
What a ticket bot should not need
Banning, kicking or timing out members, and mentioning @everyone, have nothing to do with tickets. A ticket bot asking for them specifically is worth a second look. Signing in to its website should not need your email either: TicketCrew asks Discord only for your name and the servers you are in.
The same list, kept in step with the bot, is in the docs under Permissions.