> ## 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.

# Panic

> Strip every dangerous permission in the server at once, find out who caused it, then put everything back.

If a staff account or bot is compromised, panic takes away the permissions being abused from every role at once. It buys you time to find out who's responsible instead of hunting through role settings while damage is still happening.

Only the **server owner** and antinuke [trusted managers](https://docs.mira.party/security/antinuke.md#who-can-configure-it) can use it. Only the owner can restore.

```javascript theme={null}
!panic
```

Also opens with `!antinuke panic` and `!killswitch`. Everything happens in one panel with three pages: **Lockdown**, **Roles** and **Activity**.

> [!WARNING]
>
> mira can only change roles below its own highest role. Move mira's role to the top of your role list while things are calm, so a lockdown can reach every role when you need it.

## Lockdown

The first page shows whether the server is locked down and how exposed it is right now:

| Line | Meaning |
| - | - |
| Dangerous Roles | Roles holding a dangerous permission, and how many mira can't reach |
| Bot Roles | Dangerous roles that belong to bots |
| Privileged Members | Members who currently hold a dangerous permission |
| Fake Permissions | Roles and members given permissions with [fake permissions](https://docs.mira.party/security/fake-permissions.md) |

### Locking down

| Button | Effect |
| - | - |
| Lock Down | Strips dangerous permissions from every role mira can reach |
| Bots Only | Strips only bot roles, for when the problem is clearly a bot and your staff should keep their access |
| Restore | Gives back exactly what the lockdown took (owner only) |

Dangerous permissions are Administrator, Manage Server, Manage Roles, Manage Channels, Ban Members, Kick Members, Manage Webhooks, Manage Expressions, Manage Nicknames and Mention Everyone. Every other permission is left alone, so members keep chatting normally.

Pressing **Lock Down** again during a lockdown adds any newly dangerous roles to the same lockdown, so nothing is lost if you run it twice or go from **Bots Only** to everything.

When a trusted manager locks the server down, the owner is messaged with what changed.

### Settings

| Setting | Default | Effect |
| - | - | - |
| Remove Fake Permissions | On | Takes away every [fake permission](https://docs.mira.party/security/fake-permissions.md) during the lockdown, and gives them back on restore |
| Pause Invites | Off | Pauses server invites during the lockdown, and resumes them on restore |

## Roles

Lists every role holding a dangerous permission, what it holds, and any role mira can't reach with the reason.

During a lockdown it shows what was stripped from each role. The owner can pick roles to restore early, for example bringing your staff back before everyone else.

Restoring only adds back the permissions the lockdown removed. Anything your staff changed on a role in the meantime stays as it is.

## Activity

Groups recent audit log activity by who did it, most destructive first: bans, kicks, deleted channels and roles, new webhooks, added bots, server changes and more. Choose a window from 15 minutes to 24 hours.

Some actions are flagged as dangerous on their own:

* Giving a role a dangerous permission
* Giving a member a dangerous role
* Allowing a dangerous permission in a channel
* Adding a bot

Pick someone to see everything they did, whether they're a trusted manager or whitelisted, and when they joined. From there you can **Strip Roles** to take away their dangerous roles, or **Ban** them.

Requires **View Audit Log**.

## Commands

| Command | Who | Does |
| - | - | - |
| `panic` | Manager | Open the panel |
| `panic roles` | Manager | Open the panel on the Roles page |
| `panic activity` | Manager | Open the panel on the Activity page |
| `antinuke panic` | Manager | Open the panel |

Aliases: `killswitch` for `panic`, `preview` for `panic roles`, `audit` for `panic activity`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.