Skip to main content

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.

​
What is Auto-Pilot?

Auto-Pilot is a premium guild setting that automatically creates name and PFP filters for every allowlisted and manager member. When a protected member changes their username, nickname, or profile picture, Hashbot automatically updates the filters — so impersonators are always caught, even if the real user changes their identity.
No commands needed. Just enable the setting and manage your allowlist — Hashbot handles the rest.

​
How It Works

  1. Enable “Auto-Pilot” in the Dashboard Settings (requires a Hashbot subscription)
  2. Hashbot scans every allowlisted and manager role member
  3. For each member, it creates:
    • Name filters for their username, nickname, and global display name
    • PFP filters for their profile picture (global and server-specific)
  4. When a protected member changes their name or avatar, Hashbot:
    • Retires the old filter (soft-deleted)
    • Creates a new filter for the updated identity
  5. If a non-allowlisted user joins with a matching name or PFP, they get banned automatically
Auto-Pilot protects all allowlisted roles and manager roles by default. Manager roles are treated as a “super allowlist” — they get all the same identity protections automatically.

​
Enabling Auto-Pilot

1

Open the Dashboard

Go to dashboard.hashbot.com and select your server.
2

Navigate to Settings

Click Settings in the Hashbot sidebar.
3

Enable Auto-Pilot

Toggle on Auto-Pilot. This requires an active Hashbot subscription.
4

Manage your Allowlist

Add the roles or users you want to protect via /allowlist add or the Allowlist page on the Dashboard. Manager roles are included automatically.

​
Choosing Which Roles to Protect

By default, Auto-Pilot protects all allowlisted and manager roles. If you want to limit protection to specific roles, you can customize this in the Dashboard:
  • When Auto-Pilot is enabled, a role picker appears below the toggle
  • All allowlisted and manager roles are shown as active by default
  • Click a role to remove it from protection (the color dot turns into an X on hover)
  • Use the ”+ Add role” dropdown to re-add roles
  • Click “Reset to default” to go back to protecting all roles
The role picker only shows roles that are already configured as allowlisted or manager roles. To add a new role to the picker, first add it to your allowlist or manager list.

​
Use Cases

  • Protect staff and moderators — prevent scammers from copying mod identities
  • Protect VIPs — keep high-profile community members safe from impersonation
  • Hands-off operation — no manual filter management, everything updates automatically
  • Selective protection — only protect specific roles instead of the full allowlist

​
Smart False-Positive Prevention

Hashbot uses exact-match name filters (case-insensitive) and runs strict safety checks before creating any filter:
  • Name too short (< 4 chars): skipped with a warning — names like “Joe” or “Max” are too generic
  • 1 other member matches: skipped with a “Common Name Warning” — another member already has this exact name
  • 2+ other members match: skipped — too many duplicates, not safe for auto-protection
  • Default Discord avatar: no PFP filter created — only custom avatars are protected
If a name is skipped, Hashbot logs the reason in your log channel. You can always add it manually with /name-filters add if you still want it. Fuzzy Matching (separate premium toggle) catches name variations like leetspeak and typos — the two features complement each other.
Names like “CryptoModerator” or “OfficialStaffBot” will be auto-protected. Common names like “Joe” or “Admin” will be skipped with a clear explanation in your log channel.

​
Best Practices

  • Only allowlist roles with uniquely named, trusted members (e.g., Staff, Moderators)
  • Avoid allowlisting large public roles
  • Enable Fuzzy Matching alongside Auto-Pilot for maximum coverage
  • Check your log channel for “Filter Skipped” warnings — these tell you which names were too common
  • Review your filters periodically on the Dashboard — all auto-created filters are tagged “Auto-Pilot”
  • Use the role picker to limit protection to specific roles if your allowlist is large

​
Migration from /filter-sync

If you were previously using the /filter-sync commands, your server has been automatically migrated. The Auto-Pilot setting is already enabled, and all your existing filters remain active. No action needed. The /filter-sync commands have been removed. Auto-Pilot is now managed entirely through the allowlist and the Dashboard toggle.

​
Need Help?

If you need support with Auto-Pilot: Join our Discord and open a ticket. Our team is happy to assist you.