Discord Permissions

What the bot needs, and why. Grant these guild-wide or on every category tickets use — or grant Administrator to skip the checklist.

Permission	Used for
Manage Channels	Creating and deleting ticket channels, and setting their permission overwrites.
Manage Roles	Changing who can see a ticket after it's created: claiming, unclaiming, moving, /add, and /remove.
Create Private Threads	Only for thread-based categories.
Send Messages in Threads	Only for thread-based categories.
Manage Threads	Only for thread-based categories: removing someone with /remove.
View Channels	Seeing the channels it manages.
Send Messages	Posting the panel, welcome messages, and logs.
Embed Links	Dashboard, ticket, and log embeds.
Attach Files	Delivering transcripts.
Read Message History	Generating transcripts and detecting inactivity.
Mention @everyone, @here, and All Roles	Only if Staff Can Ping Roles is on. Discord won't let the bot give staff a permission it doesn't have itself.

Catching missing permissions early

When you pick a department's channel in /ticket-dashboard, the bot warns you if it's missing Manage Channels (or Create Private Threads) there. The web dashboard shows the same warning in the department editor.

If a member sees "unable to create the ticket channel", the bot is missing one of these permissions on that department's category or channel.

Role hierarchy

The bot's role must sit high enough to manage the channels and roles involved. If you see Missing Permissions, move the Ticket Nexus role higher.