diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md
index 83d7b737b98ab..f282caa951749 100644
--- a/content/en/service_management/status_pages/_index.md
+++ b/content/en/service_management/status_pages/_index.md
@@ -9,45 +9,63 @@ further_reading:
text: "Learn more about On-Call Scheduling"
---
-{{< callout url="https://www.datadoghq.com/product-preview/status-pages/">}}
-Status Pages is in Preview.
-{{< /callout >}}
-
## Overview
-{{< img src="service_management/status_pages/shopist_status_page_example.png" alt="Example status page showing service components with their current status and recent incident updates" style="width:100%;" >}}
+{{< img src="service_management/status_pages/shopist_status_page.png" alt="Example status page showing service components with their current status and recent incident updates" style="width:100%;" >}}
-Status Pages are part of Datadog's Incident Response suite, alongside On-Call and Incident Management. They let your team proactively communicate **service availability**, **incidents**, and **maintenance updates** with customers or internal stakeholders through a shareable web page.
+Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability** and **incidents** with customers or internal stakeholders through a shareable web page.
Use Status Pages to:
* Share the availability of critical systems and features
* Communicate service disruptions clearly during incidents
-* Reduce inbound support volume with proactive updates
+* Reduce inbound support volume with proactive email notifications
-## Configure permissions
+## Configure permissions
There are three RBAC permissions that are relevant to Status Pages. Users with the Datadog Admin Role have all the necessary permissions.
To create, update, or publish Status Pages, you must have `status_pages_settings_read`, `status_pages_settings_write`, and `status_pages_incident_write` RBAC permissions. For more information, see [Access Control][1].
-| Name | Description | Default Role |
-| :---- | :---- | :---- |
-| Status Pages Settings Read (`status_pages_settings_read`) | View the list of Status Pages, the settings of each Status Pages, their Incidents, and launched Internal Status Pages. | Datadog Read Only Role |
-| Status Pages Settings Write (`status_pages_settings_write`) | Create and launch new Status Pages, and configure Status Pages settings. | Datadog Admin Role |
-| Status Pages Incident Write (`status_pages_incident_write`) | Publish and update Incidents. | Datadog Admin Role |
+
+
+
+ | Name |
+ Description |
+ Default Role |
+
+
+
+
+ Status Pages Settings Read
status_pages_settings_read |
+ View the list of Status Pages, the settings of each Status Pages, their Incidents, and launched Internal Status Pages. |
+ Datadog Read Only Role |
+
+
+ Status Pages Settings Write
status_pages_settings_write |
+ Create and launch new Status Pages, and configure Status Pages settings. |
+ Datadog Admin Role |
+
+
+ Status Pages Notice Write
status_pages_incident_write |
+ Publish and update Incidents. |
+ Datadog Admin Role |
+
+
+
## Create a status page
-1. In Datadog, navigate to [**Service Management > Status Pages**][2].
+1. In Datadog, navigate to [**Service Management > Status Pages**][2].
1. Click **Create Status Page** and follow the onboarding flow:
| Field | Description |
| ----------------- | ----------- |
- | **Visibility** | Choose who can access the page:
- **Public** - Anyone with the link can view
- **Internal** - Only authenticated users within your Datadog organization can view |
+ | **Status Page Type** | Choose who can access the page:
- **Public** - Anyone with the link can view
- **Internal** - Only authenticated users within your Datadog organization can view |
| **Page name** | Displayed as the page header (if no logo is uploaded).
*Example: Acme Cloud Platform* |
- | **Domain Prefix** | Used as your status page subdomain prefix.
*Example: shopist → shopist.status.datadoghq.com*
- Must be **globally unique**
- Lowercase, alphanumeric, and hyphenated
- May affect links if changed later |
- | **Company logo or Favicon** *(optional)* | Upload a logo or favicon to personalize the appearance of your status page |
+ | **Domain Prefix** | Used as your status page subdomain prefix.
*Example: shopist → shopist.statuspage.datadoghq.com*
- Must be **globally unique**
- Lowercase, alphanumeric, and hyphenated
- May affect links if changed later |
+ | **Subscriptions** *(optional)* | Enable users to receive email notifications about status page updates. When subscriptions are enabled, users can sign up to get notified about new notices and updates. You can turn subscriptions on or off for each status page. **Note**: [Email subscriptions](#email-subscriptions) are double opt-in, email must be confirmed. |
+ | **Company logo, Favicon, or Email Header Image** *(optional)* | Upload a logo, favicon, or image to personalize the appearance of your status page and email notifications. |
1. (Optional) [Add components](#add-components) to show the status of individual services.
1. Click **Save Settings**.
@@ -57,54 +75,59 @@ To create, update, or publish Status Pages, you must have `status_pages_settings
{{< img src="/service_management/status_pages/status_page_components.png" alt="Status page component configuration with live preview panel" style="width:100%;" >}}
Components are the building blocks of your status page. Each one represents a service or feature your users care about. Some examples of components include:
-- API Gateway
-- Web Dashboard
-- Database Cluster
+- API Gateway
+- Web Dashboard
+- Database Cluster
- US Region Services
You can add components to your status page either on intial setup or through the status page settings:
1. From your status page, click **Settings** and select the **Components** tab.
-1. Create individual components or a group of related components. You can associate [incidents](#add-an-incident) with these components to reflect impact on your status page.
-1. Select a visualization type:
- 1. Bars and Uptime Percentage
- 1. Bars Only
- 1. Component Name Only
+1. Create individual components or a group of related components. You can associate [notices](#add-a-notice) with these components to reflect impact on your status page.
+1. Select a visualization type:
+ 1. Bars and Uptime Percentage
+ 1. Bars Only
+ 1. Component Name Only
## Publish your status page
After you save your status page settings, click **Launch Status Page** to make the page available at its URL.
If you selected:
-- **Public**, the page is immediately accessible to all visitors.
+- **Public**, the page is immediately accessible to all visitors.
- **Internal**, access is limited to authenticated Datadog users in your organization.
-## Add an incident
-
-Incidents published on Status Pages are not the same as incidents declared within Datadog Incident Management. Incidents on Status Pages are carefully crafted messages posted to a public website to communicate system status, and may encompass multiple internal Incident Management incidents.
+## Add a notice
-When an issue arises, you can communicate it clearly through your status page.
+Notices on Status Pages are carefully crafted messages posted to a public website to communicate system status. When an issue arises, you can communicate it clearly through your status page.
-1. From a status page, click **Publish Incident** to open a "Publish Status Page Incident" modal and provide:
+1. From a status page, click **Publish Notice** to open a "Publish Status Page Notice" modal and provide:
| Field | Description |
| ---- | ---- |
| **Title** | Short, clear description of the incident
*Example: Increased error rates on US region* |
| **Status** | Current state of the incident:
- Investigating
- Identified
- Monitoring
- Resolved |
| **Message** *(optional)* | Additional details for your users
*Examples: known cause, expected resolution time* |
- | **Affected Components** | One or more components impacted by the incident |
+ | **Components impacted** | One or more components impacted by the incident |
| **Impact** | Level of impact per component:
- Operational
- Degraded Performance
- Partial Outage
- Major Outage |
-1. Click **Publish Incident**.
+ | **Notify Subscribers** | Toggle to send the notice to subscribers |
+1. Click **Publish Notice**.
-{{< img src="/service_management/status_pages/publish_status_page_incident.png" alt="Screenshot of the Status Page Incident creation modal with fields filled out" style="width:70%;" >}}
+{{< img src="/service_management/status_pages/publish_status_page_incident_1.png" alt="Screenshot of the Status Page Notice creation modal with fields filled out" style="width:70%;" >}}
-After an incident is published, the incident:
-- Appears on the Status Pages List under **Active Incidents**.
+After a notice is published, the notice:
+- Appears on the Status Pages List under **Active Notices**.
- Updates the uptime bars for impacted components.
-- Is visible in the incident history timeline.
+- Is visible in the notice history timeline.
+
+You can post **updates** over time to keep users informed, and then mark the notice as **Resolved**.
+
+{{< img src="/service_management/status_pages/live_status_page_incident_history.mp4" alt="Video showing the noticce history timeline on a live status page with published notices and updates" video=true >}}
+
+## Email subscriptions
-You can post **updates** over time to keep users informed, and then mark the incident as **Resolved**.
+Email subscriptions on status pages are **double opt-in**: users must confirm their email address before they are added as subscribers. After entering an email to subscribe, a confirmation email is sent, and the subscription is only activated after the user clicks the confirmation link.
-{{< img src="/service_management/status_pages/live_status_page_incident_history.mp4" alt="Video showing the incident history timeline on a live status page with published incidents and updates" video=true >}}
+For **internal** status pages, the subscription process is the same, but users must log in to the same Datadog organization to confirm their subscription and receive notifications.
## Further reading
diff --git a/static/images/service_management/status_pages/publish_status_page_incident_1.png b/static/images/service_management/status_pages/publish_status_page_incident_1.png
new file mode 100644
index 0000000000000..1aec82a31c1a6
Binary files /dev/null and b/static/images/service_management/status_pages/publish_status_page_incident_1.png differ
diff --git a/static/images/service_management/status_pages/shopist_status_page.png b/static/images/service_management/status_pages/shopist_status_page.png
new file mode 100644
index 0000000000000..b575d9b8a5d83
Binary files /dev/null and b/static/images/service_management/status_pages/shopist_status_page.png differ