> For the complete documentation index, see [llms.txt](https://docs.onlymonster.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlymonster.ai/team-and-security-management/message-guard-automation.md).

# Message Guard Automation

Message Guard Automation automatically blocks team members who repeatedly trigger Message Guard violations. When a team member reaches the violation limit, they lose access to all accounts until the block is removed.

Message Guard Automation works on all platforms together: **OnlyFans**, **Fansly**, and **Telegram**.

<figure><img src="https://3576754298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ3tUjWV0i06zjZEIvwPN%2Fuploads%2FbdhzywfUn7r7aFTmx9Ty%2F%D1%86%D1%83%D0%BA%D0%BF%D1%86%D1%83%D0%BA%D1%86%D0%BA%D1%83.png?alt=media&amp;token=51412ef8-3bf2-4aae-ae41-2bd3c99d94e4" alt=""><figcaption></figcaption></figure>

## **How It Works**

Message Guard Automation counts each team member's violations over a time period that you define. When the limit is reached:

1. The team member loses access to all accounts
2. The block appears in the **Active blocks** list on the **Automation** tab
3. The block stays in place until a user with the **Edit Restricted Words** permission removes it

{% hint style="info" %}
**Note:** Blocking applies only to team members who don't have the **Edit Member** permission. A team member with the **Edit Member** permission is never blocked.&#x20;
{% endhint %}

To turn on automation, open the **Automation** tab in Message Guard, switch on **Block Member on repeat violations**, configure the rules, and click **Save Changes**.

## **Rules**

Set the blocking conditions in the **Rules** section:

* **Block Member after** - The number of violations that triggers a block. Select a value from 2 to 20.
* **violations within** - The time period in which violations are counted. Select a value from 5 minutes to 24 hours.

Example: with **Block Member after** set to 5 and **violations within** set to 10 minutes, a team member is blocked after 5 violations within 10 minutes.

**Where violations add up**

* **All accounts** - Violations on different accounts add up.
* **Per account** - Violations on each account are counted separately.

### **What counts as a violation**

The following categories can count toward blocking: **Red Words**, **Yellow Words**, **Custom Words**, **Bypass Protection**, **Context Detection**, **Links**, **Emails**, **Phone Numbers**, and **Crypto Wallets**. You can disable individual categories in the dropdown list.

{% hint style="warning" %}
**Important!** Weigh the risks before disabling a category. Violations in a disabled category don't count toward blocking, so a team member can keep triggering them without being blocked.&#x20;
{% endhint %}

### **Exceptions**

Use the **Exceptions** section to exclude team members from automatic blocking:

* **Never block these roles** - Team members with the selected roles are never blocked.
* **Never block these Members** - The selected team members are never blocked. Members are selected by member ID.

## **Active Blocks**

The **Active blocks** section lists all team members who are currently blocked:

* **Member** - The blocked team member
* **Account** - The account where the block was triggered
* **Reason** - The violation category that triggered the block
* **Blocked at** - The date and time when the block was applied

To remove a block, click **Unblock** next to the team member. Access is restored after 2 minutes. We recommend that the team member restart OnlyMonster Browser or refresh ChatSpace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onlymonster.ai/team-and-security-management/message-guard-automation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
