What it is
The Status Page is a public board, in the style of a statuspage.io, that anyone holding your organisation's public link can read without signing in. It exists so that during an outage the people affected can find out what is happening without opening a ticket to ask.
The important thing to understand is that you do not author its content. There is no "post an update" box that writes prose onto a page. The board is derived, every time it is loaded, from records you are already maintaining.
What appears on it
Two things, both pulled live:
- Currently-active Major Incidents - incident-class tickets flagged as major and not yet resolved. Resolve the incident and it leaves the board.
- Upcoming maintenance windows - Releases that are scheduled or in progress and carry a scheduled window.
So the way to update the status page is to update the incident or the release. That is deliberate: a board maintained separately from the incident record is a board that goes stale precisely when it is being read most.
It also means an incident nobody flagged as major will not appear, however badly it is going. If customers should be seeing it, the fix is to declare it a Major Incident, not to look for a status-page editor.
The public link and its token
The board is reached at a URL carrying an unguessable token for your organisation. Anyone with the link can read it; nobody without it can. There is no login and no account.
You can rotate the token from the configuration page. Rotating it immediately invalidates the old link - which is the point, and also the caution: anyone you previously gave the link to, and any bookmark or wiki page carrying it, stops working at that moment. Rotate deliberately, and be ready to redistribute.
You can also enable or disable the board and set its title.
Subscribers
Visitors to the board can subscribe an email address to receive updates. From the configuration page you can:
- list the subscribers;
- export them, as CSV or XLSX; and
- delete a single subscriber by address.
That last one is a genuine erasure, provided for GDPR requests - the address is removed rather than flagged. If somebody asks to be forgotten, this is the control that answers it, and it is worth knowing it exists before the request arrives.
Remember what a subscriber list is: a list of people who told you they care when you break. Treat the export accordingly.
Who can do what
- Admin and above configure the board, rotate the token, and manage subscribers.
- Anyone with the link can read the board and subscribe - by design, without authentication.
Related
- Major Incidents - what puts an entry on the board
- Release Management - where the maintenance windows come from
- TATER Ops overview - where this page sits in the console