# Bot Purges

{% hint style="info" %}
**Premium Feature** — Bot purging requires a Premium subscription. [Compare plans →](/securitybot-knowledge-hub/plans-and-pricing/plans-and-pricing.md)
{% endhint %}

Bot Purges help protect your server by automatically removing unverified users. These accounts are often the first step in bot raids, mass DM scams, or token spam. Purges run on a scheduled cycle and target users who have not been assigned any roles, helping you maintain a safer server and a more accurate member list.

***

### How It Works

* **Auto-Removal**: Kicks members with no roles every 30 minutes to eliminate unverified bots.
* **Grace Period**: Members who joined within the last 5 minutes are excluded to give time for verification.
* **Bans Known Scammers**: Members listed in the SecurityBot scammer list are banned during the same scheduled run.

***

### Enable Automatic Purges

To turn on autopurge:

```
/purge enable
```

SecurityBot will show a confirmation prompt. Click **Confirm** to turn autopurge on, or **Cancel** to leave it off. Once enabled, autopurge will immediately begin checking for unverified members and known scammers every 30 minutes.

To turn it off again:

```
/purge disable
```

To check the current state at any time:

```
/purge view
```

`/purge view` is available on all tiers; free-tier servers see an upgrade prompt explaining how to get autopurge.

You can also control whether purge notifications are posted to your log channel via `/settings chat_alerts`.

{% hint style="warning" %}
**Before enabling:** Make sure the majority of your active members already have roles. If not, set up a verification system and encourage users to verify first.
{% endhint %}

***

### Run a Manual Purge

You can also run purges on-demand at any time, whether or not autopurge is enabled:

```
/purge run
```

***

### Before You Purge

* **Check for unverified members**: Make sure you don’t have legitimate users without roles.
* **Use verification**: Set up a role-based system to ensure legitimate users are verified before enabling purges.
* **Communicate with mods**: Notify your team before enabling to avoid confusion.

***

### Best Practices

* **Enable purges after your verification flow is live**
* **Manually run a purge** after a raid or bot wave
* **Monitor purges** using the log channel

***

Next up: Strengthen protection with the [Scammer Filter & Flagging](/securitybot-knowledge-hub/bot-guide/scam-prevention-features/scammer-filter.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/scam-prevention-features/bot-purges.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.