Alerts, grouping and digests
Instant for what cannot wait, grouped and cooled down so one bad deploy is one message; a digest for the rest.
A security tool that sends forty messages for one push gets muted, and a muted tool protects nobody. Alerting here is deliberately conservative.
- Instant
- Sent for what genuinely cannot wait - a critical finding, a security regression on the default branch.
- Grouping
- Findings from one scan or change set arrive as one message, not one per finding.
- Cooldown
- After a message about a site, there is a quiet window before the next one, so a bad afternoon is not forty notifications.
- Digest
- Everything that can wait, summarized on a schedule.
Channels
- Email, to the people in the organization according to their preferences.
- Slack, through one incoming webhook per organization.
- The app itself, where background work is visible while it happens.
Questions
Can I get alerts for one site only?
Yes. Preferences let each person narrow what reaches them, including by site.
Will I be alerted about findings I dismissed?
No. Dismissed findings leave the alerting path entirely.
Does the free plan send alerts?
Free delivers the report for a scan you asked for. Continuous alerting comes with a paid plan, because there is no continuous monitoring to alert about otherwise.
Something here wrong, missing or out of date? Tell us and we will fix the page.