summaryrefslogtreecommitdiff
path: root/doc/operations/incident_management/paging.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/operations/incident_management/paging.md')
-rw-r--r--doc/operations/incident_management/paging.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/operations/incident_management/paging.md b/doc/operations/incident_management/paging.md
index 27854a9e201..d0c14ab6e59 100644
--- a/doc/operations/incident_management/paging.md
+++ b/doc/operations/incident_management/paging.md
@@ -50,7 +50,13 @@ or stop alert escalations by [updating the alert's status](alerts.md#update-an-a
### Escalating an incident
-> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5716) in GitLab 14.9.
+> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5716) in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `incident_escalations`. Disabled by default.
+> - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) in GitLab 14.10.
+
+FLAG:
+This feature is available by default. To disable it per project or for your entire
+instance, ask an administrator to [disable the feature flag](../../administration/feature_flags.md)
+named `incident_escalations`.
For incidents, paging on-call responders is optional for each individual incident.
To begin escalating the incident, [set the incident's escalation policy](incidents.md#change-escalation-policy).