Clearer system health on the console home

After you pick a project, the console drops you on the home dashboard. That page has to answer one question quickly: is authentication working in this environment, and what still needs configuration. The home board now makes system health and operational readiness readable as gauges instead of a pile of widgets you have to decode.

This is the longer note behind the August 14 changelog entry.

What you see

Home is /dashboard/home. Everything on it is scoped to the selected environment and the time range in the top bar (default last 24 hours).

Readiness is a composite score: a percentage, a segmented bar of passing versus needs-attention checks, and a last-sync stamp. Under it:

• Session health — live sessions, failed sign-ins, and Lidar Signals
• Policy coverage — whether Password, MFA, and Geo policies are configured

System Health & Risk is three circular gauges from the same readiness telemetry:

• Uptime — sign-in success rate over the readiness window
• Risk Score — LOW / MED / HIGH from session health, Lidar signals, and policy gaps
• Latency — round-trip time of the last readiness query

The rest of the board is unchanged in role: Insights counters, Growth, event log (with Hide synthetic), providers, locations, and resource tiles.

How to use it

1. Select a project. You land on Dashboard.
2. Set the top-bar time range if you are not looking at the last day.
3. Read Readiness first. Amber segments mean a capability exists but is not enforced.
4. Open Authentication > Policies for Password and Countries, or Authentication > Features for MFA, when a coverage tile is incomplete.
5. Use the event log's View all activity to jump to Audit with the same time range.

Readiness is a configuration checklist, not a penetration test. A green bar means the named checks passed, not that every policy is tuned.

Trust boundaries

Gauges are derived from environment telemetry the console already has. They are not an SLA contract and not a promise about a regional edge.

Risk Score folds in Lidar Signals when Lidar is available. A locked Lidar feature means that input is missing; it does not mean there are no threats.

Do not treat Uptime as "the identity service never failed." It is sign-in success rate in the selected window. Failed attempts, bot blocks, and user typos all move that number.

Widgets can be rearranged. Layout is personal; the underlying checks stay environment-scoped.

Try it

Open Dashboard after selecting a project and compare Readiness plus the three gauges against Authentication > Policies. The home board is documented in Dashboard. The original release note is in the changelog.