> 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/it/per-iniziare/open-your-dashboard.md).

# Apri la tua dashboard

Accedi su ticketking.xyz per configurare il bot.

La dashboard di Ticket King è il posto in cui configuri tutto: pannelli, ruoli di supporto, registrazione, personalizzazione e ogni impostazione. Il bot Discord è la parte che vedono i tuoi membri. La dashboard è il posto in cui lo configuri.

<a href="https://ticketking.xyz/dashboard" class="button primary" data-icon="right-to-bracket">Apri la tua dashboard</a>

## Accesso

{% stepper %}
{% step %}

### Vai su ticketking.xyz e clicca su Dashboard

Vai a [ticketking.xyz](https://ticketking.xyz) e fai clic su **Dashboard**.

<figure><img src="https://469467122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIuyxzUxhbWXnqK9hufg3%2Fuploads%2Fgit-blob-aad319a2f22586fe4ad86355598047477e95dd49%2Fhomepage-dashboard-button.png?alt=media" alt="The ticketking.xyz homepage with the Dashboard button"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Accedi con Discord

Accedi con Discord. Se è la prima volta, Discord ti chiederà di autorizzare l'accesso.

<figure><img src="https://469467122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIuyxzUxhbWXnqK9hufg3%2Fuploads%2Fgit-blob-56f52f8ab80b9043f44be01d99ea081059226e99%2Fdashboard-step-signin.png?alt=media" alt="Discord&#x27;s authorize screen for signing in to the dashboard"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Scegli il server che vuoi configurare

Scegli il server che vuoi configurare. Tutto qui.

<figure><img src="https://469467122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIuyxzUxhbWXnqK9hufg3%2Fuploads%2Fgit-blob-be87452a63e4a5cb1d9480a0ba1d8a9da9866459%2Fdashboard-step-pick-server.png?alt=media" alt="The Server Management page showing a grid of server cards"><figcaption></figcaption></figure>

→ [Scegli il tuo server](https://ticketking.xyz/docs/it/per-iniziare/pick-your-server.md)
{% endstep %}
{% endstepper %}

## Problemi di accesso

* Se continua a chiederti di accedere più e più volte, cancella i cookie del browser per `discord.com` e `ticketking.xyz` e riprova.
* Se il tuo server non appare dopo l'accesso, potresti non avere **Gestisci server** o **Amministratore** in quel server (o esserne il proprietario), oppure Ticket King potrebbe non essere ancora stato invitato.

→ [Non riesco ad accedere alla dashboard](https://ticketking.xyz/docs/it/risoluzione-dei-problemi/cant-access-dashboard.md)

## Avanti: scegli il tuo server

{% content-ref url="/pages/394e69ad4cf570fc8399d196848e626bf79dfc3f" %}
[Scegli il tuo server](https://ticketking.xyz/docs/it/per-iniziare/pick-your-server.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/it/per-iniziare/open-your-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
