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

# Security systems

> Protect a Hedwig server with antinuke, automod, and event logging.

Hedwig has three layers of server protection:

1. **Antinuke** monitors destructive server and member actions and provides
   user, role, and extra-owner trust lists.
2. **Automod** filters risky or unwanted messages with 13 selectable modules.
3. **Logging** records message, member, moderation, voice, and server events
   for staff review.

Read the focused guides for [Antinuke](/security/antinuke), [Automod](/security/automod), and [Logging](/security/logging) when you are ready to configure each layer.

## Recommended order

<Steps>
  <Step title="Set up logging">
    Run `/logging setup`, choose the log channels, then `/logging enable`. Logging gives staff the context needed to tune the other layers.
  </Step>

  <Step title="Configure automod">
    Run `/automod setup`, review the modules, then `/automod enable`. Use `/automod whitelist` for carefully reviewed exceptions.
  </Step>

  <Step title="Enable antinuke">
    Run `/antinuke enable`, inspect `/antinuke status`, and manage trusted exceptions with `/whitelist` and `/extraowner`.
  </Step>
</Steps>

## Antinuke commands

| Command              | Purpose                                        |
| -------------------- | ---------------------------------------------- |
| `/antinuke enable`   | Enable antinuke protection                     |
| `/antinuke disable`  | Pause protection                               |
| `/antinuke config`   | View antinuke configuration                    |
| `/antinuke status`   | View the security dashboard and active modules |
| `/antinuke reset`    | Wipe antinuke configuration                    |
| `/whitelist add`     | Allow a user or role                           |
| `/whitelist remove`  | Remove an allowlist entry                      |
| `/whitelist`         | Manage allowlist entries interactively         |
| `/extraowner add`    | Add an extra owner                             |
| `/extraowner remove` | Remove an extra owner                          |
| `/extraowner manage` | Manage extra owners interactively              |
| `/extraowner reset`  | Remove all extra owners                        |

<Warning>
  An allowlist is a trust boundary, not a convenience list. Keep it small,
  review it regularly, and never add a role just because it is easy to select.
</Warning>

## Automod commands

| Command              | Purpose                      |
| -------------------- | ---------------------------- |
| `/automod setup`     | Configure automod modules    |
| `/automod enable`    | Enable automod               |
| `/automod disable`   | Pause automod                |
| `/automod reset`     | Remove automod configuration |
| `/automod whitelist` | Manage automod exceptions    |

## Logging commands

| Command            | Purpose                      |
| ------------------ | ---------------------------- |
| `/logging setup`   | Configure log channels       |
| `/logging enable`  | Enable event logging         |
| `/logging disable` | Pause event logging          |
| `/logging reset`   | Remove logging configuration |

## Practical operating rules

* Keep logs in staff-only channels. Automatic logging creates five channels
  under a private `Hedwig Logs` category when it has the required permissions.
* Test filters with a moderator account before enabling them server-wide.
* Pair automated action with logs so staff can audit false positives.
* Pause a layer before changing it if the server is actively busy.
* If you are responding to an incident, use `/antinuke status` before changing configuration.