# Permissions Ticket King needs in Discord The recommended invite link grants Ticket King the Discord permissions it needs. The easiest setup is to use that link and leave the bot's permissions as they are. {% hint style="info" %} Use the recommended invite link: {% endhint %} ## What the bot uses each permission for The recommended invite includes **Administrator** as a convenience, which covers everything below in one grant. If you would rather not give Administrator, remove it after inviting and grant these specific permissions instead. The bot works the same way. | Permission | Why Ticket King needs it | | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Administrator** | Included in the recommended invite as a convenience. Optional. It can be replaced by the specific permissions below. | | **Manage Channels** | Create, rename, and delete ticket channels. | | **Manage Roles** | Set who can see each ticket, by writing per-user and per-role access on the channel. | | **Manage Messages** | Tidy up bot messages, and remove a panel message when you move or resend it. | | **Manage Threads** | Close thread tickets. | | **Create Public Threads** and **Create Private Threads** | Create thread tickets and private staff threads. | | **Send Messages in Threads** | Reply inside thread tickets. | | **View Channel** | Read panel channels and ticket channels. | | **Send Messages** | Post panels and reply in tickets. | | **Embed Links** | Show the bot's embeds (welcome messages, logs, panels). | | **Attach Files** | Let ticket members attach files. | | **Read Message History** | Build transcripts. | | **Add Reactions** | For some interactive prompts. | | **Use External Emojis** and **Use External Stickers** | Show emojis and stickers from other servers on buttons, panels, and ticket messages. | | **Use Application Commands** | So Ticket King's slash commands work in your server. | | **Mention @everyone, @here, and All Roles** | Ping your support roles when a ticket opens. This permission covers pinging any role, including roles that are not set as mentionable. Most staff and support roles are not set as mentionable, so the bot needs this permission to ping your support team. | ## What breaks if a permission is missing | Missing permission | What breaks | | --------------------------------------- | ----------------------------------------------- | | Manage Channels | The bot cannot create ticket channels. | | Manage Roles | Tickets open, but staff cannot see them. | | View Channel | The bot cannot see or post anywhere. | | Send Messages | The bot cannot post panels or replies. | | Embed Links | Embeds show as plain text and are hard to read. | | Read Message History | Transcripts come out empty. | | Manage Threads | Thread tickets fail to open or close. | | Mention @everyone, @here, and All Roles | The bot cannot ping your support roles. | ## Make sure the bot's role is high enough In Discord, open **Server Settings**, then **Roles**, and drag the **Ticket King** role above any support role it needs to manage. A bot cannot manage roles that sit above its own role. ## How the bot keeps tickets private Inside each ticket the bot sets channel access directly: the ticket author and your support roles get access, and everyone else has the channel hidden. This is how only the right people can see a ticket. ## Related {% content-ref url="/pages/uXg0kpOfy9oBJvaeJhN8" %} [The two layers of permissions](/docs/permissions-and-your-support-team/two-layers.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ticketking.xyz/docs/reference/discord-permissions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.