2020-10-01 00:10:16 +00:00
---
stage: Monitor
group: Health
2020-11-26 06:09:20 +00:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-01 00:10:16 +00:00
---
2021-01-28 06:08:59 +00:00
# Paging and notifications **(FREE)**
2020-10-01 00:10:16 +00:00
2020-10-14 18:08:47 +00:00
When there is a new alert or incident, it is important for a responder to be notified
immediately so they can triage and respond to the problem. Responders can receive
notifications using the methods described on this page.
2020-10-01 00:10:16 +00:00
## Slack notifications
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216326) in GitLab 13.1.
2020-10-14 18:08:47 +00:00
Responders can be paged via Slack using the
[Slack Notifications Service ](../../user/project/integrations/slack.md ), which you
can configure for new alerts and new incidents. After configuring, responders
receive a **single** page via Slack. To set up Slack notifications on your mobile
device, make sure to enable notifications for the Slack app on your phone so
you never miss a page.
2020-10-01 00:10:16 +00:00
## Email notifications
2021-03-04 21:08:59 +00:00
Email notifications are available in projects for triggered alerts. Project
members with the **Owner** or **Maintainer** roles have the option to receive
a single email notification for new alerts.
2020-10-01 00:10:16 +00:00
1. Navigate to **Settings > Operations** .
1. Expand the **Incidents** section.
2021-03-04 21:08:59 +00:00
1. In the **Alert Integration** tab, select the checkbox
**Send a single email notification to Owners and Maintainers for new alerts** .
2020-10-01 00:10:16 +00:00
1. Select **Save changes** .
