Lockdown

A one-click "freeze chat" for incident response. Removes the ability to send messages from a role (default: @everyone) across all channels (or a subset). Useful when something's happening and you need everyone to stop typing right now.

Settings

Setting	What it does
Enabled	Master switch (must be on to engage lockdowns).
Locked status	Read-only — true when the server is currently locked down.
Message	The embed posted to affected channels when lockdown engages.
Role ID	The role to deny send-messages permission for. null = @everyone.
Auto-on-raid	Engage lockdown automatically when Anti-Raid triggers.
Channel IDs	Specific channels to lock down. Empty = all text channels.
Category IDs	Lock entire categories.
Auto-lift (minutes)	Auto-unlock after N minutes. 0 = manual only.
Exempt channels	Channels that stay writable even during lockdown — mod coordination rooms typically.
Hide channels	When true, ALSO deny ViewChannel during lockdown (server "goes dark" — closer to a real incident response than the standard "you can read but not post" freeze).

Engaging lockdown

Dashboard → click Engage lockdown. Confirm modal. Phantom:

1. Snapshots the current send_messages permission for the configured role on every affected channel.
2. Denies send_messages for that role.
3. Posts the lockdown embed to each affected channel.
4. (Optional, if hide_channels) denies view_channel too.
5. Schedules an auto-lift if configured.

Lifting lockdown

Click Lift lockdown. The role's send_messages permission is restored to the snapshotted state (so channels that had explicit allows / denies keep their custom overrides).

Tips

• Always set an auto-lift duration, even a long one (e.g. 4 hours). A lockdown that nobody remembers to lift kills your server's chat for days.
• Exempt your mod-coord channel. During an actual incident your mods need to talk to each other.
• hide_channels = true is a stronger signal. Use it for actual emergencies, not as a daily quiet-hours feature.
• Lockdowns survive a Phantom restart — the auto-lift timer keeps running through any blip.

Permissions

• security.view — see lockdown status
• security.edit — engage / lift

Behaviour

• The original per-channel permissions are snapshotted on engage, so lifting restores them precisely.
• Auto-lift fires within a minute of the deadline.
• Re-engaging an already-locked server re-targets without losing the original snapshot.

Related pages

• Anti-Raid — auto_lockdown triggers Lockdown when a raid is detected
• Audit Log — engage / lift events log here