> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rbxweb.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Auto mute

> Automatically mute users who ping @everyone or @here. Optionally time out repeat offenders.

Auto mute detects when a user pings `@everyone` or `@here` — a common spam-bot signal — and applies your server's mute role to them. An embed is posted to a chosen channel explaining the action. Separately, a follow-up timeout can kick in if the same user keeps spamming after the mute.

Open **Dashboard → Auto Mute**. The view has two cards: **Auto Mute Settings** on the left and **Timeout on Spam** on the right.

<Warning>
  Auto mute fires on any `@everyone` or `@here` mention, including legitimate ones. If your server allows members to use these mentions normally, keep this feature disabled.
</Warning>

<Note>
  **How this message is delivered.** It posts through a bot-owned webhook. With no custom
  identity set it uses the bot's own name and avatar, so it looks exactly like a normal bot
  message. Enabling **Custom identity** simply overrides that name and avatar (the custom name is capped at
  **80 characters** — Discord's webhook limit). This works in
  both Message and Embed mode. The bot needs **Manage Webhooks** in the target channel; without
  it the message is posted normally instead, so nothing is ever lost.
</Note>

## Auto mute settings

### Behavior

When enabled, the bot scans every message. If a message contains `@everyone` or `@here` pings that Discord would actually deliver, the bot:

1. Applies the configured mute role to the author.
2. Posts the configured embed to the selected channel.

This works even when server permissions block normal users from using `@everyone` — the bot reacts to any attempt.

### Settings

<ResponseField name="Enable" type="toggle">
  Master switch for auto mute.
</ResponseField>

<ResponseField name="Message template" type="embed or text">
  The message posted when a user is auto-muted. Same template editor as elsewhere, with support for [placeholders](/placeholders).
</ResponseField>

<ResponseField name="Channel" type="channel picker">
  Where the mute notification embed is posted.
</ResponseField>

<ResponseField name="Mute role" type="role picker">
  The role applied to the muted user. This must be a role that removes send-message permissions server-wide.
</ResponseField>

## Timeout on spam

A follow-up layer for repeat offenders. After a user is auto-muted, if they continue pinging `@everyone` / `@here`, the bot applies a Discord timeout (server-wide) in addition to the mute role.

### Settings

<ResponseField name="Enable Timeout on Spam" type="toggle">
  Master switch for the timeout follow-up.
</ResponseField>

<ResponseField name="Timeout Duration" type="select">
  How long the Discord timeout lasts. Options: 1 minute, 5 minutes, 10 minutes, 30 minutes, 1 hour, 6 hours, 1 day, 3 days, 1 week.
</ResponseField>

<ResponseField name="Timeout Message" type="WYSIWYG editor">
  The message posted when a timeout is applied, composed in the full message/embed editor (Variables, Markdown, Emoji, Timestamp, Preview, Restore default, Clear). Placeholders: `{user}`, `{user_name}`, `{duration}`, `{server}`. Defaults to an embed titled **Timed Out**.

  Turn on **Custom identity** to post the timeout message under a custom name and avatar (sent via a webhook). This is **not** tier-gated — but the bot needs the **Manage Webhooks** permission in the channel; without it, it falls back to posting as the bot.
</ResponseField>

## Setup checklist

1. Create a **Muted** role in **Server Settings → Roles** with send-message permissions denied in every channel.
2. Move the bot's own role **above** the Muted role so it can assign it.
3. Open **Dashboard → Auto Mute**, pick the Muted role, the notification channel, and customize the message.
4. Save.