The Reports page gives you visibility into how Vega is being used across your workflows and whether everything is operating as expected.

At a high level, it answers four questions:

This page is primarily designed for user with Admin permissions.

Users with Admin permissions have access to the “All users” filter, which they can toggle on to view activity across the entire firm, as well as a filter to select specific users and monitor their usage.

Users with standard permissions can still access the Reports page, but the data is limited to their own account.

The Usages tab shows how Vega is being used over a selected time range.

By default:

You can adjust this range at any time.

Usage is broken down across:

Next to each metric, you’ll see a percentage.

This represents the comparison to the prior period (for example, the previous month), helping you understand whether usage is increasing or decreasing over time.

The Integrations tab shows the status of your connected systems.

Each integration is represented with a status indicator:

If an integration is broken, the expected fix is to:

The Compliance tab is where your firm’s automated review of client communication lives.

It covers two types of communication:

Both are assigned the same risk levels: None, Low, Medium, High, and Critical.

This analysis is based on whether the content aligns with regulatory expectations (for example, SEC-related considerations for US-based advisors).

The tab is built around a simple idea: the report should not just count risks, it should help you work through them.

Four figures summarize the selected period:

Below them, the Risk overview shows the distribution of every review in the period as a single bar, with a legend naming each segment and its count.

The Review queue is the working surface of the report. It lists the individual reviews rather than aggregating them, sorted by risk level first and then by recency, so the most serious and most recent items sit at the top.

Each row shows the advisor, the risk level, the current status, and when the review was generated. Click any row to open it.

Two filters sit above the queue:

The queue opens pre-filtered to the outstanding work, showing Open reviews rated High or Critical, so the first thing you see is what still needs attention rather than everything Vega has ever reviewed.

The queue heading always reports how many reviews match your current filters. The queue shows the first ten by default, with the option to show all.

Opening a review shows the full detail:

Reviewing communications is only half the job. The other half is keeping track of what you have already dealt with, so that a flagged email you looked at last Tuesday does not sit there next week looking exactly as urgent as it did the first time.

That is what the status on each review is for. Every review is one of:

The distinction between Addressed and Dismissed matters more than it might seem. Both mean a human has reviewed the item, and both remove it from your open queue. But they record two different conclusions. Addressed says something was done. Dismissed says the flag did not warrant anything, which is a perfectly normal outcome for automated review and worth being able to say explicitly.

Being able to tell the two apart later is what turns the report into a record of your process rather than just a list of alerts.

The status appears as a pill next to the risk level when you open a review, and you can change it right there. Vega records who changed it and when, shown underneath as “Status updated [date] by [name]”. The change takes effect immediately across the whole report, so the queue, the figures at the top, and the review itself stay in sync without a reload.

Only users with Admin permissions can change a status.

Advisors can still open their own reviews and see the status, they simply cannot change it. Clearing a flag raised on your own communication would be a self-review, so that decision is reserved for firm admins.

The status reads identically either way, so everyone is looking at the same information.

Marking a review as Addressed or Dismissed does not delete it or hide it permanently. Switch the status filter to Addressed, Dismissed, or All statuses and it is right there, with its full history intact.

It also does not change anything about the communication itself. The email was still sent and the meeting still happened. The status records what your firm decided to do about it.

The two figures to watch are Open elevated and Open high priority. Those are the counts that should be trending toward zero.

Below the queue, the By advisor table gives the aggregate view: one row per advisor, one column per risk level, with the number of reviews in each. The columns are sortable, so you can order the firm by Critical or High to see where attention is needed.

Clicking a number opens those specific reviews. If there is only one, it opens directly.

For higher-risk categories (High and Critical), Vega can also send compliance reports by email to designated contacts.

These reports include:

Vega also runs a compliance review on every Client deliverable it generates. Those reviews stay on the deliverable itself rather than appearing in this tab, for the reasons explained in Deliverable compliance review.

The Tasks tab provides a structured view of task activity over a selected time range.

This view is designed to work best for teams using Vega as their task management system, but it also supports third-party CRM-based task data.

The report includes:

It also includes performance metrics:

Book signals take what Meeting analytics (read our article: Meeting analytics) finds inside each individual conversation and rolls it up across your whole firm, so you can see patterns instead of reading meetings one at a time.

You will find your Book signals from the Meetings tab of the Reports page.

Set a date range, report on all users or a single advisor, and narrow to specific meeting types.

Three figures summarize the period:

Below them you will find:

A simple way to approach it:

For users with Admin permissions, this becomes a firm-level dashboard.

For individual users, it becomes a way to stay aware of their own activity and workflows.