From 3683f407f492c161651cf27711f0f562d955e86c Mon Sep 17 00:00:00 2001
From: Pangidoan Butar <38452094+doanbutar@users.noreply.github.com>
Date: Thu, 9 Nov 2023 09:28:32 +0800
Subject: [PATCH] A few clarifications and updates for "Notify whole Slack
 channel" and "Notify Slack User Group"

https://github.com/grafana/support-escalations/issues/8169#issuecomment-1799997674
---
 docs/sources/escalation-chains-and-routes/_index.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md
index 2c9a255f..a372cccf 100644
--- a/docs/sources/escalation-chains-and-routes/_index.md
+++ b/docs/sources/escalation-chains-and-routes/_index.md
@@ -69,6 +69,11 @@ Useful when you want to get escalation only during working hours
 passes some threshold
 * `Repeat escalation from beginning (5 times max)` - loop the escalation chain
 
+   > **Note:** Both "**Notify whole Slack channel**" and "**Notify Slack User Group**" will filter OnCall registered users matching the users in the Slack channel or Slack User Group with their profiles linked to their Slack accounts (ie. users should have linked their Slack and OnCall users). In both cases, the filtered users satisfying the criteria above are notified following their respective notification policies. 
+
+   > However, to avoid **spamming** the Slack channel/thread, users **won't be notified** in the alert group Slack **thread** (this is how the feature is currently implemented) but instead notify them using their **other defined** options in their [respective policies]([url](https://grafana.com/docs/oncall/latest/notify/#configure-user-notification-policies)).
+
+
 ### Notification types
 
 Each escalation step that notifies a user, does so by triggering their personal notification steps. These are configured in the Grafana