Skip to main content
This guide covers the minimum steps needed to get Hashbot actively protecting your Discord server. Complete these steps in order for basic protection.

Prerequisites

Before starting, ensure you have:
  • Manage Server permission on your Discord server
  • Invited Hashbot to your server
  • Basic understanding of Discord roles and permissions

Step 1: Configure Hashbot Role

Hashbot needs proper permissions to moderate your server effectively.
  1. Go to Server SettingsRoles
  2. Find the Hashbot role
  3. Move it above the roles of users you want it to moderate
  4. Verify it has these permissions:
    • Ban Members
    • Kick Members
    • Manage Messages
    • View Channels
    • Send Messages
If Hashbot’s role is below other roles, it cannot moderate users with those roles.

Step 2: Set Up Log Channel

Create a private channel where Hashbot will report its actions.
  1. Create a new private channel (e.g., #hashbot-logs)
  2. Run: /settings logging set channel:#hashbot-logs
  3. Verify Hashbot can access the channel
Without a log channel, reports go to the server owner’s DMs, which can be overwhelming.

Step 3: Add Manager Role

Designate who can configure Hashbot settings.
  1. Choose a trusted admin role (e.g., @Admins)
  2. Run: /manager add role:@Admins
  3. Verify with: /manager list

Step 4: Configure Allowlist

Protect your team from accidental moderation.
  1. Add your admin roles: /allowlist add role:@Admins
  2. Add your moderator roles: /allowlist add role:@Moderators
  3. Add any trusted bots: /allowlist add user:@TrustedBot
Allowlisted users and roles are exempt from all Hashbot actions.

Step 5: Add Your First Filter

Start with basic protection against impersonation.
  1. Add your project name: /name-filters add phrase YourProjectName
  2. Add common scam terms: /name-filters add phrase airdrop
  3. Test a filter: /name-filters test scammer_airdrop

Step 6: Enable Fuzzy Mode (Subscription Required)

For enhanced detection of Unicode and symbol variants.
  1. Run: /settings fuzzy set-state fuzzy-state:enable
  2. Verify: /settings fuzzy report
Fuzzy Mode requires an active subscription. Activate your subscription if you haven’t already.

Step 7: Run Initial Cleanse

Scan existing server members for matches.
  1. Run: /cleanse to see what would be detected
  2. Review the results carefully
  3. If satisfied, run: /cleanse force to take action
Cleanse only affects existing members. New members are automatically scanned upon joining.

Verify Your Setup

Check that everything is working correctly:
  1. Settings Status: /settings status - Review all configurations
  2. Test Protection: Create a test account with a filtered name and try to join
  3. Check Logs: Verify actions appear in your log channel

What’s Next?

Now that you have basic protection, consider these enhancements:

Need Help?

If you encounter issues during setup: Your server now has basic Hashbot protection active! 🛡️