# Grafana Alerting: Scale alert routing without scaling complexity using multiple notification policies

DevFeed: [Grafana Alerting: Scale alert routing without scaling complexity using multiple notification policies](<https://devfeed.tech/articles/grafana-alerting-scale-alert-routing-without-scaling-complexity-using-multiple-notification-policies-57758.md>)

Original publisher: [Read original article](<https://grafana.com/blog/grafana-alerting-scale-alert-routing-without-scaling-complexity-using-multiple-notification-policies/>)

Author: Matt Jacobson

Published: 2026-09-22T08:36:57.034266Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [API](<https://devfeed.tech/topics/api.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>)

Tags: [alerting](<https://devfeed.tech/tags/alerting.md>), [alertmanager](<https://devfeed.tech/tags/alertmanager.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [complex](<https://devfeed.tech/tags/complex.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [policy](<https://devfeed.tech/tags/policy.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [split](<https://devfeed.tech/tags/split.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [traces](<https://devfeed.tech/tags/traces.md>)

## AI overview

Grafana Alerting introduces generally available multiple notification policies in Grafana 13.2. Named policy trees let teams organize alert routing by ownership boundary, assign rules to specific policies, manage policies independently, control access with policy-level role-based access control, and update one policy without affecting others.

## Source excerpt

Alert routing often starts simple. A team creates a few contact points, adds some label matchers, and builds a notification policy tree that sends each alert to the right destination. But alerting configurations rarely stay simple. As an organization grows, its notification policy tree must accommodate more teams, services, and routing requirements. Changes for one team still require editing a global configuration, making ownership less clear and independent provisioning harder. Over time, even small updates can require navigating an increasingly complex routing tree. With Grafana 13.2, multiple notification policies are now generally available in Grafana-managed alerting. You can create named notification policy trees, assign alert rules to a specific policy, and manage each policy independently. Existing alert rules continue to use the default notification policy unless you assign them to a named policy, so you can adopt the feature incrementally without migrating every rule at once. What multiple notification policies enable Multiple notification policies provide clearer boundaries for organizing, managing, and securing alert routing. With them, you can: Split routing logic into smaller, named trees organized around a team, service, domain, or other ownership boundary Assign alert rules directly to the policy that should handle their alerts Provision and manage each policy independently through the Grafana UI, API, or Terraform Control access using policy-level role-based access control Update one policy without affecting the routing configuration or notification state of alerts assigned to another policy The limits of one global notification policy tree Grafana Alerting's notification routing model builds on Prometheus Alertmanager, where routing is represented as a single global notification policy tree with a top-level route and nested child routes. Within that tree, alert labels are matched against routes that determine how alerts are grouped, when notificati