> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/discovering/dashboard.md).

# The Dashboard

The Dashboard is the Seal UI's landing page after sign-in. It aggregates the state of every Seal Project in your tenant into a small set of summary tiles and charts, refreshed once a day. There is no per-project filter on the Dashboard itself; for project-level detail, use the [Protection page](/discovering/protection-page.md).

<figure><img src="/files/JidOD4wpKmky3T4NBojd" alt="The Seal Dashboard with nine widgets covering vulnerable packages, sealed packages, available fixes, time savings, total projects, vulnerable packages over time, most critical vulnerable packages, and most vulnerable projects"><figcaption><p>The Dashboard</p></figcaption></figure>

## What's on the Dashboard

| Widget                                | What it shows                                                                                                     |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Vulnerable packages**               | Donut chart of vulnerable packages broken down by severity (critical, high, medium, low).                         |
| **Sealed packages**                   | Donut chart of sealed packages broken down by severity.                                                           |
| **Available fixes**                   | Count of vulnerable packages that have a sealed version available but have not been replaced yet.                 |
| **Estimated time saved**              | Engineering hours saved by sealed packages already deployed.                                                      |
| **Predicted time savings**            | Engineering hours that would be saved if every available fix were applied.                                        |
| **Total number of projects**          | Count of active Seal Projects in the tenant. Archived projects are excluded.                                      |
| **Vulnerable packages over time**     | Line chart of vulnerable-package counts by severity, with a range selector for the last quarter or the last year. |
| **Most critical vulnerable packages** | Top vulnerable packages ranked by maximum CVSS score. Columns: package, version, project, vulnerabilities.        |
| **Most vulnerable projects**          | Top 5 Seal Projects ranked by vulnerability severity. Columns: project, owner, vulnerabilities, last seen.        |

## How the numbers are computed

The Dashboard is **tenant-wide aggregate**. Every Seal Project's data is rolled up into the metrics. To break the same numbers down by Seal Project, by package manager, or by team, generate a report from the [Reports Manager](/using-platform/reports-manager.md).

The metrics are **recomputed once a day** by a scheduled job, not in real time. Activity that lands after the most recent recompute does not appear on the Dashboard until the next run.

Rows hidden on the Protection page are excluded from every Dashboard widget by default.

## Empty states

* **Brand-new tenant, before any scans land.** The Dashboard displays a Welcome view with onboarding suggestions in place of the metric tiles. Once scans complete and the tenant transitions out of the onboarding state, the metric tiles take over.
* **Vulnerable packages over time, with insufficient history.** The line chart needs at least two data points to render. While the platform is still accumulating points, the chart shows "Not enough data yet."
* **Top tables, with no findings.** The Most critical vulnerable packages and Most vulnerable projects tables show empty-state messages when there are no findings to rank.

## Relationship to the ROI report

The Dashboard's **Estimated time saved** and **Predicted time savings** tiles show the headline numbers from the same model as the **ROI report** in the Reports Manager. The two views differ in shape:

* The Dashboard is a single read-only view of tenant-wide aggregates.
* The ROI report can be filtered by Seal Project and by package manager, and exported as CSV or PDF.

For executive snapshots and the at-a-glance posture, the Dashboard is the right view. For finer-grained reporting, generate an ROI report. See [Reports Manager](/using-platform/reports-manager.md) for the full set of report types.

## Permissions

Every authenticated user in the tenant sees the Dashboard, regardless of role. The data shown is the same for all roles.

## Related

* [The Protection page](/discovering/protection-page.md): per-Seal-Project detail for the same data.
* [Reports Manager](/using-platform/reports-manager.md): the ROI report and other report types.
* [If you're a security leader](/introduction/audience-guides/security-leader.md): how a security leader uses the Dashboard.