> ## Documentation Index
> Fetch the complete documentation index at: https://hashbot.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Hashbot Role & Other Bots

> When Hashbot is invited to your server, Discord will automatically create a new role named **Hashbot**.

## Adjusting Role Position

To function properly, the **Hashbot role must be positioned above** any role it needs to moderate, including:

* Member roles
* Verified or Holder roles
* Custom roles assigned to regular users
* Roles assigned to bots that Hashbot may act upon

<Info>
  **Why this matters:**\
  Discord does not allow a bot to moderate (kick, ban, timeout, etc.) users whose roles are equal to or higher than its own.
</Info>

### How to adjust role position:

1. Open your **Server Settings**
2. Navigate to the **Roles** section
3. Drag the **Hashbot** role above the roles it needs to manage
4. Click **Save Changes**

## Working with Other Bots

Some moderation tools—like **Wick**, **Beemo**, or **Sentry**—may restrict or quarantine new bots by default.

To prevent permission conflicts:

* Add Hashbot to any **Trusted Admin list** or allowlists maintained by other bots
* Ensure the **Hashbot role is higher** than other bot roles in your role hierarchy
* Confirm that no automation is muting, timing out, or stripping permissions from Hashbot
* Avoid overlapping moderation triggers (e.g., two bots banning on join), which can create instability or duplication

<Tip>
  Regularly review your server's bot roles and settings to prevent unintended conflicts between moderation tools.
</Tip>

<Frame caption="Role Hierarchy and Bot Conflicts">
  <iframe src="https://www.loom.com/embed/c4e84868c63844b8965ce02b46e01534?sid=02156515-7288-49c1-a5d4-043ec82fcc85" allowfullscreen scrolling="no" allow="encrypted-media *;" height="420" width="100%" />
</Frame>
