Management dashboard

The management dashboard adds up what happened across your Workspaces and shows it as a handful of figures. It is in the account menu: Account → Dashboard.

It is a screen to read, not to operate. Nothing here changes a domain. The only things you set on it are two email preferences, at the bottom.

The account Owner can always open it. A Operator or a Viewer opens it if their role includes dashboards, and sees only the Workspaces assigned to them.

• See the portfolio without opening each client. One screen answers how many alerts there were, how fast the critical ones were closed and how the domains score.
• Put a number on the work. Reports generated, protected improvements and an estimate of the hours they represent.
• Know which clients are looking. How many client contacts opened what you send them, and which Workspaces have gone quiet.
• Spot the client that takes the most effort. A ranking of Workspaces by operational load per domain.
• Get it by email. A summary of the account sent every month or every quarter, also to people who have no user.

• Everything is calculated when you open the screen. Nothing is stored from one visit to the next; press Reload to calculate it again.
• Most figures cover a period that ends now. You choose Last 30 days or Last 90 days. They are rolling days counted back from this moment, not calendar months.
• Some figures ignore the period. The portfolio health block shows the state of the domains today. The inactive clients figure always uses 30 days.
• You see what your role reaches. The Owner, and members with access to every Workspace, see the whole account. Everyone else sees figures calculated only over their assigned Workspaces, and a notice says how many those are.
• Alerts come from continuous stabilization only. An alert counts if it was raised in the period on a domain with Continuous stabilization, even if it was turned off on that domain later.
• Scores come from two sources, never mixed. One is the score that continuous stabilization keeps up to date; the other is the score of the last static analysis of the domain. Each is shown separately, with the number of domains it covers.
• The hours saved are an estimate. Each report, each protected improvement and each alert is multiplied by a fixed number of hours. It is not a measurement of your team's time.

At the top, next to the title, is the Reload button. Below it, the period selector: Last 30 days or Last 90 days. Then come five blocks of figures and three panels.

Protection metrics

• Alerts detected. Every alert that continuous stabilization raised in the period, of any severity.
• Critical alerts resolved within 24 h. Of the critical alerts raised in the period, those marked resolved no more than 24 hours after they were raised. It measures how fast the response was, not whether the problem had an effect.
• Critical alerts open or resolved after 24 h. The rest of the critical alerts of the period: those still open and those resolved after more than 24 hours. It is green at zero and amber otherwise.

Productivity metrics

• Estimated hours saved, with the Estimate mark. The sum of three parts, shown under the figure: hours for reports, hours for protected improvements and hours for alerts.
• Reports generated. PDF reports that finished generating in the period, in your Workspaces.
• Protected improvements. Improvements that continuous stabilization recorded as protected in the history of your domains during the period.

End-client stickiness

• Contacts who opened this period. Two numbers: client contacts with some recorded access in the period, out of all your active client contacts. An access is recorded when a contact enters their portal, opens a domain or a report there, or opens an email whose opening is tracked. Below, the same as a percentage. The figure is green from 70%, amber from 40% and red below that.
• Inactive Workspaces (30+ days). Workspaces where no client contact has been seen in the last 30 days, or ever. A Workspace with no active contact counts here too. When there are any, they are listed below with the days since the last visit, the longest first. The list, and therefore the figure, stops at ten.

Aggregate portfolio health

Two rows, one per source. The title of each row says how many of your domains have a score from that source.

• The row for continuous stabilization uses the latest score of each domain that has it turned on.
• The row for static analysis uses the score of the last static analysis of each domain.

Each row splits the domains into four figures: three score bands, labelled with their limits (green is the highest band, red the lowest), and No score yet for the domains that have no score from that source.

Under the rows, a notice names the domain with the lowest score, its Workspace, the score and its date. It takes the lowest score from continuous stabilization; if no domain has one, the lowest from static analysis. The notice turns amber when that score falls in the red band.

Evolution

Three figures. Each shows the current value, an arrow with the difference when there is one, and the value it is compared with.

• Average score · Continuous stabilization. The average of the latest score of the domains under continuous stabilization. It is compared with the average of the last score those domains had before the period started.
• Average score · static analysis. The average of the last static analysis of your domains. It is compared with the average of the first analysis of the domains that had already been analyzed before the period started. So this one tells you how far the domains have come since you added them, not what changed in the period.
• Stickiness rate. The percentage of active contacts with an access in the period, compared with the same percentage for the period of equal length just before it.

A dash means there is nothing to average yet.

Executive digest by email

The preferences of the summary sent by email. This panel appears only if your role can manage the account. See Management dashboard.

Usage intensity by workspace

A table with one row per Workspace, ordered from the highest score to the lowest. It has its own selector for 30 or 90 days, independent of the one at the top.

• Workspace. The name and the number of domains.
• Score. Protected improvements, alerts raised and reports of the period, each multiplied by its weight, added up and divided by the number of domains. A higher score means more operational load per domain. The weights in use are written under the table. The score is grey at zero, then blue, amber from 5 and red from 10.
• Continuous stabilization. Domains of the Workspace that are under continuous stabilization right now.
• Protected. Protected improvements in the period.
• Alerts. Alerts raised in the period and, in parentheses, alerts resolved in the period.
• Reports. Files generated in the period, of any format. That is why this number can be higher than the PDF count in the block above.
• Events. Entries added to the history of the domains of that Workspace in the period.
• Last activity. How long ago the latest entry in that history was made, with no period limit.

Notification model

• Monthly workspace digest. One row per Workspace of the account, with a switch for its monthly email.
• Who receives what. A list, read only, of the notifications the account sends, grouped by who receives them. Each one says its channel and where it is configured: Always on, Account-level, Per-workspace or Per-contact.

• Account overview
• Workspaces
• Clients
• Team