# Keychain page

> The console's Keychain page, its two tabs (Keychain and Installs), what each state shows, the help on every term, and who can use it.

Source: https://docs.3am.si/console/keychain · Markdown: https://docs.3am.si/console/keychain.md · All docs: https://docs.3am.si/llms.txt
3AM is an on-prem AI on-call engineer for regulated enterprises (https://3am.si).

**Keychain** (`/keychain`, `g k`) is where an organisation with several installs sets 3AM up once. How the Keychain
works, end to end: [Keychain](https://docs.3am.si/licensing/keychain). This page is the console's side of it.

## Two tabs

| Tab          | For                                                                                                          | Tiers                                       |
| ------------ | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------- |
| **Keychain** | One setup for every install: the home, its members, adding sites, what it carries                            | Enterprise, Strategic                       |
| **Installs** | The installs on the licence: add one (ask to join, vouch with six digits), take one off, the install history | Every tier whose licence names its installs |

The arrow keys switch tabs; the choice is remembered.

## What each state shows

| This install is   | The page shows                                                                                                                                                                                                                                                                                                                                             |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Not on a Keychain | A map of the idea, then **1 · Start a Keychain here** (make this the home) and **2 · Join a Keychain** (site key, pair, sealed file); a fold to seal this install's setup for an offline site                                                                                                                                                              |
| The home          | The ring: a map of the home and its members, each dot by health; *N keys on the ring · your licence allows 10 installs*; what it carries; **Members** (rename, make it the home, remove); **Add a site** (a new host, an install already running, no network between them, each in numbered steps); **What it carries** (a switch per part); **Site keys** |
| A member          | Where its setup comes from and when it last synced; *If the home is gone* after 15 minutes of silence (owners can take over); **Each part** (keep my own, take the Keychain's); **The ring** as the home last told it; **Move to another home**                                                                                                            |

## Help on every term

A **?** beside each term (home, member, site key, pairing, sealed file, joining the licence, keeping its own, the ring)
explains it in a sentence or two; Tab reaches it, Enter opens it, Escape closes it. **How it works** (top right) opens
the whole story in a side panel: how it goes, three ways in, changing the home, when an install is lost, what it
carries and never carries, how it's kept safe, who can change it.

## Who can use it

Everyone signed in sees it. Owners and admins change it; viewers and responders see *You can view the Keychain. Owners
and admins change it.* Taking over as the home is for owners only. The server enforces all of it.