Guide
Create alert policies
Choose actionable conditions, thresholds, destinations, and ownership for SiteWall notifications.
Last reviewed September 12, 2026
Integrations overview
SiteWall can route alert notifications through email, Slack, Microsoft Teams, and Discord when the corresponding channel is configured and available for the account. Configure the destination, define a count threshold for an issue or anomaly source, enable the policy, and verify delivery from both SiteWall and the receiving service.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Channel capabilities | Compare the observed browser access with the resource’s expected function before allowing or restricting it. |
| Prerequisites | Review prerequisites in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Delivery boundary | Confirm the enabled policy, finding type, count threshold, evaluation window, destination configuration, and destination owner. Verify policy evaluation, SiteWall delivery status, destination receipt, and human acknowledgment as separate events. |
Alert policies
An alert policy combines a finding source, count threshold, delivery channel, recipient or endpoint, and enabled state. Use Configuration to create or edit the policy and Logs to review evaluation and delivery records. A threshold alert summarizes qualifying events; it does not replace investigation of the underlying records.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Alerts in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Record the current delivery configuration
Note the enabled policy, finding type, count threshold, destination, destination owner, and latest delivery outcome. Protect recipient addresses, webhook values, and credentials in accordance with your secret-handling process.
- 3.
Finding type
Compare the signal with the affected entity, representative session, expected behavior, recent deployments, and configured detection settings. Record the reason for the disposition before tuning detection or policy.
- 4.
Count threshold
Confirm the enabled policy, finding type, count threshold, evaluation window, destination configuration, and destination owner. Verify policy evaluation, SiteWall delivery status, destination receipt, and human acknowledgment as separate events.
- 5.
Enable/disable
Review enable/disable in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context.
- 6.
History
Compare the first, last, and event timestamps with the investigation or reporting window. These values describe SiteWall observations for the active project and do not establish activity outside the captured period.
- 7.
Test evaluation and delivery
Generate a controlled qualifying issue or anomaly condition. Confirm the policy evaluation and SiteWall delivery outcome, then verify receipt and link access in the destination independently.
- 8.
Document destination ownership
Record the policy condition, approved destination, owner, test event, SiteWall delivery status, destination receipt, and credential-rotation or removal process.