Discord Ticket Bot Permissions Explained (and the 6 That Break Setups)
What permissions a Discord ticket bot needs, why Manage Roles is the one everyone misses, the role hierarchy trap, and how to fix each failure by its symptom.
Dani, Founder, AI Ticket Bot
6 min readUpdated
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. Your staff see the channel; the member does not; nobody can work out why.
The role hierarchy trap
Permissions are not the only gate. Discord also enforces role position.
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:
Specific permission set
- Cannot delete channels or ban members
- A missing permission fails loudly, so you fix it
- Carried by the invite link, so it is the same number of clicks
- Auditable: you can say what the bot can do
Administrator
- Can do anything, including both
- Everything works until the day you remove it
- Also carried by the invite link, so it saves nothing
- Not auditable in any useful sense
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.
The permissions a connected second bot needs
If you run two ticket bots, or you are adding an AI layer to a bot you already have, there is one extra requirement worth knowing about.
View Audit Log is what lets a bot detect that another bot created a ticket channel. Without it, nothing happens at all and there is no error, because the event was never seen. On top of that, the second bot needs to be able to see and send in those private ticket channels, which usually means adding it to the first bot's ticket access settings the same way you would add a staff role. We cover the whole setup in adding AI to a ticket bot you already run.
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.
On AI Ticket Bot there are fourteen, set per role and grouped by the question you are actually asking: what can this role do with a ticket, how can it reply, what can it see, and what can it do with the AI and with moderation. Four ready-made sets cover the common answers in one tap.
Per-role staff permissions worth setting deliberately
- Claim tickets
- Take ownership so two people do not answer the same ticket at once
- Close tickets
- Not everyone who can read tickets should be able to close them
- See every ticket
- This one is a Discord channel permission, not a filter. Without it a role only sees the tickets it is pinged for
- Read transcripts
- Every closed conversation in the server, including ones the role never touched
- Manage the blacklist
- Blocking abusers, without handing anyone Manage Server
- Teach the AI
- Decides who can teach the brain. Keep this tight, because a wrong fact taught here gets repeated to every member who asks
The last three are the ones worth being deliberate about, because they reach past a single ticket. A new role gets none of them by default.
These are per-role and server-authoritative, so the server owner decides, not the bot. Every one is re-checked on the bot side each time, including when the action is started from the dashboard, so there is no path where a web page lets someone through.
There is also a role hierarchy guard on unclaiming, so a junior staff member cannot yank a senior's claimed ticket.
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 reading transcripts and teaching the AI
- Add View Audit Log only if you plan to connect a second ticket bot
Troubleshooting, by symptom
- Nothing happens when I press the button
- The bot cannot View Channel, or the panel message is stale. Republish the panel
- Ticket opens but the member cannot see it
- Manage Roles is missing, or the bot's role sits below theirs
- Bot posts the panel but never replies
- A channel overwrite denying Send Messages in that specific channel
- Transcript is empty
- Read Message History is missing
- Embeds look broken or blank
- Embed Links is missing
- Works in one channel, not another
- Always a channel overwrite. Check the channel, not the role
- The AI never answers in another bot's tickets
- View Audit Log is missing, or our bot has no access to those private channels
If you are setting a bot up from scratch rather than debugging one, the full setup walkthrough covers the panel, categories and staff wiring too, and on AI Ticket Bot a single /setup command builds all of it and repairs the permissions it can.
Keep reading
Frequently asked questions
Manage Channels, Manage Roles, View Channel, Send Messages, Embed Links, Attach Files and Read Message History. View Audit Log is needed only if you want the bot to detect ticket channels created by a second ticket bot. Grant that specific set rather than Administrator.
Because when a ticket channel is created the bot has to grant the person who opened it permission to see that channel. Discord requires a bot to hold the permissions it is granting, so without Manage Roles the ticket opens and nobody can be let in. The symptom is a ticket that exists but the member cannot see.
No. It is not simpler, because the invite link already carries the specific set, and it is worse in two ways: a compromised or misbehaving bot with Administrator can delete channels and ban members, and Administrator hides misconfiguration until the day you remove it.
Almost always role position. A bot can only manage roles positioned below its own role in your server settings, so if the bot's role sits at the bottom of the list it cannot grant ticket access no matter which boxes you ticked. Drag the bot's role above your member and staff roles.
A channel overwrite. Server-level permissions are the floor and a channel can take them away again. The classic case is a support channel with an old overwrite denying Send Messages to everyone, so the panel posts and the bot cannot reply. Check the specific channel's permissions, not the role's.
No, and it is worth keeping them separate in your head. Discord permissions decide what the bot can do. Staff permissions decide what your team can do inside tickets, and they are configured in the bot rather than in Discord. On AI Ticket Bot there are fourteen of them per role, grouped into what a role can do with tickets, how it can reply, what it can see, and its AI and moderation powers.
It’s not just an AI, it’s your AI.
See it on your own server.
Add the bot free, teach it a few of your most common answers, and watch it clear the repeat tickets on its own.
Free plan, no card. Your first panel starts 14 days of Premium.
Keep reading.
All articlesDiscord Ticket Logs: Four Events, Four Channels, One Blind Spot
Ticket log channels are free on every plan and set per event, so opens, claims, closes and transfers can each land somewhere different. What each one carries.
9 min read
How to Open a Ticket in Discord (and What Decides If It Opens)
Members open a ticket by pressing a button on a panel. Behind that press sit five steps in a fixed order, and five routes in that do not all pass them.
9 min read
Discord Ticket Panel Design: What You Can Change, and What Discord Decides
The ticket panel is designable on every plan. What you can change, the two layouts, how members pick a category, and the rules Discord imposes on all of it.
9 min read