# Nested Notification Policy Contact Point **URL:** \ **Category:** Alerting\ **Created:** [October 13, 2022, 5:00pm UTC](https://community.grafana.com/t/nested-notification-policy-contact-point/74137 "2022-10-13T17:00:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![milinpatel13298](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/milinpatel13298/32/26506_2.png) [@milinpatel13298](https://community.grafana.com/u/milinpatel13298)\ **Post date:** [October 13, 2022, 5:00pm UTC](https://community.grafana.com/t/nested-notification-policy-contact-point/74137/1 "2022-10-13T17:00:24Z")
The [Grafana documentation to add notification policy](https://grafana.com/docs/grafana/latest/alerting/notifications/#add-new-specific-policy) outlines the following step to add a nested notification policy. > Optionally, enable **Continue matching subsequent sibling nodes** to continue matching nested policies even after the alert matched the parent policy. When this option is enabled, you can get more than one notification. Use it to send notification to a catch-all contact point as well as to one of more specific contact points handled by nested policies. Does the “catch-all” contact point mean the root policy contact point or the contact point defined in the parent notification policy (under which the nested policy is being defined)? ---
**Author:** ![milinpatel13298](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/milinpatel13298/32/26506_2.png) [@milinpatel13298](https://community.grafana.com/u/milinpatel13298)\ **Post date:** [October 21, 2022, 7:53pm UTC](https://community.grafana.com/t/nested-notification-policy-contact-point/74137/2 "2022-10-21T19:53:45Z")
Closing the loop here with a link to the [discussion on GitHub](https://github.com/grafana/grafana/issues/57098). Summary: If the labels match the nested policy definitions, then that’s the only contact point the alert is sent to.