# Permissions

<details>

<summary>What's the difference between Discord roles and dashboard permissions?</summary>

* **Discord roles** control what members can do inside Discord, such as which channels they see and whether they can post.
* **Dashboard permissions** control what users can do on the dashboard at ticketking.xyz.

They are independent. A user can have Discord channel access without dashboard access, or the other way around.

→ [The two layers of permissions](/docs/permissions-and-your-support-team/two-layers.md)

</details>

<details>

<summary>Why does one teammate see all dashboard pages but I don't?</summary>

They most likely have Discord's **Administrator** or **Manage Server** permission, or they are the server owner. Any of those gives full dashboard access and bypasses the dashboard permission areas.

To see the same pages, ask the owner to grant your role the dashboard permissions you need.

→ [Dashboard permission areas](/docs/permissions-and-your-support-team/permission-areas.md)

</details>

<details>

<summary>I'm blocked from a panel I should be able to use</summary>

One of your roles is on a blocked list. Check these:

* The server-wide **Blocked Roles** list in Settings. A role here is blocked from opening tickets and using bot commands across the whole server.
* The panel's **Default Blocked Roles**. A role here is blocked from every option on that panel.
* The option's **Blocked Roles**. A role here is blocked from that one option.

The per-panel and per-option blocked roles are a <i class="fa-crown">:crown:</i> Premium feature. The server-wide list is free.

Ask a server admin to remove the role from the blocked list, or to remove the blocked role from you.

</details>

<details>

<summary>A staff member can claim but can't close</summary>

Check **Close Requires Support Role** in Settings. When it is on, only a support role, Manage Channels, Manage Server, or the server owner can close a ticket. The ticket author can no longer close their own. If your staff member can claim but not close, confirm they hold a support role or one of those Discord permissions.

→ [A support role can't close a ticket](/docs/troubleshooting/support-role-cant-close.md)

</details>

<details>

<summary>A new staff role doesn't see new tickets</summary>

Two checks:

1. **The role is set as a support role**, server-wide or per panel or per option.
2. **Ticket King's role sits above the support role** in Discord's role list.

When both are true, future tickets include the role. Tickets that are already open keep the access they had when they opened, so you would add the role to those channels by hand.

</details>

<details>

<summary>Can a role manage tickets without being a server admin?</summary>

Yes. Add the role as a support role at the relevant level (server / panel / option). The role doesn't need any Discord permissions beyond what the bot grants per-channel.

</details>

<details>

<summary>A user with Discord Administrator can bypass everything?</summary>

In the dashboard, yes. They see every page no matter what dashboard permissions are set. On the Discord side, also yes, because Administrator includes every Discord permission.

This lets an owner recover from a misconfiguration. Limit who you give Administrator to.

</details>

<details>

<summary>How do I let a friend temporarily help me set up the bot?</summary>

Use [Temporary Dashboard Access](/docs/permissions-and-your-support-team/temporary-dashboard-access.md). It is a short-lived link that gives one person dashboard access without joining Discord. You can set it to 30 minutes, 1 hour, 3 hours, or 6 hours, and revoke it when you are done.

</details>

<details>

<summary>What's the maximum number of roles I can give dashboard access?</summary>

Up to 50 roles per server.

</details>

<details>

<summary>Why can't I grant @everyone permissions?</summary>

The role picker leaves out @everyone and bot-managed roles. You add specific Discord roles instead.

</details>

## Related

{% content-ref url="/pages/RK4hI1VK3OmRDu2Okj2Y" %}
[Dashboard permission areas](/docs/permissions-and-your-support-team/permission-areas.md)
{% endcontent-ref %}

{% 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/faq/permissions.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.