> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mira.party/llms.txt
> Use this file to discover all available pages before exploring further.
# Moderation overview
> What's in the moderation toolkit and how the pieces fit together.
Around 230 commands, but they break down into six areas that don't overlap much.
Ban, kick, mute, jail, timeout — and every temporary variant.
Warn members and escalate automatically at set counts.
Every action is logged with an editable reason and a case number.
Delete messages by author, content, type or position — 30+ filters.
Lockdowns, slowmode, hiding, nuking, threads.
Mass assignment, temp roles, role links, restoring on rejoin.
## Before you start
Two things need setting up once, or half the commands won't work.
Discord will not let a bot moderate anyone whose highest role sits above the bot's own. Drag mira near the top of the role list — above your staff roles, below nothing that matters.
```javascript theme={null}
!setup
```
Explains what `mute`, `jail`, `imute` and `rmute` need, and creates the missing roles and channel overwrites. Requires **Manage Roles** and **Manage Channels**.
If you add channels later, re-sync them:
```javascript theme={null}
!mute sync
!jail sync
```
## Things that apply everywhere
You can't punish someone whose highest role is at or above your own, and neither can mira. This holds even with [fake permissions](/security/fake-permissions) — it's checked against the person running the command, not just the bot.
The server owner can never be punished by anyone.
Every punishment command takes a trailing reason. If you don't give one, a default is recorded. Reasons are stored on the [case](/moderation/cases) and can be edited afterwards, so a rushed ban can be documented properly later.
```javascript theme={null}
!ban @someone raiding
!case reason 47 raiding — coordinated with 3 alts
```
Frequently-used reasons can be saved as templates:
```javascript theme={null}
!reason create raid coordinated raid participation
!ban @someone raid
```
Adding `-s` or `--silent` to a reason suppresses the DM that would otherwise be sent to the punished member.
```javascript theme={null}
!ban @someone raiding -s
```
What mira replies with after a moderation command is fully customisable per command, including the DM the member receives:
```javascript theme={null}
!invoke ban {content: {user.name} is gone. case #{case}}
!invoke dm ban {title: You were banned from {guild.name}} {description: {reason}}
```
`!invoke variables` lists what you can use. Full details on the [Cases](/moderation/cases#custom-responses) page.
Several commands accept more than one member at a time — `massban`, `voicekick`, `role multiple`. Where they do, separate targets with spaces:
```javascript theme={null}
!massban 111111 222222 333333 --history 1d
```
## Quick reference
The commands people reach for most often:
| Command | Aliases | What it does |
| ---------------------------------- | ------------------ | -------------------------------------------- |
| `ban [history] [reason]` | `boot` | Ban, deleting up to 7 days of messages |
| `tempban