Notification policies let organization administrators define notification requirements for on-call alerts and incidents. In default compliance mode, policies set minimum requirements. If strict compliance is enabled, policies define the exact saved preferences members must match.
This feature follows a compliance and reminder model. Policies flag gaps and offer a one-click fix. Depending on your organization's compliance mode, Make compliant may add missing requirements, replace saved preferences with the exact policy requirements, or switch your active preference mode to the policy's mode.
Admins can create one or more named notification policies. Your org's Notification policy mode (under Settings → Org Config) decides whether policies use Basic mode to require notification steps by priority, or Advanced mode to require event-specific notification rules. Policies can apply to everyone or only to selected teams, labels, or users.
Members can see whether their saved preferences meet the policies that apply to them. If not, a single click brings them into compliance. In default compliance mode, this adds what's missing. In strict compliance mode, it replaces saved preferences with the exact combined policy requirements.
In Basic mode, each priority covers a fixed range of alert and incident severity levels: High = levels 0-1 (SEV0, SEV1), Medium = levels 2-3 (SEV2, SEV3), Low = levels 4-5 and SIGNAL. If your organization uses the P-level severity preference, the same ranges apply to P0-P5.
Organization administrators create and manage notification policies from the Notification Policies page under Settings.

To switch between Basic and Advanced, change Notification policy mode under Settings → Org Config. Policies made in the other mode are kept but stop applying until you switch back.
Once a policy is saved, it takes effect immediately. Members will see their compliance status based on the policies that apply to them the next time they visit their notification preferences.