In pictures
Before you begin
Use anti-raid.manage and permissions for the selected responses. Audit protection requires available data and permissions to identify actions.
Step by step
In Security → Anti-raid, create and name a rule, then choose management modules: channels, roles, webhooks, bot additions, kicks and bans.
Set a threshold and window for each module, then choose affected groups and exceptions with the role, member and channel selectors.
In Actions, choose a punishment, privileged role removal and restoration. You can pause invites and lock all channels or a selection for a specified duration.
Save and enable the rule. Temporary changes are restored at expiry while preserving later administrator changes. Review incidents to check each outcome.
Monitored sensitive actions
- Channel creation, editing, deletion and permissions; role creation, editing, deletion and assignment.
- Webhooks, bot additions and mass bans or kicks according to enabled protections.
- Mass mentions and unauthorised links, with their thresholds and exceptions.
One incident per burst
Actions by the same member for the same protection within its detection window are grouped into one incident. The punishment is applied once and the existing notification is updated. Countermeasures continue processing actions already sent even after the member is kicked or banned. Reactions are processed per actor: repairs, logging and direct messages run separately so they do not delay subsequent punishments.
Bot responsible for an incident
When the actor is a bot, Spider sets its dedicated role permissions to zero and removes other dangerous roles it can manage before the selected punishment. Shared roles keep their permissions. Spider needs Manage Roles and a sufficient position in the hierarchy; refusals are reported in the incident. The server owner, Spider itself and exempt members remain excluded from countermeasures.
What can be restored
Recreating a channel does not restore its messages. A recreated role cannot fully recover previous assignments; a recreated webhook has a new URL. A kicked member cannot be automatically rejoined. Permission restoration preserves newer changes when they are detected.
Categories and incomplete repairs
Spider recreates categories first, then reconnects affected channels to their original category with their saved permissions. A channel moved to another category during the intervention stays in its new location. Pending or failed repairs remain in the incident and are retried for a limited period without repeating the punishment. Check the bot’s permissions and reported results when manual intervention is needed.
Preconfigured intervention
The /raid start and /raid stop commands use the ID of a rule prepared in the dashboard. Check its scope and duration before triggering it. For a server-wide lock with preview, see Emergency mode.