Documentation

Appearance

Dashboards and displays ​

Dashboards combine organisation or network data sources with layouts and widgets. Use them for internal operational views such as fleet health, customer support context, or rollout progress.

Build a dashboard ​

  1. Define the data sources required by the view.
  2. Create a dashboard layout.
  3. Add the smallest set of widgets that answers one audience's questions.
  4. Configure variables and scope so a customer, network, or class selection cannot leak unrelated data.
  5. Preview with a read-only user and with missing or stale data.
  6. Publish only after checking units, time windows, and empty states.

A chart is not an alert. Add a monitor and response route for conditions that require action.

Troubleshoot data ​

  • Stale widget: inspect the source refresh time before changing the layout.
  • Empty widget: verify source scope, variable value, permission, and retained data window.
  • Different totals: compare time window, class, network, tag, and customer filters.
  • Hidden edit controls: check dashboard-write access and effective organisation role.

Pair a shared display ​

Dashboard displays support a paired TV or wallboard view.

  1. Create a display and select its content.
  2. Open the pairing view on the physical screen.
  3. Enter the short-lived pairing information in the management surface.
  4. Verify the screen shows only intended data.
  5. Revoke pairing when the screen is moved, replaced, or no longer trusted.

Treat a paired screen as a shared credential. Position it to avoid exposing customer, security, or personal data. Test fallback behaviour and network recovery before using it in a response centre.

Status pages and customer surfaces ​

Use a public status page for selected service and incident communication. Use a whitelabel customer portal, hosted documentation site, or support inbox only when the corresponding module is enabled for the organisation. These surfaces have separate access and publication boundaries from dashboards.