Server Protection

Use Server Protection to help staff prevent abuse, review incidents, and handle member reports and appeals.

Set up the essentials

1. In Server Protection, choose the moderator roles that Guardy should recognise.
2. Choose private destinations for moderation logs, reports, and message logs.
3. Turn on the protections your server needs: Join Gate, Anti-Nuke, Link filter, Strike ladder, or Traps.
4. Decide how members can report a person or message, and whether appeals are available.
5. Test with a non-owner moderator and a test member.

Staff can use /warn, /timeout, /kick, /ban, /purge, /slowmode, and case commands. Use clear reasons, because they help a later review. Guardy still follows Discord permissions and role hierarchy.

Protect new members and the server

Join Gate can hold risky arrivals until they verify. Set up its holding role, verification channel, and channel protection before depending on it. Anti-Nuke, Link filter, and Traps should be tested in a safe environment before a live incident.

Reports, appeals, and cases

When reports are on, members can use /report or Discord's Apps menu to report a person or message to your moderators. Explain when to use this workflow and when to use Discord's own report tools.

Review reports, appeals, and cases in the dashboard. Restrict their destinations to the staff who need them.

During an incident

/panic on can pause invites and, when Join Gate is configured, hold new members. An optional slow mode can be applied across channels. Use it only during an active incident and review the result immediately.

/panic off releases the panic state, but any slow modes it set remain until staff clear them. Keep a trusted human administrator able to review and reverse settings.