Dashboard

Dashboard is the Fleet overview. It answers: what is loaded, what has fresh signal, and what needs attention?

If you are unsure where to go next, start with Dashboard, then follow How Thalovant Works.

Use Dashboard as a starting point, not as the place to fix every issue. It points you to the page that owns the next action.

Use Dashboard as the daily starting point for fleet signal: header metrics, snapshot cards, client activity, attention, and updates.

Start Here If

• you just signed in and need the Fleet overview;
• a hub, client, permission set, live signal, or update needs attention;
• you need to decide whether the next page is Hubs, Clients, Permissions, Live Map, Analytics, Billing, or Help;
• you want to confirm the setup still tells one clear story.

At a Glance

Dashboard signal	First page to open
Locked action or plan warning	Billing
Missing or stale client	Live Map, then Clients
Access warning	Permissions
Skill, runtime, or hub update	Manage Updates
Activity spike or demand question	Analytics
Broad service issue	the status page

Main Panels

Header metrics

Shows loaded hubs, clients, policies, live telemetry, log coverage, and public domains.

Live fleet load

Shows fresh load only when telemetry is current enough to trust.

Needs attention

Collects hubs or clients with missing, stale, or warning updates.

Fleet snapshot

Shows loaded hubs, client identities, policy coverage, and the current activity window.

Client activity

Summarizes connection churn, utterances, messages, and top active hubs or clients.

Available updates

Highlights skill, runtime, and hub releases when updates are available.

Header Metrics

The top of Dashboard summarizes counts such as hubs, clients, policies, live telemetry, log coverage, and public domains. Treat these as a quick pulse, then open the matching page for details.

Reading Dashboard in Order

For a clean review, move through Dashboard in this order:

1. Header metrics: confirm hubs, clients, policies, and live signal match what you expect.
2. Live load: trust live panels only when telemetry and log coverage are fresh.
3. Fleet snapshot: compare loaded hubs, client identities, policy coverage, and activity window.
4. Attention items: open stale, missing, warning, runtime, or permission-related items.
5. Client activity: use activity mix and top entities before opening Analytics for deeper demand questions.
6. Updates: open Manage Updates when the workspace is ready for skill, runtime, or hub changes.

When Data Is Partial

Sometimes Dashboard can show normal inventory while live status is unavailable. That does not always mean something is broken. Open the related hub, client, Live Map, or Analytics detail to see whether the issue is a missing update, a stale update, incomplete telemetry, or a real warning.

Good Dashboard Habits

• Start here after signing in.
• Use Billing before creating hubs or clients when a plan gate appears.
• Open attention items before changing healthy items.
• Open Analytics when the question is about volume, geography, time windows, or top signals.
• Use Manage Updates when you are ready to apply newer skill, runtime, or hub releases.
• Use Live Map when the issue is about whether a client is connected.

Dashboard Looks Right When

Dashboard looks right when:

• hub, client, and policy counts match what you created;
• telemetry and log coverage are fresh enough for the question;
• Fleet snapshot cards route to the expected owner pages;
• attention items are understood or cleared;
• update prompts are intentional;
• Live Map and Analytics tell the same story for connection and usage health.