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

# Join Gate, raids and Anti-Nuke

> Configure defensive controls and understand Lockdown behavior.

## Join Gate and unverified timers

Join Gate checks a new member's Discord account age. Its default approach records and alerts; an owner-configured action can instead kick or ban ineligible accounts. Review the selected action before enabling the module.

The separate unverified-member timer can kick members who do not verify within the configured number of minutes. Set its delay to zero to disable it.

## Raid Watch

Raid Watch detects a configured number of joins within a time window, records security signals and alerts the security log channel. It does not automatically start Lockdown. An authorized human reviews the alert and chooses a response.

## Lockdown

Configure its channel scope and optional new-joiner kicking in the dashboard. Selected scope supports up to **25 channels**. Saving changes prepares the next activation; it does not start, stop or rewrite the active Lockdown snapshot.

The actual server owner uses:

```text theme={null}
/lockdown start reason:<reason>
/lockdown stop
```

Lockdown updates the selected channels' send-message and thread-send overwrites. The bot records originals before changing them and uses the snapshot to restore them. Inspect reported failures when some channels could not be restored.

## Anti-Nuke

Enable the module and select watched actions, thresholds, time windows and an assignable quarantine role, or allow the bot to create one.

Watched events include channel creation/deletion, role deletion/update, bans, member pruning, webhook creation, bot additions and server updates. Detection uses audit-log attribution and can quarantine the actor for human review. Incident cards support review and escalation.

Discord hierarchy still applies. The bot cannot reliably impose restrictions on the actual owner or members above its own role; review the recorded outcome. The Anti-Nuke whitelist remains actual-owner-only.

## Check effectiveness

Use a test server to validate access overwrites and bot hierarchy. A module toggle shows configuration, not proof that every future Discord action will succeed. Keep a working security log channel so failures and review cards are visible.


## Related topics

- [AEGIS Security Bot](https://docs.aegissentinellab.com/en/introduction.md)
- [Staff ranks and Discord roles](https://docs.aegissentinellab.com/en/staff-hierarchy.md)
- [Set up your server](https://docs.aegissentinellab.com/en/quickstart.md)
- [Discord command reference](https://docs.aegissentinellab.com/en/commands.md)
- [Blacklists, requests and appeals](https://docs.aegissentinellab.com/en/blacklists-appeals.md)


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