> ## 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.

# Global Status Page Templates

> Create organization-wide update templates that responders can use on any status page, so every team posts consistent messages.

Global templates are update templates for your whole organization. Write them once and they're offered on every status page, next to each page's own templates. Teams reuse the same wording without copying templates into every page.

## Global and Page Templates

| | Page templates | Global templates |
| - | - | - |
| Where you manage them | The page editor's **Templates** tab | The **Templates** tab on the Status pages index |
| Where they're offered | That page only | Every status page |
| Fields | Title, kind, update status, update title, message, notify subscribers | The same |

Page templates work the same as before. See [Creating a Status Page](https://docs.rootly.com/configuration/creating-a-status-page.md#templates).

## Create a Global Template

**1. Open Templates**

Go to **Status Pages** and click the **Templates** tab at the top of the page.

**2. Add a Template**

Add a new template and fill in its fields:

* **Title:** The template's name, which responders see in the picker.
* **Kind:** **Incident** or **Maintenance**. This decides which updates the template is offered for.
* **Update status:** The status the update is posted with.
* **Update title** and **Message:** The content that's pre-filled in the update.
* **Notify subscribers:** Whether subscribers are notified by default.

**3. Save**

Save the template. Enabled templates are offered on every status page right away.

## Use a Global Template

When you post an update from the web or with `/rootly statuspage` in Slack, the template picker lists:

1. The selected page's own templates, first.
2. Your enabled global templates after them, labeled as global.

Selecting a global template fills in the update's status, title, message, and notify subscribers setting, just like a page template. You can edit anything before you post, and the edited version is what gets published.

**How it behaves**

* **Matched to the update type.** Incident templates are only offered for incidents, and maintenance templates only for scheduled maintenance.
* **Listed once when you post to several pages.** Each global template appears once, not once per page.
* **Pages without templates still get them.** If a page has no templates of its own, the picker shows only global templates.

See [Publishing Updates](https://docs.rootly.com/configuration/publishing-incidents.md).

## Manage Global Templates

* **Edit:** Changes apply to new updates. Updates already published keep their content.
* **Disable:** A disabled template isn't offered in any picker. Enable it again to bring it back.
* **Delete:** The template stops appearing in pickers. Updates already published keep their content.

You need a role with permission to create or update status pages to create, edit, or delete global templates.

## Limits

| Limit | Value |
| - | - |
| Global templates per organization | 100 |
| Template title | 255 characters |
| Message body | 10,000 characters |

Going over a limit shows a validation error when you save.

> [!NOTE]
>
> Global templates aren't offered in the **Publish Incident to Status Page** workflow action, and they aren't returned by the status page templates API. Both work with page templates only.

***

## Related Pages

> [card] [Creating a Status Page](https://docs.rootly.com/configuration/creating-a-status-page.md)
>
> Set up a page, including its own templates.

> [card] [Publishing Updates](https://docs.rootly.com/configuration/publishing-incidents.md)
>
> Post incidents, scheduled maintenance, and announcements.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.