# The team view of a status page

> Your status page is written for your customers. It answers one question — is something broken — and it deliberately answers nothing else.

Source: https://infranest.io/docs/status-page-team-view
Last updated: 2026-09-19

---

The team view shows your team what customers never see on a status page — who's on call and where the runbook is. It's for anyone who helps keep your services running.

## Overview

- Your public status page answers one question for customers: is something broken?
- The team view is the same page, written for the people fixing things — it lives behind your normal sign-in.
- It adds two things customers never see: who's on call, and links to your runbooks.
- It refreshes every 30 seconds, so you can leave it open during an incident.

## Open the team view

1. Go to **Status Pages**.
2. Click the lifebuoy icon on any page.

<!-- screenshot: status-page-team-view -->

<!-- docs-screenshots:start:status-page-team-view -->

![The team view of a status page](/media/28c93584-f71c-4386-8483-8afde5bce383)

<!-- docs-screenshots:end:status-page-team-view -->

## What you see

- **The strip at the top** — overall status, how many of the page's services are up, the average uptime over the last 30 days, and when the next maintenance window starts.
- **On call** — whoever is holding the pager for this page. You write this yourself; see below.
- **Open right now** — every incident currently running on this page's services, with a link to the public write-up. That's the link to paste into a support ticket — it's the page your customer can actually read.
- **Services, last 30 days** — every service on the page, grouped exactly as your customers see them, with uptime bars, when it was last checked, and how many monitoring regions are still reporting on it. If a service has a runbook link, you'll see a **Runbook** button beside it.

## Set the on-call contact

1. Go to **Status Pages**.
2. Open the page.
3. Fill in **On-call contact**.

It's free text, so put whatever your team actually needs: a name and a phone number, a link to your rota in PagerDuty or a spreadsheet, or a Slack channel. There's no rota built in — this is a pointer to wherever yours already lives.

> [!TIP]
Clearing the box removes it. Do this when someone leaves the rotation — a stale name here is how last quarter's on-call keeps getting called.

## Add a runbook link to a service

1. Go to **Status Pages** and open the page.
2. Open the **Components** tab.
3. Click a service.
4. Fill in **Runbook link**.

It has to start with `https://`. Point it at the document for *that* service, not at your wiki's front page — the whole reason it sits on the service is that someone woken at 3am should land on the right document, not on an index.

## Who can see it

Only people signed in to your organisation.

> [!NOTE]
This is worth being precise about, because status pages have a password option and the two are unrelated. Someone who knows your status page's password sees the public page and nothing more. The on-call contact and the runbook links are never sent to that page — they only ever appear in the team view, which requires a real sign-in.

## Which plans include it

The team view is part of **private status pages**. If your plan doesn't include it, the page tells you so, and everything else about your status page works exactly as before.