> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Publishing Updates to Status Pages
> Post incidents, scheduled maintenance, and announcements to your status pages from the web, Slack, or @Rootly.
Posting to a status page shares what's happening with the people who depend on you, keeping them informed while you work.
Posting is deliberate, not automatic. An incident linked to a component on your page isn't posted on its own. Someone on your team writes and posts each update, so every message is reviewed before customers see it.
**Private incidents can only be published to private status pages.** The **Publish Incident** dialog on a [private incident](/incidents/private-incidents/private-incidents) hides public status pages entirely, and workflow **Publish Incident** actions targeting a public page for a private incident fail with `Cannot publish a private incident to a public status page`. If your organization keeps every incident private, plan your status page setup accordingly.
## Publishing Updates
Go to **Status Pages**, open a page, and click **Post to page**. Then choose what to post:
* **Incident:** An unplanned issue.
* **Scheduled maintenance:** Planned work with a start and end time. See Scheduled Maintenance.
* **Announcement:** A standalone notice. See Announcements.
## Publishing Incidents
When you post an incident, the page shows:
* The incident title
* Affected components and their impact levels
* A timeline of updates
* The incident's current status
### Post an Incident Update from the Web
You can start from the status page with **Post to page** → **Incident**, or from the incident's **Status Page** tab.
1. Choose the incident to post about, or choose **Create new incident**. A new incident is only created when you post.
2. Under **Status pages**, pick the pages to update. The pages from your last update are preselected, or check **All**.
3. Pick a **Status**: Investigating, Identified, Monitoring, or Resolved.
4. Choose a **Template** (optional), or write the **Message**.
5. Under **Affected components**, add the affected components and set an impact level for each.
6. Leave **Update subscribers** on to let subscribers know.
7. Click **Post update**.
### Update and Resolve an Incident
As the incident moves along, keep posting updates from the same place so customers see progress.
* Post each new update with the latest status and message.
* When the incident is over, post a final update with the status set to **Resolved**, so customers know it's fixed.
### Post from Slack
Post updates without leaving the incident channel, so responders can keep customers informed while they work. Slack supports incident updates and announcements.
1. In the incident's Slack channel, type `/rootly statuspage`. The **Update status page** modal opens.
2. Under **Status pages**, pick one or more pages.
3. Add a **Public Title**. Everyone who can see the page sees this title.
4. Pick a **Status**: Investigating, Identified, Monitoring, or Resolved.
5. In **Event**, write what's happening.
6. Under **Impacted Components** (optional), add the affected components. An impact level appears for each one, so you can set how badly it's affected.
7. Click **Submit**.
### How it behaves
* Components linked to the incident are preselected, and components you don't select keep their current status.
* Posting to several pages is all or nothing, and every selected page gets the same update.
### Ask @Rootly to post
Tell @Rootly what to post in plain language. It sets up the update from the incident, asks you for the message, and waits for your confirmation before anything goes live.
1. In the incident's Slack channel, mention `@Rootly` with your request. For example: "Post an Investigating update to the public status page", "Post a Monitoring update to the US and EU pages, mark Auth Service as degraded", or "Resolve this on all status pages".
2. @Rootly fills in the pages, status, and affected components from your request and the incident.
3. It asks you for the message to post.
4. Review the update, then click **Confirm** in the thread to post it.
**How it behaves**
* **You approve every update.** Nothing is posted until you click Confirm.
* **Incidents and announcements.** Scheduled maintenance is web only.
* **It works where the incident runs.** Write actions only work inside incident channels. The Slack side pane and DMs are read-only.
* **It respects your role.** @Rootly can only take actions your Rootly user has permission to perform.
* It can post to several pages and include affected components.
* It requires @Rootly in Slack to be turned on for your team. See [Getting Started with Rootly AI in Slack](/ai/rootly-in-slack/getting-started).
## Publishing Scheduled Maintenance
Let customers know about planned work before it happens, so nobody mistakes it for an outage.
Scheduled maintenance is posted from the web.
1. Go to **Status Pages** and open a page.
2. Click **Post to page** → **Scheduled maintenance**. The **Scheduled maintenance** form opens.
3. Add a **Title**, plus the **Start** and **End** times.
4. Write the **Message**. Tell customers what to expect during the window.
5. Under **Affected components**, add the components the work touches.
6. Leave **Update subscribers** on to let subscribers know.
7. Click **Post**.
### How It Behaves
* **Auto-resolve** is on by default, so the maintenance is marked complete when the end time passes.
* Maintenance posts to the page you open it from.
## Publishing Announcements
Share planned changes, notices, or general updates on your status page without opening an incident. Customers get the news in the same place they already check for service health.
### When to Use Announcements
* New features, policy updates, region migrations, general notices, and deprecation notices
* Information that affects customers but isn't an outage
* Messages that should stay off the incident timeline and out of incident metrics
### Post an Announcement from the Web
1. Go to **Status Pages** and open a page.
2. Click **Post to page** → **Announcement**. The **New announcement** form opens.
3. Add a **Title** and **Message**.
4. Under **Publish to**, check the pages to post on, or check **All**.
5. Leave **Notify subscribers** on to let subscribers know, or turn it off to post quietly.
6. Click **Post announcement**.
**How it behaves**
* An announcement is a standalone post. It isn't tied to an incident or maintenance window.
* It shows as a banner at the top of the status page.
* It doesn't change any component status.
* You can post it to several pages at once.
* After posting, you can edit or remove it.
## Publishing to Multiple Pages
Send one update to every page that needs it, instead of repeating the same update page by page. This matters most for teams running regional, brand, or per-customer pages.
1. Open the **Post update** form from a status page with **Post to page** → **Incident**, or from the incident's **Status Page** tab.
2. Under **Status pages**, check each page you want to update, or check **All**. The pages from your last update are preselected.
3. Pick the status, write the message, and set the affected components.
4. Click **Post update**.
**How it behaves**
* Every selected page gets the same status, message, and affected components.
* Works for incidents and announcements, on the web and in Slack. Scheduled maintenance posts to one page at a time.
***
## Related Pages
The umbrella concept — where published incidents actually show up.
Set up the page before you can publish updates to it.
Where published-update events surface inside the incident record.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.