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

# Discord

## Error Getting Roles. Check your Permissions. <a href="#error-getting-roles" id="error-getting-roles"></a>

This can be caused by two reasons:\
\
1\) You need to try to invite the bot from an incognito window to make sure your cache / cookies are cleared. \
\
2\) You need to grant the bot the proper permissions as outlined in:

{% content-ref url="/pages/-MWni8hhcJqquC9I9vQw" %}
[Getting Started](/getting-started.md)
{% endcontent-ref %}

## **Admin or Moderator can't see or edit settings** <a href="#admin-mod-cant-see-upgrades" id="admin-mod-cant-see-upgrades"></a>

**Admins CAN edit and manage the bot.** You must make sure this person is **ACTUALLY an ADMIN in Discord** in order to see or edit settings in the control panel. The role they have **MUST** have ADMINISTRATOR permissions with their role in your server:&#x20;

![](/files/-M6KWoIlNUdWYCdN6tdm)

## The bot responds in every channel? Does it need to be administrator? <a href="#responds-all-channels" id="responds-all-channels"></a>

You control access to the channels, you can prevent the bot from speaking in certain channels by removing admin privileges from the bot but allow it to send messages, links, add, remove, ban, and  send embeds, then prevent it from talking / seeing the channel that you don't want it to talk in. This involves you setting Discord perms. **We do not guarantee that the bot will function correctly since we add new features all the time that may require different permissions.**

## User logged in / paid with the wrong Discord account, what can I do? <a href="#wrong-user-account" id="wrong-user-account"></a>

You can use the Transfer Command or the customer can use the Transfer Command. Swap an upgrade from one user to another. Use this if one of your users mistakenly upgraded with a wrong account.&#x20;

**FOR MERCHANTS:**&#x20;

> ```
> $transferUpgrade  Purchaser DiscordID  Recipient DiscordID
> ```

**FOR CUSTOMERS:**

```
$TransferMyUpgrade  Recipient DiscordID OR Username
```

{% hint style="warning" %}
If you get an error that the subscription cannot be transferred or the user has no subscription, the user receiving the role needs to go to the checkout page to be registered within the Upgrade.Chat Database. They do not need to purchase, just simply log in on the checkout page.&#x20;
{% endhint %}

{% content-ref url="/pages/-MK6yQIAWvMZEAt-ldji" %}
[Broken mention](broken://pages/-MK6yQIAWvMZEAt-ldji)
{% endcontent-ref %}

{% hint style="danger" %}
**THE BOT WILL NOT TRACK USERS THAT WERE MANUALLY GIVEN ROLES. THEY MUST SIGN UP WITH THE BOT.  THE TRANSFER COMMANDS ARE THE ONLY WAY THAT THEY WILL BE TRACKED IF YOU NEED TO MIGRATE!**
{% endhint %}


---

# 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://docs.upgrade.chat/general-questions/troubleshooting/discord.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.