Triage That Scans, and an Admin Area That Keeps You In It ​

August 24, 2026 · InfraScout Team

Structural work across the dashboard and the admin area, mostly in service of one goal: making a screen answer the question it exists to answer on the first look.

The summary counts your whole queue ​

The dashboard hero summarized as "10 critical findings · 11 sessions running" — critical findings only.

On a tenant whose backlog is mostly high-severity rather than critical, which is most tenants most of the time, that understated the queue at exactly the moment you were deciding whether to look at it. It now reads "10 critical and 3 high findings · 11 sessions running", tone-colored, counting up on load and on refresh.

Needs attention now is a table ​

The triage list is now a proper table with fixed columns — severity, title, key, host and age — so the same field lands in the same place on every row and the list scans rather than merely being present. Below a tablet width it collapses to three columns, and long relative timestamps truncate with the full value on hover instead of overflowing their column.

The category and top-host bars moved onto a real progress primitive rather than hand-built markup, and the agent fleet panel became a proportional strip: the shape of the fleet across online, stale, offline and pending reads at a glance instead of as four numbers to compare.

KPI cards hold their value ​

A KPI card showed a placeholder block while loading, and a background refresh re-triggered it — so a card sitting at 47 dropped to a placeholder and climbed back every time the dashboard refreshed itself, which it does whenever anything changes.

A card now holds the number it has and counts from the old value to the new one, with the placeholder reserved for a genuine first load. A card whose value is not a number — a health state, a duration — shows a dash rather than a 0 that would read as a measurement.

One heading per admin page ​

Every nested admin page drew its own heading inside the section heading, itself inside a card — so a page stacked two titles and three borders before any data. Twenty-six views lost the duplicate. Titles, descriptions, icons and actions are unchanged; only the container went.

Clicking a section name in the admin menu now navigates to that section's first page. Previously the name was not a link — hovering opened its panel and a click had nowhere to go, which reads as a dead control rather than a menu.

Auditing a session keeps you in the admin area ​

Two related improvements for anyone using the admin area to review someone else's work.

The executions tab now shows the whole session. An administrator inspecting a session run by another user was seeing an execution list scoped to themselves, beneath a tab badge counting every execution in the session — so the badge and the list could disagree, and the list could be empty under a badge of 27. The list now reads the whole session for an administrator and the two agree. Non-administrators still see only their own executions, where the badge can still over-count; that is unchanged and documented on the page.

And opening a session keeps the admin navigation. Following a child session from an admin session group used to drop you into the user navigation bar mid-audit, because sessions had no admin route to land on. They do now, and back-navigation follows the route you arrived by.

Two smaller clarifications ​

The footer names your tenant rather than printing a bare identifier — which answered "which tenant am I looking at?" only for someone who had memorized the GUID, and is a genuine hazard if you work across several tenants with two portal tabs open.

And the licensed-systems notice states its denominator: "70/50 licensed systems in use". Without that word it scanned as an inventory tally rather than as the ceiling it is warning you about.

See Dashboard and Admin Overview.

Questions or feedback? Reach us at info@infrascout.cloud.