> For the complete documentation index, see [llms.txt](https://securitybot.gitbook.io/securitybot-knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/chat-filters/strict-mode.md).

# Strict Mode

{% hint style="info" %}
**Available on all tiers** for free. [Compare plans →](/securitybot-knowledge-hub/plans-and-pricing/plans-and-pricing.md)
{% endhint %}

By default, SecurityBot skips chat filtering for your trusted people: admins and anyone with an exempt role. Strict Mode turns that exception off. When it is enabled, your chat filters apply to everyone, including admins and exempt roles.

This is useful for breach containment. If an admin account is compromised or the device of someone with an exempt role is hijacked, Strict Mode makes sure scam links and wallet addresses posted from those accounts are still caught and removed.

Strict Mode is **off by default**.

***

## How It Works

Strict Mode changes **who** is checked. It does not change where filtering happens or what counts as a violation.

When Strict Mode is enabled:

* **Chat filters apply to everyone.** Links, wallet addresses, ADA Handles, and Discord invites are filtered for admins and exempt-role holders exactly as they are for any other member.
* **Only chat filters are affected.** Name, avatar, account-age, and scammer filters are unchanged. Strict Mode has no effect on them.
* **Ignored channels and categories are still ignored.** Anywhere you have told SecurityBot to skip filtering stays skipped. See [Bypass Settings](/securitybot-knowledge-hub/bot-guide/chat-filters/bypass-settings.md).
* **Allowlisted entries are still allowed.** Approved domains, addresses, handles, and invites are still permitted for everyone. Strict Mode does not turn your allowlists into violations.
* **The bot's own messages are unaffected.**

In short: Strict Mode removes the admin and exempt-role bypass for chat filters, and nothing else.

{% hint style="info" %}
The moderator role does not exempt anyone from chat filters, with or without Strict Mode. Mods are only exempt from name and avatar filters. Chat-filter exemptions come from the Admin role, Discord's Administrator permission, exempt roles, and ignored channels or categories.
{% endhint %}

***

## How to Enable Strict Mode

You can toggle Strict Mode in three ways.

### Slash command

```
/chat_filters strict toggle
```

Run it once to enable Strict Mode, and again to disable it.

To check whether Strict Mode is currently on or off:

```
/chat_filters strict about
```

### Filter embed button

Open your chat filter settings and use the **Strict Mode** toggle button in the embed.

### Dashboard

Open your server on the [SecurityBot dashboard](https://securitybot.org/), go to **Chat Filters**, and switch **Strict Mode** on or off. Dashboard and Discord share the same setting, so changing it in one place updates the other.

***

## Best Practices

* Tell your team before you enable it, so staff know their messages are now filtered
* Keep an allowlist of the domains and addresses your staff legitimately share, so normal posts are not caught
* Use [Bypass Settings](/securitybot-knowledge-hub/bot-guide/chat-filters/bypass-settings.md) to keep private staff channels unfiltered even with Strict Mode on
* Remember that role-based exemptions no longer apply to chat filters while Strict Mode is on. See [`/roles`](/securitybot-knowledge-hub/command-reference/roles.md) for how exempt roles normally work

{% hint style="info" %}
Only users with the Admin role or Discord's Administrator permission can toggle Strict Mode.
{% endhint %}

***

Next up: Explore additional [scam prevention tools](/securitybot-knowledge-hub/bot-guide/scam-prevention-features.md) designed to protect your community from compromised accounts, scam links, and more.