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

# Add & Remove Filters

> Manage your name-based blocklist by adding or removing keywords and patterns.

### Adding Filters

Use `/name-filters add` to block usernames or nicknames that match specific words or patterns. Choose between **phrase** filters (simple text matching) or **regex** filters (pattern matching).

<Info>
  **Phrase filters** are easier and safer to use — they match any name containing the exact text (case-insensitive).\
  **Regex filters** are more powerful but require testing to avoid false positives.
</Info>

#### Examples

| Command                               | What It Does                                                        |
| ------------------------------------- | ------------------------------------------------------------------- |
| `/name-filters add phrase scam`       | Blocks names containing "scam" (e.g., `scammer123`, `NFT-Scam-Bot`) |
| `/name-filters add regex (?i)sc[ae]m` | Blocks pattern variations like `scam`, `scem`, `SCAM`               |

### Removing Filters

Use `/name-filters remove` with the filter ID to delete a filter from your blocklist.

| Command                            | What It Does                             |
| ---------------------------------- | ---------------------------------------- |
| `/name-filters remove <filter_id>` | Removes the filter with the specified ID |

<Tip>
  Find filter IDs on the [Hashbot Dashboard](https://dashboard.hashbot.com) Text Filters page, or use `/name-filters list` for a quick count and dashboard link.
</Tip>

### Bulk Management

For bulk filter management, the [Dashboard](https://dashboard.hashbot.com) is the fastest option:

* **Search** your filter list by keyword
* **Import** filters from a JSON file (Premium)
* **Export** your entire filter list (Premium)
* **Filter Optimizer** — identifies redundant or overlapping filters

### Tips

* Use **phrase filters** for clear, specific keywords
* Test **regex filters** on [regex101.com](https://regex101.com/) (Golang flavor) before adding
* Run `/name-filters test <name>` to verify a filter catches what you expect
* Run `/cleanse` after adding new filters to catch existing members