Account overview

The overview is the first thing you see when you enter the console. It sums up the whole account: how many domains need attention, how each Workspace is doing and what changed lately. It is in the account menu: Account → Overview.

It is a screen for reading and jumping. Nothing is edited here: every row takes you to the Workspace or the domain where the work is done.

The account Owner can always open it. Other roles can, if their role includes dashboards.

• Know where the fire is. One line tells you how many domains lost something that was protected, how many are worth a look and how many have a pending verification.
• Compare Workspaces at a glance. Each one has its card with the same reading, and the one with the most urgent problems comes first.
• Go straight to the problem. From an alert or an event you land on the domain, in the right section.
• See what happened without asking. The events of the last day and the activity of the last month are listed with their domain and their Workspace.

• Every domain falls into up to three counters. On fire: it has an open regression, meaning something that was protected was lost. To review: a domain under continuous stabilization with medium or high risk, or a domain without it whose static analysis scored low, is old or was never run. In maintenance: its domain verification is pending or has expired. Maintenance is counted apart, so a domain can be in it and in one of the other two.
• There are two scores, and they are never mixed. The continuous stabilization score is the overall score of the latest measurement of the domains that have it turned on: the state of now. Static is the score of the latest static analysis of each domain: a snapshot of the day it was run.
• Each average says how many domains it covers. It reads as the average, then how many domains have that score out of the total. A dash means no domain has it.
• The same reading is used at every level. The account, each Workspace and each client show the same three counters and the same two averages.
• Alerts come only from domains under continuous stabilization. A domain without it shows up through its static analysis, never in the alert blocks.
• Blocks with nothing to say are not shown. A day with no events has no events block.

When the account has no domains yet, the screen shows a getting-started panel instead; see the task below. With domains, it is a column of blocks.

• Account Overview. The header, with the number of Workspaces, the number of domains and, if there are any, the number of domains with continuous stabilization.
• Account status. The three counters of the whole account in one line, which turns red when a domain is on fire. Below, the two averages, the continuous stabilization one and Static, each with a question mark that explains it when you hover over it.
• The Workspace cards. One per Workspace: its three counters, its two averages, how many domains it has and how many have continuous stabilization. The first four are shown; View all shows the rest. Inside each card, the section Continuous stabilization lists its domains that have it turned on, each with its score, when it was last measured and a mark: Open regression, or its risk level. A domain turned on and waiting for its first measurement says Active, not measured yet. At the bottom, the link Show domain detail results opens the Workspace.
• Active alerts. One row per Workspace with the number of problems found in its domains under continuous stabilization. Press a row to unfold its domains and the alerts of each one.
• Latent risk. The alerts that are still open, up to fifteen, with their Workspace, severity and age. One that was fixed and broke again carries a mark with the number of times, and goes first. One that was already acknowledged is marked Acknowledged.
• Clients. One row per client: Status, Workspaces, Domains, Portfolio with its counters and averages, and Renewal. A client whose renewal is within thirty days is highlighted and goes first. The renewal date is shown only if your role includes the commercial data of clients.
• Hot today. What happened in the last twenty-four hours, up to ten events: new alerts, alerts that came back, alerts resolved, and the milestones of continuous stabilization, such as turning it on or an improvement being protected. The most serious go first.
• Recent Activity. The last twenty events of the last thirty days, grouped by day: static analyses run and changes in continuous stabilization.

• Workspaces
• Clients
• Management dashboard
• Billing