# Help with Permission Problems

## Troubleshooting Bot Permissions in Discord Servers

If you’ve invited <mark style="color:red;">InHouseQueue</mark> to your Discord server, but you get "Bot is missing permissions" errors, this guide should hopefully help resolve the issue.

***

## Important

The <mark style="color:red;">InHouseQueue</mark> Support team <mark style="color:green;">**cannot**</mark> provide permission troubleshooting beyond what's covered in this article. We can't access every server to diagnose permission problems. If you're a server owner, admin, or moderator, it's your responsibility to understand how [Discord Permissions](https://support.discord.com/hc/en-us/articles/206141927-How-is-the-permission-hierarchy-structured) work.

Problems **specific** to InHouseQueue Discord Bot we can always help with!

[Support Server](https://discord.com/invite/NDKMeT6GE7)

#### **1. Check InHouseQueue's Role**

* **Verify Bot Role Placement:**\
  Go to **Server Settings → Roles**, and ensure <mark style="color:red;">InHouseQueue</mark>'s role is <mark style="color:green;">**above**</mark> the roles it needs to manage. For example:
  * <mark style="color:red;">InHouseQueue</mark> needs to manage channels and permissions, so its role (`In House Queue`) should be high enough to perform those actions.

<div align="left"><figure><img src="/files/PzjZMaNNyqIh962VRonh" alt="" width="401"><figcaption></figcaption></figure></div>

* **Role Permissions:**\
  Edit <mark style="color:red;">InHouseQueue</mark>'s role and confirm it has all necessary permissions. It needs:
  * Manage Server
  * Manage Roles
  * Manage Channels
  * View Channels
  * Send Messages
  * Manage Messages
  * Embed Links
  * Read Message History
  * Use External Emoji
  * Use Application Commands
  * Move Members

***

#### **2. Check Channel-Specific Permissions**

* Right-click on a channel where <mark style="color:red;">InHouseQueue</mark> isn’t working → **Edit Channel** → **Permissions**:
  * Ensure <mark style="color:red;">InHouseQueue</mark> has the following permissions:
    * Manage Channel
    * Send Messages
  * For Categories:
    * Manage Channel
    * Send Messages

<div align="left"><figure><img src="/files/Faq7cGlXn3tFDU2u0LcV" alt="" width="401"><figcaption></figcaption></figure></div>

* If you’re using category-level permissions, ensure these are correctly inherited by the channels within the category.

<mark style="color:red;">InHouseQueue</mark> should <mark style="color:green;">**automatically**</mark> have all of these permissions after you've done the [Basic Setup](/docs/quick-start.md). If you still get permission errors, it means your Discord Role permissions are complex and something is overriding the base permissions. If you have a "Bots" or "Members" Discord role in your server, try giving this role to <mark style="color:red;">InHouseQueue</mark>.

***

#### **3. Re-Invite InHouseQueue with Correct Permissions**

* If <mark style="color:red;">InHouseQueue</mark> was invited without all necessary permissions, you can try re-inviting it using the invite link [here](https://discord.com/oauth2/authorize?client_id=1001168331996409856).

***

#### **4. Ensure InHouseQueue Is Active**

* Check if <mark style="color:red;">InHouseQueue</mark> is <mark style="color:green;">**online**</mark>. If it’s offline:
  * Visit the [Support Server](https://discord.com/invite/NDKMeT6GE7) for latest updates.
* Ensure <mark style="color:red;">InHouseQueue</mark> is not **muted** from the server.

***

#### **5. Enable Slash Commands**

* Ensure <mark style="color:red;">InHouseQueue</mark> has slash commands enabled, go to **Server Settings → Integrations → Bots and Apps**:
  * Make sure <mark style="color:red;">InHouseQueue</mark> is listed and has slash commands enabled.
  * Check <mark style="color:green;">**Command Permissions**</mark> to ensure server members have access to <mark style="color:red;">InHouseQueue</mark>’s commands.

<div align="left"><figure><img src="/files/uVSYGGVcEOhYbxVSBGBB" alt="" width="401"><figcaption></figcaption></figure></div>

***

#### **6. Most Common Issues**

* **Role Placement:** <mark style="color:red;">InHouseQueue</mark>’s role should always be high enough to manage roles and channels it interacts with.
* **Basic Roles:** Ensure <mark style="color:red;">InHouseQueue</mark> has "Members" or "Bots" Discord role if your server has one. This is likely the case in big servers with complex permissions.

***

#### Last Resort

As a last resort, you can give <mark style="color:red;">InHouseQueue</mark> <mark style="color:green;">**Administrator**</mark> permissions. This is usually not advised, but this will resolve any permission issues. Once you've confirmed providing <mark style="color:green;">**Administrator**</mark> works, you can begin to narrow down the permissions, or leave it.

{% hint style="warning" %}
We don't recommend giving **ANY** Discord Bots **Administrator** permissions. But this usually solves the issue.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.inhousequeue.xyz/docs/quick-start/trouble-shooting-ihq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.