# Setup

<details>

<summary>How do I install Ticket King?</summary>

Click the invite link at [ticketking.xyz/invite](https://ticketking.xyz/invite?via=docs), pick your server, authorize.

→ [Invite Ticket King](/docs/getting-started/invite-ticket-king.md)

</details>

<details>

<summary>What permissions does the bot need?</summary>

The recommended invite link grants a specific bundle: View Channel, Send Messages, Manage Channels, Manage Roles, Embed Links, Read Message History, plus thread-related permissions.

→ [Permissions Ticket King needs in Discord](/docs/reference/discord-permissions.md)

</details>

<details>

<summary>How do I create my first panel?</summary>

Three options:

1. **Dashboard wizard.** In the sidebar open Panels, then click New Panel and walk through the steps.
2. **`/quicksetup` slash command.** A 3-step wizard inside Discord that sets your staff roles, a log channel, and the panel channel.
3. **`/panel` slash command.** Posts a basic ticket panel in the current channel using defaults. Edit it afterward on the dashboard.

→ [Build your first panel](/docs/getting-started/build-your-first-panel.md)

</details>

<details>

<summary>How do I make only staff close tickets?</summary>

Turn on **Close Requires Support Role** in Settings, under Ticket Close & Transcript Settings. When it is on, the ticket author can no longer close their own ticket. A support role, Manage Channels, Manage Server, or the server owner can still close it.

→ [Closing a ticket](/docs/tickets/closing-a-ticket.md)

</details>

<details>

<summary>Why don't Required Roles work on my server?</summary>

<i class="fa-crown">:crown:</i> Required Roles is a Premium feature. On a free server you can set it, but it only takes effect once the server has premium.

→ [Premium feature list](/docs/premium/feature-list.md)

</details>

<details>

<summary>Why does the bot say a channel is not a ticket?</summary>

The bot replies "You cannot interact with this channel since it is not a ticket." when you run a ticket-only command, like `/claim` or `/close`, in a regular channel. These commands only work inside a ticket channel.

</details>

<details>

<summary>Why are my members told the server reached the maximum amount of tickets?</summary>

The server has hit **Max Active Tickets** (default 500). Raise it in Settings, under Server Settings & Logging, or close some old tickets to free up room.

</details>

<details>

<summary>How do I move a panel to a different channel?</summary>

Open the panel in the editor, change the panel channel field, save. The bot deletes the old message and posts a new one in the new channel.

→ [Move a panel](/docs/panels/move-a-panel.md)

</details>

<details>

<summary>How do I add my support team?</summary>

**Settings → Support Roles** to set server-wide support roles. They're added to every ticket automatically and can `/claim`, `/close`, etc.

For per-panel or per-option overrides, configure in the panel editor.

→ [Support roles](/docs/permissions-and-your-support-team/support-roles.md)

</details>

<details>

<summary>How do I let my admin team configure the dashboard?</summary>

Sidebar → **Permissions** → add their Discord role → grant the dashboard permissions they need.

→ [Giving a role dashboard access](/docs/permissions-and-your-support-team/giving-a-role-dashboard-access.md)

</details>

## Related

{% content-ref url="/pages/AfTtLnv8UVmSkrL5hGIi" %}
[General](/docs/faq/general.md)
{% endcontent-ref %}

{% content-ref url="/pages/FyuYRXVNy5gGJzlTLeRS" %}
[Permissions](/docs/faq/permissions.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/faq/setup.md?ask=<question>
```

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.