Discord Ticket Bot Permissions Explained (And What Breaks Without Them)
Exactly which Discord permissions a ticket bot needs, what breaks when each one is missing, how channel overwrites interact with ticket channels, and how to grant access safely without handing over Administrator.
- Published
- Author
- Dani, Founder, AI Ticket Bot
Short answer: a ticket bot needs Manage Channels, Manage Roles, View Channel, Send Messages, Embed Links, Attach Files, and Read Message History. Do not grant Administrator instead; it is not simpler and it is a real risk. Almost every "the bot is not working" report traces to one of the six specific failures below.
The permission set, and what breaks without each one
| Permission | What breaks without it |
|---|---|
| Manage Channels | Tickets do not open at all. The bot cannot create the channel |
| Manage Roles | The ticket opens but the member cannot see it |
| View Channel | The bot cannot see the panel channel, so buttons do nothing |
| Send Messages | The panel posts but the bot never replies inside tickets |
| Embed Links | Panels and welcome messages render as blank or plain text |
| Attach Files | Transcripts and file replies fail |
| Read Message History | Transcripts come out empty or partial |
| View Audit Log | Only needed to detect another bot's ticket channels |
The two that produce the most confusing symptoms are Manage Roles and Read Message History, because in both cases the bot appears to work.
Why Manage Roles is needed for a ticket bot
This one surprises people, and it is the single most common misconfiguration.
When a ticket channel is created, the bot has to grant the person who opened it permission to see that channel. In Discord, editing a channel's permission overwrites requires the bot to hold the permissions it is granting. Without Manage Roles, the bot creates the ticket and then cannot let anybody in. The symptom is a ticket that exists but that the member cannot see, which reads like the bot silently ignoring them.
The role hierarchy trap
Permissions are not the only gate. Discord also enforces role position.
A bot can only manage roles positioned below its own role in your server settings. If your bot's role sits at the bottom of the list, it cannot grant access involving roles above it, no matter which permissions you ticked.
Fix: drag the bot's role above the roles it needs to work with. It does not need to be at the top. It needs to be above the staff and member roles involved in tickets.
This is the answer to a large share of "I granted everything and it still does not work".
Should I just give the bot Administrator?
No. It is not simpler, and it is worse in two concrete ways:
- A compromised or misbehaving bot with Administrator can do anything, including deleting channels and banning members. The permission set above cannot.
- It hides misconfiguration. With Administrator everything works until the day you remove it, and then you are debugging from scratch.
Granting the specific set takes the same number of clicks, because the invite link carries them.
Channel overwrites and where they bite
Server-level permissions are the floor. Channel overwrites can take them away again.
The classic failure: the bot has Send Messages at the server level, but your #support channel has an overwrite denying Send Messages to everyone, added months ago to stop chatter. The panel posts, the buttons work, and the bot cannot reply.
When something works in one channel and not another, it is always an overwrite. Check the specific channel's permissions, not the role's.
Permissions for your staff, which are a separate thing
Bot permissions decide what the bot can do. Staff permissions decide what your team can do inside tickets, and they are configured in the bot, not in Discord.
Worth separating:
- Claim: take ownership so two people do not answer at once.
- Close: not everyone who reads tickets should close them.
- Train the AI: if the bot has a per-server brain, this decides who can teach it. Keep it tight, because a wrong fact taught here gets repeated to every member who asks.
On AI Ticket Bot these are per-role and server-authoritative, so the server owner decides, not the bot.
A safe setup checklist
- Invite with the standard permission set, not Administrator.
- Drag the bot's role above your member and staff roles.
- Check the panel channel's own overwrites, not just the role.
- Open a test ticket from an account with no roles.
- Confirm the opener can see the ticket, staff can see it, and closing produces a transcript.
- Set staff permissions inside the bot separately, especially who can train the AI.
Troubleshooting, by symptom
- Nothing happens when I press the button: bot cannot View Channel, or the panel is stale.
- Ticket opens but the member cannot see it: Manage Roles missing, or role hierarchy.
- Bot posts the panel but never replies: channel overwrite denying Send Messages.
- Transcript is empty: Read Message History missing.
- Embeds look broken: Embed Links missing.
- Works in one channel, not another: always a channel overwrite.
Related reading
- How to set up a Discord ticket bot
- Discord ticket transcripts and retention
- Best Discord ticket bots in 2026, compared
Accurate as of July 2026. Plan limits and pricing change; our pricing page carries the live figures.
Frequently asked questions
- What permissions does a Discord ticket bot need?
- Manage Channels, Manage Roles, View Channel, Send Messages, Embed Links, Attach Files, and Read Message History. View Audit Log is only needed if the bot detects ticket channels created by a different bot. Administrator is not required and should not be granted.
- Why can members not see their own ticket?
- Almost always a missing Manage Roles permission or a role hierarchy problem. The bot has to edit the ticket channel permissions to let the opener in, and Discord only allows that if the bot holds the permissions it is granting and its role sits above the roles involved.
- Should I give my ticket bot Administrator?
- No. It is no simpler than granting the specific set, a compromised bot with Administrator can delete channels and ban members, and it hides misconfiguration until the day you remove it. The invite link already carries the correct permissions.
- The bot works in one channel but not another. Why?
- That is always a channel permission overwrite. Server-level permissions are the floor and a channel overwrite can remove them again. Check the specific channel permissions rather than the role.
- Who should be allowed to train the AI?
- Keep it tight. Training permission decides who can teach the per-server brain, and a wrong fact taught there gets repeated to every member who asks. On AI Ticket Bot it is a per-role permission set by the server, separate from being able to read or close tickets.
See it on your own server.
Add AI Ticket Bot free, teach the brain a few of your most common answers, and watch it clear the repetitive tickets on its own.
Keep reading
Guide
Free Discord Ticket Bots in 2026: What You Actually Get
What "free" really means for a Discord ticket bot: which options are free forever, which cap AI usage, what always costs money, and how to pick without building your support flow on a feature you will lose.
Guide
How to Train an AI Ticket Bot for Discord (Step by Step)
A practical guide to teaching a Discord AI ticket bot your own rules: what to train first, how to write facts it actually uses, how to check what it learned, and how to fix a wrong answer.
Guide
Discord Support Analytics: The Numbers Worth Tracking
Which Discord support metrics actually tell you something, which ones look useful and mislead, how to credit staff fairly, and how to read AI resolution rates without fooling yourself.