> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer reliability portal

> Give each customer a private page with the live status of their services, their contracted service levels, signed statements and the incidents that affected them.

The reliability portal is a private page for one customer. It shows what
Observer measured for that customer: the live status of the services in
their contract, their service levels month by month, their signed SLA
statements, and the incidents that affected them. A customer opens it
with an access link you give them.

<Info>
  The reliability portal is available on the Business and Enterprise
  plans.
</Info>

## Before you start

* The status page has the **Reliability Center** turned on. Open the page
  in the page builder and turn it on under **Identity**.
* The customer exists under **Customers** and has an SLA contract with at
  least one line. The portal reads its service levels from the contract
  and its statements from [SLA Ledger](/docs/concepts/sla-methodology).

## What the customer sees

The portal lives at `/reliability/portal` on the status page's address
(its subdomain or its custom domain). It has five sections.

### Your services

The live status of the check behind each of the customer's contract
lines, one row per SLO, with the service name and the time of the last
result ("Last reported ...") in the page's time zone. The status is the
check's current status, as on the status page.

### Your service levels

Each contract line with its contracted target, the attainment for the
month so far, and the **last 12 closed months**. Month to date is
computed with the contract's own rules. Closed months are shown exactly
as stated in the statements delivered to the customer, so the portal
never shows a figure for a closed month that differs from the signed
statement. A month with no delivered statement has no figure.

### Your statements

Every statement delivered to the customer, with its period, its lowest
attainment, and its delivery date or revision. Each statement downloads
as **PDF**, **CSV** or **JSON**, and **Verify a statement** opens the
verify page with the statement's SHA-256 digest filled in. See
[Integrity](/docs/concepts/sla-methodology#integrity) for how statements
are signed.

### Incidents that affected you

Published incidents from the last 12 months that are marked as affecting
this customer, or that target all customers, and that this customer is
allowed to see. Each shows when it was published and whether it is
resolved, with a link to the incident history and, when one is set, the
postmortem. Up to 50 incidents are listed, newest first.

### Notifications

How many addresses from the customer's organization receive updates from
the page. No addresses are shown. Each recipient changes channels or
services, or unsubscribes, from the preferences link in any notification
they receive. See
[Status page subscriptions](/docs/guides/status-page-subscriptions).

## Give a customer access

<Steps>
  <Step title="Open the customer">
    In the console, open **Customers**, select the customer and open the
    **Contract** tab.
  </Step>

  <Step title="Create an access link">
    Under **Access links**, choose the status page and select **Create access
    link**. Only pages with the Reliability Center turned on are listed.
  </Step>

  <Step title="Copy the link and send it">
    The link is shown once. Copy it and send it to the customer yourself:
    creating a link sends no email. Observer stores only a hash of the link,
    so it cannot be shown again. Create a new one if it is lost.
  </Step>
</Steps>

Statement emails also carry a fresh access link: the **View your
statements** button in every delivered statement opens the customer's
view. These links appear in the list tagged **Statement email**.

## How access links work

* A link looks like
  `https://status.example.com/reliability?access=rca_...`. It opens the
  Reliability Center for that customer, which then shows **Open your
  portal**.
* A link is valid for **90 days**. It can be opened as often as needed
  until it expires or is revoked.
* Opening a link starts a session in that browser. The session lasts 30
  minutes from the last page view or download, and never outlasts the
  link.
* Without a session, the portal shows only "Open the access link you were
  sent to see your portal." It never names a customer.
* An expired or revoked link shows that the link is invalid, expired or
  revoked, and the public Reliability Center below it stays visible.
* To revoke a link, select **Revoke** next to it under **Access links**.
  The customer loses access through it on their next request. Other links
  keep working.
* The list shows each link's page, creation date, last use, expiry and
  state (**Active**, **Expired** or **Revoked**).

If the status page itself is protected (password, sign-in, IP allowlist
or a token), the customer must pass that protection too. The access link
decides which customer's view is shown; it does not bypass the page's
access settings. See [Sign-in protected pages](/docs/guides/sign-in-protected-pages).

The portal is never indexed by search engines.


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