diff --git a/openmetadata-docs/content/v1.5.x/how-to-guides/admin-guide/alerts.md b/openmetadata-docs/content/v1.5.x/how-to-guides/admin-guide/alerts.md
index 0c7f1dc5498..8792a34f249 100644
--- a/openmetadata-docs/content/v1.5.x/how-to-guides/admin-guide/alerts.md
+++ b/openmetadata-docs/content/v1.5.x/how-to-guides/admin-guide/alerts.md
@@ -5,6 +5,15 @@ slug: /how-to-guides/admin-guide/alerts
 
 # Set up Data Observability Alerts and Notifications
 
+{%inlineCalloutContainer%}
+ {%inlineCallout
+    icon="MdGppGood"
+    bold="Required Permissions"
+    href="/how-to-guides/admin-guide/roles-policies"%}
+    Setting up alerts requires create permission on the `Eventsubscription` entity. More info here.
+ {%/inlineCallout%}
+{%/inlineCalloutContainer%}
+
 OpenMetadata has been providing alerts right from the start to notify users of important data lifecycle events: schema modifications, ownership shifts, and tagging updates. Users can define fine-grained alerts and notifications.
 
 Starting from the 1.3 release, Data Observability alerts have been completely revamped, simplifying the process of monitoring data. Users can quickly create alerts for:
diff --git a/openmetadata-docs/content/v1.6.x/how-to-guides/data-quality-observability/observability/alerts.md b/openmetadata-docs/content/v1.6.x/how-to-guides/data-quality-observability/observability/alerts.md
index e8575b94f2e..e497d91c9ce 100644
--- a/openmetadata-docs/content/v1.6.x/how-to-guides/data-quality-observability/observability/alerts.md
+++ b/openmetadata-docs/content/v1.6.x/how-to-guides/data-quality-observability/observability/alerts.md
@@ -7,6 +7,15 @@ slug: /how-to-guides/data-quality-observability/observability/alerts
 OpenMetadata provides a native way to get alerted in case of test case failure allowing you to proactively resolve data incidents
 
 ## Setting Up Alerts
+{%inlineCalloutContainer%}
+ {%inlineCallout
+    icon="MdGppGood"
+    bold="Required Permissions"
+    href="/how-to-guides/admin-guide/roles-policies"%}
+    Setting up alerts requires create permission on the `Eventsubscription` entity. More info here.
+ {%/inlineCallout%}
+{%/inlineCalloutContainer%}
+
 To set up an alert on a test case or test suite, navigate to the observability menu and select `Alerts` and click on `Add Alert`.
 
 {% image
diff --git a/openmetadata-docs/content/v1.7.x-SNAPSHOT/how-to-guides/admin-guide/alerts.md b/openmetadata-docs/content/v1.7.x-SNAPSHOT/how-to-guides/admin-guide/alerts.md
index c4b5c55d63c..3e03275748b 100644
--- a/openmetadata-docs/content/v1.7.x-SNAPSHOT/how-to-guides/admin-guide/alerts.md
+++ b/openmetadata-docs/content/v1.7.x-SNAPSHOT/how-to-guides/admin-guide/alerts.md
@@ -22,6 +22,16 @@ Depending on your use cases, notifications can be sent to owners, admins, teams,
 - [Additional Details for the Configuration of Destinations](#additional-details-for-the-configuration-of-destinations)
 
 ## Create Observability Alerts
+
+{%inlineCalloutContainer%}
+ {%inlineCallout
+    icon="MdGppGood"
+    bold="Required Permissions"
+    href="/how-to-guides/admin-guide/roles-policies"%}
+    Setting up alerts requires create permission on the `Eventsubscription` entity. More info here.
+ {%/inlineCallout%}
+{%/inlineCalloutContainer%}
+
 ### Step 1
 Navigate to Observability > Alerts.