Protection responses

Open Protection in the dashboard to see each message protection’s behavior: Off, Monitoring, Taking action, or Needs review. Setup problems appear separately. Open a rule for its settings and five latest recorded matches; All matching incidents opens its full filtered history. Open an incident to see the result of each action. “Applied” means all actions and notifications completed; “Applying” means work is still pending. A partial result shows which steps completed and which failed. Viewing incidents requires case-viewing access.

​

Choose a mode

In the editor, Off stops new responses, Monitor records matches, and Take action uses the selected response. Turning a protection off does not undo completed Discord actions or disable manual restoration. For example, choose Take action, delete the triggering message and record a warning, then select Timeout for ten minutes. pup shows the combined outcome before you save. File, content, link, mention-spam and attachment-spam filters have an Exempt staff checkbox under Where this protection applies. It starts checked and applies when pup handles the protection. Uncheck it to apply that filter to members with pup moderation or server-management access. The server owner, bots and webhooks stay exempt, and your selected channel, role and member exclusions still apply. Choose the response for each message protection. You can delete the triggering message, record a warning, and choose at most one member action: timeout, kick, temporary ban, or ban. pup always runs those steps in that order and shows the complete outcome before you save. Durations appear only for timeout and temporary ban. Message-history deletion appears only for temporary and permanent bans. Discord role hierarchy and Discord limits still apply, and a failed step remains visible for retry without repeating steps that already succeeded. When an automatic protection deletes a message and staff notices are enabled, the staff alert includes the triggering text and attachment count. The message preview shows up to 1,800 characters; when shortened, Full text attached appears with message.txt containing the complete original text. Original images and files are not copied. Public notices and direct messages do not include this content. If deletion fails, the alert labels it Triggering message and shows the failed action. Older alerts cannot recover text that pup did not capture. Changes do not alter a response that staff already reviewed. Before applying that response, pup checks that the protection still permits it; a settings change can stop the pending action.

​

Discord AutoMod coordination

Saving a protection selects pup. To keep Discord AutoMod, choose it as the responder before saving; it supports block and timeout actions. The coordination panel shows the responder saved in pup and any detected overlap. Also check Discord’s Server Settings for rules created there. Join admission, anti-nuke, raid mode and server lockdown have their own access restrictions and recovery settings. Review the affected roles or channels before activating them. Server lockdown can reopen selected channels in stages; see Server lockdown for the preview and restoration steps.

​

Scopes and exemptions

Channel, member and role inclusions restrict where a rule applies. Member and role inclusions combine with “or”; exemptions win. A selected-channel scope with no entries matches no channels. Saved missing resources remain visible, and a missing required resource prevents the affected rule taking action. Bots and webhooks are always skipped by message protections. Use Protection scopes → Test saved protections to check a member, channel and roles. Changing an input clears the previous result. Discord AutoMod compares pup and native coverage; edit exceptions on the protection’s own page. Native AutoMod supports role and channel exemptions. It cannot represent selected channel/member inclusions or member, thread and event exclusions. Choose pup for those scopes. Missing or overlapping native responders stop automatic response. When switching to pup, it waits until the previous native rule is confirmed removed. Check the coordination result after saving.

​

Honeypot channels

Open Honeypot, select Add channel, choose a decoy channel and select Add selected channel. Review the list, mode and response, then save. Adding a channel does not switch enforcement on. Removing it also requires saving.

​

Incidents and recovery

The incident list filters by protection, mode and outcome. Its summaries omit matched message content and private pattern values. Open an incident to check each action and retry failed work. Automatic staff deletion notices can contain captured triggering text; keep their destination private. Protection → Active emergencies lists accessible containment, lockdown and raid work. Open an incident to keep its link and use the available recovery actions. Refresh after an action to see whether it completed or needs a retry.