> 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/support/wrong-discord-account.md).

# My Discord is linked to the wrong Cesium account

Unlink Discord from the account it is on, then link it to the right one.

{% hint style="info" %}
Unlink Discord from the account it is on, then link it to the right one.
{% endhint %}

## If you can sign in to both Cesium accounts

{% stepper %}
{% step %}
Sign in to the Cesium account that currently has the Discord link.
{% endstep %}

{% step %}
Open Account and click Unlink next to Discord.
{% endstep %}

{% step %}
Sign out, sign in to the correct Cesium account.
{% endstep %}

{% step %}
Open Account and click Link. Approve the Discord prompt.
{% endstep %}
{% endstepper %}

## If you cannot sign in to the account that has the link

You cannot unlink from the outside. Ask in [Discord](https://discord.gg/3QBFFwbbH) with the email of the account you want the link moved to.

## Why it matters

Beta access is given through Discord and follows the linked account. If the link is on the wrong account, that account gets the access.

See also [Discord](/cesium-docs/account/discord.md).


---

# 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/support/wrong-discord-account.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.