Skip to content

Wall

Wall is the ambient fleet display for Colony Cloud. It has two entry points depending on how you want to use it.

Entry pointRouteWhen to use
In-shell view/operations/fleet?view=wallPreviewing the wall inside the normal dashboard UI
Standalone kiosk/wallCasting to an office screen, TV, or a second monitor for passive fleet monitoring

Route: /operations/fleet?view=wall

The in-shell view renders the same wall display inside the normal dashboard navigation (sidebar and header). This is where you go to preview the wall or orient yourself before putting it on a shared display.

An Enter wall mode button in the page header opens the standalone kiosk at /wall in the same browser tab, entering fullscreen automatically.

Route: /wall

The kiosk is a full-screen, chrome-free view intended for a shared office display or TV. It is rendered outside the normal dashboard navigation — no sidebar, no header.

When the kiosk loads, it automatically requests browser fullscreen. If the browser blocks the request (for example, because it was not triggered by a direct user gesture), the page continues to render normally without fullscreen.

To exit the kiosk, press Escape or exit browser fullscreen by any other means. Either action navigates back to /operations/fleet?view=wall in the in-shell view, keeping the period and tenant parameters.

The in-shell view (/operations/fleet?view=wall) gets live updates over the dashboard’s streaming connection. The standalone kiosk (/wall) has no streaming connection, so it always refreshes pipeline state by polling every 15 seconds.

If pipeline data is older than two refresh intervals (30 seconds on the kiosk), the header label reads THE HIVE · STALE instead of THE HIVE · LIVE. See Staleness indicator.

The wall display is composed of the header, the open report’s statements and the status distribution. The header carries a live clock, the tenant name and the staleness indicator.

The nine sentences of the current period’s open report, from bands A and B. They are the same sentences the Reporting home shows. They are fleet-wide: the repo filter does not apply to them.

Every in-progress item is a hexagon, grouped by status:

StatusMeaning
FlowingWork is moving through its workflow.
Awaiting youThe item needs a decision or action from you.
Awaiting externalThe item is blocked on something it will recover from without you, such as another issue it depends on.
ParkedThe item is paused and not expected to move on its own.

Each item’s status comes from its own workflow, so content and code workflows are counted alike. Completed items are excluded.

Hexagon heat shows time in state: the longer an item has stayed in its current state, the warmer its hexagon. A stuck ring appears around an item at 12h.

The wall reads two parameters from its URL.

ParameterValuesBehavior
?periodday, week or monthPicks the report period. Defaults to week and is written into the URL.
?tenant<org id>Selects that tenant when it is one of yours. Otherwise the current selection is used and written back.

Bookmark the URL to pin a room’s screen to a period and a tenant. Both parameters survive Enter wall mode and leaving the kiosk.

Once pipeline data is older than two refresh intervals (30 seconds on the kiosk, or 2 minutes in the in-shell view while its stream is connected), the header label reads THE HIVE · STALE instead of THE HIVE · LIVE. The heartbeat dot beside it stops pulsing and changes color. Nothing else on the Wall changes.

The check runs every 5 seconds, so on the kiosk the indicator can appear up to about 35 seconds after the last successful refresh. This can happen when the kiosk loses network connectivity or when a refresh is slow to respond. The label returns to THE HIVE · LIVE once a refresh succeeds.

Both Wall and Floor show live fleet activity, but they are designed for different contexts.

FloorWall
Route/operations/fleet?view=floor/operations/fleet?view=wall (in-shell) or /wall (kiosk)
Intended useInteractive per-Worker monitoringPassive ambient display on a shared screen
Navigation chromeInside the normal dashboard navigation (sidebar and header)Kiosk: none; in-shell: inside the normal dashboard navigation
Data connectionHTTP poll every 30 s, or every 60 s with SSE worker-status updates connectedIn-shell: live streaming updates; kiosk: always 15 s poll
InteractionPer-Worker tableRead-only display, no click targets

Use Floor when you are actively monitoring Workers. Use Wall when you want a persistent, no-interaction overview on a dedicated screen.

For the full tour of dashboards and monitoring surfaces, see Dashboards and Floor. To track an individual issue, use the Ledger.