> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/troubleshooting/cant-access-dashboard.md).

# I can't access the dashboard

## You don't see any servers

To manage a server on the dashboard you need one of these:

* Discord **Administrator** or **Manage Server** in that server, or be the server owner.
* A role in that server that has been granted dashboard access. Those servers show under **Servers You May Have Access To** on the server picker.
* A temporary dashboard access link that someone shared with you.

You also need Ticket King to be in the server. If you just added the bot, wait about 30 seconds, then sign out and sign back in so your server list refreshes.

## A specific server doesn't appear

Check these:

1. **Are you still in the server?** If you left, its card disappears.
2. **Do you have access?** You need Administrator, Manage Server, ownership, or a role that was granted dashboard access. Without one of these the server does not show.
3. **Did your roles change recently?** Sign out and back in to refresh.
4. **Is the server very large?** For very large servers the list can take a moment to refresh. Wait a minute and retry.

## Sign-in keeps looping

* Sign out fully from the profile menu in the top right.
* Clear cookies for `discord.com` and `ticketking.xyz`.
* Try a private or incognito window.
* Sign in again.

If it still fails, reach out on the [support Discord](https://ticketking.xyz/support).

## The dashboard says you don't have permission

You are signed in, but a page or action is refused. Three reasons:

1. **You lack the dashboard permission for that section.** Each section has its own permission area. Ask the server owner to grant your role the area you need. See [Dashboard permission areas](/docs/permissions-and-your-support-team/permission-areas.md).
2. **You are using a temporary access link.** A temporary link gives owner-level access except it cannot manage dashboard permissions. So you cannot grant access to yourself or others while on a temporary link.
3. **The feature is** <i class="fa-crown">:crown:</i> **Premium.** On a free server, premium pages show a locked preview instead of the page. Subscribe from your dashboard's Premium page.

## Changes aren't saving

* Make sure you clicked **Save** on the unsaved-changes bar at the bottom of the page. Some pages, such as Settings, save on their own.
* Fix any fields with red borders first. They block saving.
* If the dashboard saved but the bot's behavior has not changed yet, wait up to a minute for the change to reach the bot.

## Related

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

{% content-ref url="/pages/L19Le8ZsA0TPLKv2tkjt" %}
[Open your dashboard](/docs/getting-started/open-your-dashboard.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://ticketking.xyz/docs/troubleshooting/cant-access-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.