> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/status-pages.md).

# Status Pages

A status page shows the current health of a set of services to the people who depend on them. You build it from shared categories, from monitors added directly, or both, and share its public link. The status of a page is computed every minute from its monitors; it is never set by hand.

Open it from **Workspaces** → **Service Health** → **Status pages** in the sidebar.

{% hint style="info" %}
Requires the **Service Health** licence.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtMm769k23iN78dHEI7DL%2Fv2-sh-status-pages.png?alt=media&amp;token=f1861a5c-ebfd-4ca6-a9a3-658a4d4c853a" alt="Status pages list"><figcaption><p>Status pages</p></figcaption></figure>

## Status Pages List

Use the **Status** filter to show **All**, **Needs attention**, **Private** or **Disabled** pages; **Save filters** keeps a combination to pick again from **Saved filters**. The list has a search box, **Refresh**, **Columns** and **Export**.

| Column          | Description                                                                                                                                                                     |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Status page** | Page name. Click it to open the owner view (**Owner View** below).                                                                                                              |
| **Status**      | The page status and its last check. A page with nothing on it stays **Unknown**.                                                                                                |
| **Visibility**  | **Public** or **Private**, **Disabled** when the page is turned off, and a **Managed by** tag when a monitoring policy maintains the page.                                      |
| **On the page** | How many categories and directly added monitors the page shows, or **Nothing added yet**.                                                                                       |
| **Public link** | **Copy public link** and **Open public page** for an enabled public page. A private page shows **Private · no public link**; a disabled page shows that its link shows nothing. |
| **Actions**     | **Review page**, **Edit settings** and delete.                                                                                                                                  |

## Owner View

Click a page name to open its owner view. It shows the page as its audience sees it, plus private monitors that the public link never shows. Only signed-in users with status page access see it. From there you can **Copy public link**, **Open public page**, **Configure page**, open **Maintenance windows** and **Subscribe to updates**. The **Current status**, **Uptime** and **Incident history** tabs show the live state, past availability and incidents.

## Create a Status Page

1. Click **Create status page**.
2. Fill in the fields below.
3. Click **Create status page**. The new page opens in the review drawer, where you can keep adding content.

| Field                       | Description                                                                                                                         |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Status page name**        | **Required.** Up to 100 characters.                                                                                                 |
| **Visibility**              | **Public**: the page has a link anyone can open. **Private**: no public link; signed-in users open its private view from this list. |
| **Page state**              | **Enabled** or **Disabled**. A disabled page shows nothing on its public link.                                                      |
| **Shared categories**       | Optional. Each category shows its monitors under its own heading.                                                                   |
| **Monitors added directly** | Optional. Listed in the page's own **Services** section, first on the public page.                                                  |

**Edit settings** on a row changes the name, visibility and page state.

## Review a Page

Click **Review page** on a row.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FLKZyOZutzLzsYSIiDLkb%2Fv2-sh-status-review.png?alt=media&amp;token=538eb179-2fce-45c2-b020-d865b26388d3" alt="Status page review drawer showing what the page shows now"><figcaption><p>Review a status page</p></figcaption></figure>

The drawer shows:

* The status, last check, visibility, page state and the number of shared categories and directly added monitors.
* **Open private view** and **Manage subscriptions**, where people subscribe to updates about the page.
* A notice that says how many enabled services the public page lists, and why.
* **What the page shows now**: each enabled monitor with its section, status, last check and **Public page** state: **Listed**, **Private view only** (the monitor is private), **Category hidden** or **Not published** (the page is private or disabled).
* **Monitors added directly**: search and click **Add monitor to page**, or **Remove monitor**.
* **Shared categories**: search and click **Add category to page**, or **Remove category**. **Manage categories →** opens [Categories](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/categories.md).

{% hint style="info" %}
Only public, enabled monitors appear on a public page. Disabled monitors are never listed.
{% endhint %}

### Pages Maintained by a Monitoring Policy

A page created by a monitoring policy shows **Maintained by** in its drawer. The policy adds a section per asset type as it creates monitors. Click **Take over** to stop the policy maintaining the page; everything on it stays as it is, and from then on you change it yourself.

{% hint style="warning" %}
You need a role that can create status pages to create one, a role that can edit status pages to change settings or content, and a role that can delete status pages to delete one or remove a category from it. Adding monitors also needs a role that can view monitors.
{% endhint %}

## Next Steps

* [Categories](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/categories.md): group monitors once and reuse them on several pages.
* [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md): make monitors public so they can appear on public pages.
* [Maintenance Windows](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/maintenance-windows.md): announce planned work on a page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/status-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
