Create an alert policy
Summary
Alert policies define the conditions that generate an alert, a DLP violation, risky agent behavior, blocked-platform usage, unusual timing or volume, and more, and how each is scoped and optionally auto-escalated. This step completes when you create one.
Before you start
The Policies page requires Professional or above. On a lower plan the step shows locked on your checklist, with the caption Not in your plan.
Within Policies, alert policies are on the Alerts and playbooks tab. Creating one needs the Manage Alert Policies permission.
1. Choose a policy type
- Go to Act → Policies and open the Alerts and playbooks tab.
- Select + Create alert policy and choose from the built-in types on offer: each comes with its own relevant settings (for example, a minimum DLP severity, or a volume-spike sensitivity multiplier).
2. Configure it
- Name the policy and set its severity.
- Set its deduplication window and lookback period, so repeat triggers don't flood your queue.
- Once it's created, optionally edit it to scope it (for example, to a specific department) and to decide whether it should auto-promote to an incident when it fires.
3. Save
The policy joins your list, grouped under its category (Sensitive data signals, AI tool signals, Agent and behavior signals, Unusual activity, or Coverage signals).
Confirm it worked
The new policy appears in its category with the severity, dedup window, and lookback you configured. Its 30-day fire count starts at zero and links directly into the alert inbox once it begins firing.
If it didn't work
- Can't find alert policies: they're on the Policies page's Alerts and playbooks tab, at the right end of the tab row.
- Can't create a policy: you need the Manage Alert Policies permission; ask an administrator.
- Told the alert type's thresholds are set on another policy: some alert types allow only one policy for the whole organization, because their thresholds apply organization-wide. The message names the existing policy; edit that one instead.
- Policy fires too often, or not at all: revisit the deduplication window and lookback period; these are what control how noisy or quiet a policy is, more often than the trigger condition itself.
- Notifications aren't reaching anyone: confirm the notification destination itself is configured and enabled; see Turn on notifications and An expected notification didn't arrive.