> For the complete documentation index, see [llms.txt](https://cesium.gitbook.io/cesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesium.gitbook.io/cesium-docs/account/discord.md).

# Discord

Linking Discord to your Cesium account is how beta access reaches you.

Linking Discord to your Cesium account is how beta access reaches you.

## Why link

Beta access is given out in the Cesium Discord server at [cesiumclient.com/discord](https://discord.gg/3QBFFwbbH). When your Discord is linked to your Cesium account, that access follows your account automatically. Support in the server can also look up your account faster.

## Linking

{% stepper %}
{% step %}
Sign in to the dashboard and open Account.
{% endstep %}

{% step %}
Next to Discord, click Link.
{% endstep %}

{% step %}
Approve the Discord authorization prompt.
{% endstep %}
{% endstepper %}

Your Discord username shows on the Account page once linked.

## Unlinking

Click Unlink on the Account page. Then link the right Discord account. If your Discord is attached to a Cesium account you do not have access to, see [Discord linked to the wrong account](/cesium-docs/support/wrong-discord-account.md).

## One Discord, one account

A Discord account can be linked to one Cesium account at a time.


---

# 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://cesium.gitbook.io/cesium-docs/account/discord.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.