> ## 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.

# Allowlist

> Prevent trusted users and roles from being flagged or punished by Hashbot.

### What is the Allowlist?

Allowlisted users and roles are **exempt from all Hashbot actions** — bans, kicks, and timeouts — even if they match a name filter, profile picture, or keyword.

> Allowlisted users do **not** gain Manager access and cannot modify Hashbot settings. For configuration access, use [Manager roles](/manager) instead.

<Tip>
  You can manage your entire allowlist from the [Hashbot Dashboard](https://dashboard.hashbot.com) — add, remove, and review entries without slash commands.
</Tip>

### When to Use the Allowlist

* **Moderators** who may trigger impersonation filters
* **Team members** who need protection without admin rights
* **Trusted bots** (e.g., Wick, Beemo, Sentry)
* **VIPs** or high-profile users whose names resemble filtered terms

<Check>
  Allowlisting ensures that trusted users are never mistakenly moderated by Hashbot.
</Check>

### How to Add to the Allowlist

Use the `/allowlist add` command to allowlist roles or users:

```
/allowlist add role:@Moderators
/allowlist add user:@username
/allowlist add user-id:146613143592894464
```

### How to Remove from the Allowlist

```
/allowlist remove role:@Moderators
/allowlist remove user:@username
/allowlist remove user-id:146613143592894464
```

### View Your Current Allowlist

Run `/allowlist list` to see a count of allowlisted roles and users, with a **"Manage on Dashboard"** button linking to [dashboard.hashbot.com](https://dashboard.hashbot.com).

<Frame>
  <iframe src="https://www.loom.com/embed/58ada753580445b98cf81ffae8eb7fe4?sid=375b644b-5ebc-4d6d-9c4a-60ea685b3e43" allowfullscreen scrolling="no" allow="encrypted-media *;" height="420" width="100%" />
</Frame>

### Role-Based Allowlist Behavior

When you allowlist a **role**, all members with that role are automatically protected. Members stay on the allowlist even after the role is removed — this prevents accidental exposure if a role is briefly unassigned.

You cannot remove a user from the allowlist while they hold an allowlisted role. Remove the role first, then remove the user individually if needed.

<Info>
  If your server was using Hashbot before October 2025 and some members aren't properly allowlisted, run `/allowlist migrate` to sync existing role members to the individual allowlist.
</Info>

### Auto-Pilot

When **Auto-Pilot** is enabled, every allowlisted and manager member automatically gets name and PFP filters created for them. If someone impersonates a protected member, Hashbot catches it — and filters update automatically when members change their profile.

You can also limit protection to specific roles using the **role picker** in the Dashboard settings.

[Learn more about Auto-Pilot](/filter-sync)

### Best Practices

* Only allowlist roles you fully trust
* Add essential bots to avoid unintended moderation
* Avoid allowlisting broad roles like `@everyone`
* Review your allowlist regularly with `/allowlist list` or on the Dashboard

### Need Help?

If you need support with allowlist configuration:
[**Join our Discord**](https://discord.gg/hashbot) and open a ticket.