Operations
Shows which capabilities are installed in this Tenant, which are installing or stuck, and the status of platform components that also affect this Tenant.
For: Operator, Tenant administrator
What's on this screen
- Figures at the top: installed, installing, failed and not-started installs; if you have permission, the number of workspaces. The notice above them says the numbers are this Tenant's only.
- This tenant's installs: failed ones first, then those in progress.
- Platform components — not tenant-specific: the health status of the platform as a whole.
- Incidents: an explanation only. Incident records do not carry which Tenant they belong to, so they are not listed here.
Install statuses
| Label | What it means |
|---|---|
| installed | The capability is active in this Tenant. |
| installing | The steps are running. How long it has been running is not shown, because it cannot be read from the records. |
| install failed | Shows the step where it stopped, the error code and the steps that never ran because of it. |
| requested, not started | The request is recorded, but the install was never started. Starting it is done on the Capabilities screen. |
What the screen does not tell you
- It does not show record volume; the module that holds records offers no Tenant-wide count, and no estimate is shown.
- None of the component rows says ‘this happened in this Tenant’. A component with no live check shows as unknown; checks are started by the platform operator.
Tip The console must be in a Tenant scope. Viewing requires operations.read in this Tenant, the install list requires capability.read, and the workspace count requires workspace.read. Nothing is changed on this screen.