# The two layers of permissions

Permissions in Ticket King work at two layers. One is your normal Discord roles. The other is Ticket King's own dashboard permissions.

## Layer 1. Your Discord roles

This is the standard Discord permission system. Members have roles, and roles grant Discord permissions.

Ticket King uses Discord roles for:

* **Who can see a ticket channel.** The bot sets channel access so only the right people see each ticket.
* **Who can manage tickets in Discord.** Anyone with Manage Channels or Manage Server, plus the server owner, can run ticket commands like `/claim` and `/close`. Discord Administrators also pass.

## Layer 2. Ticket King dashboard permissions

This is Ticket King's own system, separate from Discord. It controls what each role can do on the dashboard at ticketking.xyz. Each area is turned on per Discord role:

| Area                     | Unlocks                                 |
| ------------------------ | --------------------------------------- |
| Info & Statistics        | The Statistics page.                    |
| Manage Panels            | Panels, Templates, and Public Presets.  |
| View History             | Ticket History and Steam Linking.       |
| View Application History | The application submission history.     |
| Review Applications      | Approving or denying applications.      |
| Manage Commands          | The Custom Commands page.               |
| Manage Settings          | The Settings page and Bot Personalizer. |
| View Audit Logs          | The Audit Logs page.                    |
| Manage Permissions       | The Permissions page itself.            |
| Manage Premium           | The premium subscription page.          |

There is also a **Full Access** toggle per role that turns them all on at once.

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

## How the two layers work together

The two layers do different jobs. A user can have one without the other.

| Task                                   | Needs Discord role access | Needs dashboard permission |
| -------------------------------------- | ------------------------- | -------------------------- |
| Reading and replying in a ticket       | Yes                       | No                         |
| Closing a ticket with `/close`         | Yes                       | No                         |
| Editing a panel on the dashboard       | No                        | Yes                        |
| Granting another role dashboard access | No                        | Yes                        |

For example, a junior moderator with a support role can see and reply in tickets but cannot change panel settings without a dashboard permission. A lead moderator has both.

## Who bypasses these checks

* The **server owner** always has full access.
* Anyone with Discord **Administrator** or **Manage Server** bypasses the dashboard permission checks. They are still subject to normal Discord channel permissions.

{% content-ref url="/pages/SlvQjhFgYNRVLgp6h7E8" %}
[Owners and Administrators](/docs/permissions-and-your-support-team/owners-and-administrators.md)
{% endcontent-ref %}

## Support roles are a separate idea

Support roles are not the same as either layer. They decide who gets added to and pinged in ticket channels. You can set them server-wide, per panel, and per option. Server-wide support roles always apply to every ticket.

{% content-ref url="/pages/UIA35ZwZnGsgiE5BmK60" %}
[Support roles](/docs/permissions-and-your-support-team/support-roles.md)
{% endcontent-ref %}

## A simple way to think about it

* Discord roles and channel access control what members can see and do inside Discord.
* Dashboard permissions control what members can configure on the dashboard.
* Support roles control who gets added to and pinged in tickets.

A typical staff role has all three: a Discord support role, the Manage Panels and View History dashboard permissions, and a spot in your server-wide support roles.


---

# 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/permissions-and-your-support-team/two-layers.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.