Customizable Dashboards (Pro)
Note: Customizable Dashboards (layouts, widgets, and the widget catalog) are a DefectDojo Pro feature. They are off by default โ a superuser can turn them on from Settings > Feature Flags on both Cloud and On-Premise instances.
DefectDojo Pro Customizable Dashboards let each user assemble their own dashboards out of widgets (counts, charts, leaderboards, feeds, and notes) arranged on a drag-and-drop grid. Instead of a single fixed dashboard for everyone, you build the layouts that matter to you: an executive overview, a triage queue, a remediation-velocity board, a scanner-effectiveness view. You can keep layouts private, share them with Groups, publish them to everyone, set one as the default that opens on the Dashboards page, and clone any layout (yours or a shared template) as a starting point. The home page itself is the Command Center, which every user has and which links to these grids.

How it compares to open source
Open source DefectDojo has a single, built-in Main Dashboard with a fixed set of summary cards and charts that a superuser can show or hide. It is the same for every user.
DefectDojo Pro’s home page is the Command Center, and beside it Customizable Dashboards give each user per-user customizable dashboards. You choose which widgets appear, how they are filtered, and where they sit on the grid. You can build any number of named layouts, switch between them, share them with your team, and drive the whole system from the REST API or an LLM.
๐ก Tip: In DefectDojo Pro, Assets were formerly called Products and Organizations were formerly Product Types. The UI uses the new wording, but some underlying widget settings still use the legacy names โ for example, most widgets take a
modeloffinding,product,engagement, ortest. Where this matters, it is called out below.
Enabling Customizable Dashboards
Customizable Dashboards are off by default. A superuser can turn them on from Settings > Feature Flags, on both Cloud and On-Premise instances. See Feature Flags.
Once it is enabled, Dashboards appears in the sidebar under Home (the Command Center), opens your customizable dashboards, and the Dashboards REST API becomes available.
๐ Important: While the feature is off, that sidebar entry reads Dashboard and opens the classic tile dashboard instead, and every
/api/v2/dashboards/endpoint other than the Command Center’s own returns403 Dashboards 2.0 is not enabled.Home is the Command Center either way. Turning it on does not change anyone’s data access: every widget still respects DefectDojo’s role-based access control, so each user only ever sees the Findings, Assets, and other records they are authorized to view.
Core concepts
A customizable dashboard is built from a few simple pieces.
Layouts
A layout is one named dashboard: a collection of widgets and their positions on the grid. Each layout belongs to you, and you can have as many as you like โ for example a “Daily Triage” board and a separate “Exec Overview.” A layout stores three things:
- widgets โ the ordered list of widgets it contains, each with its own type, title, and configuration.
- layout โ where each widget sits and how big it is on the grid.
- settings โ layout-level display options.
The first time you open Customizable Dashboards, DefectDojo gives you a personal copy of the Default Dashboard starter so you are never staring at a blank page.
Widgets
A widget is a single panel on the dashboard. Every widget is an instance of a type from the catalog (a Count, a Graph, a Top-N leaderboard, and so on), and carries its own configuration: which data model it reads (finding, product, engagement, or test), what filters scope it, and type-specific display options like chart type, colors, or grouping. Two widgets of the same type with different filters are completely independent.
Each widget also has an optional auto-refresh interval (off, 30 seconds, 1 minute, 5 minutes, or 15 minutes) and an editable title. A widget’s title bar has a refresh button, and on a wide enough tile the time its numbers were last updated beside it; on a small tile the refresh button’s tooltip carries that time. Markdown, Section Break, Quick Actions and Favorites read nothing that changes, so they show neither.
The widget catalog
The catalog is the fixed menu of widget types the platform supports, grouped into four categories โ Numbers, Charts, Lists & Feeds, and Static & Utility. When you add a widget, you pick its type from the catalog. The catalog is also available over the API so scripts and LLMs can discover the available widget types and a known-good starting configuration for each. See The widget catalog below for the full list.
The grid
Widgets are placed on a 12-column grid. In edit mode you drag widgets to move them and drag the bottom-right corner to resize them; the grid compacts upward to fill gaps. Each widget type has sensible minimum and maximum sizes so charts and tables stay legible. A newly added list widget (SLA Burndown, Recent Activity, Top N and the like) is sized to show every row it is set to show; a taller tile can show more rows by raising the widget’s row limit. Lists such as Top-N, Recent Activity and Saved Reports show the rows that fit their tile and how many more there are, and table widgets such as Team Scorecard and Root Causes drop their least important columns as the tile narrows rather than scrolling sideways.
Sharing, cloning, and defaults
- Default โ one of your layouts is your default: the one that loads when you open the Dashboards page. You can change which layout is your default at any time.
- Clone โ copy any layout (one of yours, or a shared template) into your own space as a fresh, independent starting point. Cloning gives the copy its own widgets, so editing the clone never touches the original.
- Share โ publish one of your layouts to the whole team as a shared layout. Other users can see it and clone it, but only a team Maintainer can publish, edit, or unshare a shared layout (unless it is collaborative, below). Sharing a layout shares only its design โ every viewer still sees only the data their own permissions allow.
- Share with Groups: with Group Ownership on, Share in a layout’s menu sets who can see it: Only Me (or Group for a Group’s layout), Specific Groups, or Everyone. Members of a Group you share with can open the layout and set it as their default, but they cannot change it. Everyone is the shared layout described above, and publishing to everyone (or withdrawing it) needs the Dashboard Share permission held through a Global Role.
- Group dashboards: Transfer in a layout’s menu moves it into a Group, or back to you as Only Me. A Group’s dashboard belongs to the Group rather than to the person who made it: every Member sees it in their layout picker (marked with the Group’s name), and Members whose role in the Group carries Dashboard Share change, share, transfer and delete it. Moving a dashboard into a Group needs that permission in the Group, or as a Global Role. A Group’s dashboards are counted on the Owned Content tab of the Group’s page.
- Collaborative โ a Maintainer can mark a shared layout as collaborative from Manage Layouts (Make Collaborative, reversed with Stop Collaborating). A collaborative layout is one live dashboard rather than a template to copy: it appears in every user’s layout picker, anyone can set it as their default, and anyone can add, remove, rearrange, or configure its widgets. Every change is saved to the same layout, so everyone using it sees it. Renaming, unsharing, deleting, and the collaborative setting itself stay with a Maintainer. If a layout stops being collaborative (or is unshared), users who had it as their default fall back to their own layouts. Edits are saved as they are made, so two people editing at the same moment can overwrite each other’s change; the layout re-syncs from the server when you enter edit mode.
- Read-only: a Maintainer can also mark a collaborative layout as read-only (Make Read-Only in Manage Layouts, reversed with Allow Editing). It stays one live dashboard in every user’s layout picker, and anyone can still set it as their default, but only a Maintainer or the layout’s owner can change its widgets or arrangement. Everyone sees it tagged Read-Only; the owner and Maintainers keep the Edit button and everyone else has none, so a Maintainer can keep one dashboard current for the whole team without anyone else changing it. Anyone who wants a version of their own can still duplicate it. Stopping collaboration (or unsharing) also turns read-only off.
- Starter & shared templates โ DefectDojo ships a set of curated shared templates you can clone as a head start (see Shared templates below). The Default Dashboard is the special “starter” template that new users are given automatically.
- Instance Default: a user who can share dashboards can mark a shared layout as the Instance Default from Manage Layouts (Set as Instance Default, cleared with Clear Instance Default). It carries an “Instance Default” badge, and it is the dashboard everyone is shown when dashboard customization is restricted (see below). It can also be chosen from a dropdown on Settings > Defaults > Instance Defaults (the Dashboards card).
Restricting customization
An administrator can enable Restrict Layout Customization (Settings > Defaults > Instance Defaults, the Layout Customization card) to limit dashboard changes to superusers. With Group Ownership on, everyone else switches among the dashboards approved for them instead of making their own:
- the Instance Default dashboard (or the built-in starter dashboard when none is set), which opens until they pick another,
- every dashboard shared with everyone, and
- every dashboard owned by, or shared with, a Group they belong to.
These dashboards are read-only to them, and the toolbar offers no options to create or manage layouts. The dashboard they pick opens again the next time, on any browser. A Member whose role in a Group carries Dashboard Share still changes that Group’s own dashboards, and the toolbar shows Managed by
With Group Ownership off, everyone else sees only the Instance Default (or the starter dashboard), or, under Restrict to Selected Layouts, the dashboards their Default Profile lists. A dashboard they switch to there is not remembered.
Default Profile and instance defaults
When you have not chosen a default dashboard (with Set as My Default in the layout manager, tagged My Default), the Dashboards page opens the one from the first Default Profile that sets one and that you can open (the profile assigned to you directly, then your Groups’ profiles in rank order), else the Instance Default, else your own copy of the starter dashboard. The dashboard picker marks it, as From
Building a dashboard in the UI
The dashboard toolbar
The toolbar across the top of the Dashboards page is where you switch layouts and manage them. It includes a layout picker (with badges that mark your default layout, any shared layouts/templates, collaborative layouts shared with you, and a lock on read-only layouts), and buttons to create a New Layout, open Manage Layouts, Refresh all widgets, and toggle Edit mode.

Step 1: Enter edit mode
Click Edit to unlock the dashboard. The grid becomes draggable and resizable, and an Add Widget button appears. Click Done when you are finished โ edit mode also turns off automatically when you switch layouts.

Step 2: Add a widget
In edit mode, click Add Widget to open the picker. It has three tabs:
- By Type: browse the catalog by category (Numbers, Charts, Lists & Feeds, Static & Utility). Each card shows the widget’s name and a short description. Picking one adds it to the grid and opens its configuration dialog.
- From Catalog: start from a pre-configured widget taken from one of the shared templates (for example, the “Findings by Severity” chart from the Default Dashboard). These come ready-configured, so they drop straight onto the grid.
- From Reports: start from a Chart or Widget block someone already built in the Report Builder. The widget lands configured the way that block is. This tab appears when Reporting is enabled and you can view report templates.

Step 3: Configure the widget
Each widget opens a configuration dialog tailored to its type. Common settings include:
- Title โ the heading shown on the widget.
- Model โ which records the widget reads (Finding, Asset, Engagement, or Test), where applicable.
- Filters โ an embedded list-view filter UI that scopes the widget to exactly the records you want (for example, active Critical findings). The filters you pick here are the same ones you would use on that object’s list page.
- Refresh interval โ how often the widget reloads on its own.
- Type-specific options โ for example chart type and group-by dimension for a Graph, thresholds for a Gauge, or the metric for a Top-N leaderboard.

Graph options
A Graph widget groups its records by one dimension (Group By) and can split each group by a second (Split By). Every dimension picker (the Graph, Top-N, Rate Chart, Sankey and Sunburst settings) lists its dimensions under the same headings as the chosen model’s list page uses for Add Filter, in the same order, with every date dimension under Dates, once it offers at least twelve dimensions under two or more headings (the Finding model’s dimensions do; the shorter Asset, Engagement and Test lists are one flat list). The options:
- Split By draws one line, or one run of bars, per value of a second dimension. Grouping by Created Date by month and splitting by Severity Group gives new findings per month as two lines, one for Critical and High findings and one for Medium and Low findings. Split By takes any dimension that is not a date and not the Group By, and is available on bar, line and area charts (a pie or doughnut shows one dimension). A chart draws up to 10 series: past that, the smallest values are combined into one Other series. A chart that counts unique CWEs or vulnerability IDs cannot combine values that way, so it asks for a filter or a dimension with fewer values instead.
- Severity Group is a finding dimension with three values: Critical and High, Medium and Low, and Info. It works as a Group By (a two or three slice doughnut) or as a Split By. Its lines and slices are red for Critical and High and green for Medium and Low unless you pick other colors. Clicking one opens the Findings list filtered to that group’s severities.
- PAIN Rating is a finding dimension with the FedRAMP Potential Agency Impact ratings as its values: N5 to N1, then Unrated for every finding nobody has rated, so the values add up to the chart’s total. It works as a Group By or a Split By on a Graph, and as the dimension of a Top-N Leaderboard. Clicking a value on a Graph opens the Findings list filtered to that rating. See PAIN ratings.
- Created Date is when a finding was created in DefectDojo (when it was imported or added), as opposed to Discovered Date, the date the scanner reported. Charting new findings per month by Created Date counts each finding in the month it arrived.
- Order: a chart grouped by Severity, Status, Risk or a band (Severity Group, SLA Band, Age Band, the CVSS bands, PAIN Rating) lists its values in that dimension’s own order: Critical, High, Medium, Low, Info for severity; Active first, then each way a finding is closed, for status; Urgent, Needs Action, Medium, Low for risk; N5 to N1, then Unrated, for PAIN Rating. Any other dimension (a component, an Asset, a test type) lists the biggest values first. With a limit on the number of values, the chart keeps the biggest ones and then puts them in that order. The Top-N Leaderboard always ranks by count, whatever the dimension, so its first row is the biggest. The
/api/v2/dashboards/widget_data/aggregate/endpoint returns its labels in the same order as the chart, and ranks them by count when the request sets"order": "count". - Show Values prints the number on each bar, point or slice. A pie or doughnut also shows each slice’s share of the total.
- Stacked stacks the series of a split chart on top of each other instead of drawing them side by side. It appears once Split By is set.
- Colors sets the color of each series (with Split By) or of each slice or bar (without). Default keeps the color the chart would pick, such as the severity colors.
A chart over a date (Created Date, Discovered Date, Mitigated Date and the others) shows every period between its first and last, with 0 for a month in which nothing happened, so a line never skips a gap. When the widget filters on the same date (for example Created Date in the past 180 days), the chart spans that whole window. Records with no value for the date, such as open findings on a Mitigated Date chart, are not counted, so a fixed-findings-per-month chart needs no extra Mitigated filter.
Each period is labeled by its size, in your language: a day or a week by the date it starts (May 4, 2026), a month by its month and year (May 2026), a quarter as Q2 2026 and a year as 2026. Clicking a period opens the list filtered to that period.
A management pack of three monthly charts, for example, is three Graph widgets over findings:
| Chart | Chart Type | Group By | Split By | Filters |
|---|---|---|---|---|
| Open findings by severity | Doughnut, with Show Values | Severity | Active findings | |
| New findings per month | Line, with Show Values | Created Date, by Month | Severity Group | Created Date in the past 180 days |
| Fixed findings per month | Line, with Show Values | Mitigated Date, by Month | Severity Group | Mitigated Date in the past 180 days |
๐ก Tip: A widget’s data always respects your permissions. If a shared layout includes a “My Work” widget, every viewer sees their own assignments and mentions โ not the layout author’s.
Step 4: Arrange, then save
Drag widgets to rearrange them and drag a corner to resize. Each widget’s title bar holds a Widget Actions menu (the three dots at the right end of the bar). When a tile’s title does not fit beside them, as on a small Count, the refresh button and the menu sit over the end of the title and appear when you point at the tile or tab to them, so the title has the whole bar; a title still too long to fit shows in full as its tooltip. While editing it offers Edit Widget to reconfigure the widget, Title Style to set the title’s weight and size, Duplicate Widget to copy it, and Remove Widget, which asks for confirmation. Position and size changes are saved automatically as you go. Click Done to leave edit mode.
Duplicating a tile is the fastest way to build a row of related tiles: the copy keeps the original’s type, filters, size, title style, and refresh cadence, lands in the next free space on the grid, and gets a (Copy) suffix on its title. Choose Edit Widget from its menu to rename it and change the one filter that differs.
A Section Break is the exception: its header already labels it, so a copy keeps the original’s title as it is, with no (Copy) suffix. A Section Break shows its header once: while you view the dashboard it has no title bar of its own unless its title says something other than its header. In edit mode its title bar comes back as the handle you drag it by, with its Widget Actions menu. A Section Break’s title is optional; clear the Title field in its Edit Widget form to leave it blank.
Putting a widget into a report
Customizable Dashboards and the Report Builder share one widget catalog, so a figure your team reads on a dashboard can go straight into a document you send out.
Open a widget’s Widget Actions menu and choose Add to Report. Name the block, optionally pick a report Template to append it to, and it is created carrying the widget’s current filters. The action appears on widgets a report can draw, when Reporting is enabled and you have permission to add report templates; a widget that offers nothing else shows no menu while you are viewing.
This copies the widget rather than linking to it. Editing the dashboard widget later does not change the report block, and the reverse is also true, so a shared dashboard never depends on who can see which report block.
Managing layouts
The Manage Layouts dialog (the gear button on the toolbar) is the hub for everything layout-level:
Every row’s actions are in the menu at the start of the row.
- Saved Layouts: rename, set as default, share, transfer, duplicate, or delete each layout you own. Collaborative layouts shared with you are listed here too, tagged Collaborative, and so are your Groups’ dashboards, tagged with the Group’s name. Each can be set as your default or copied into a layout of your own. A Maintainer also sees Make Collaborative / Stop Collaborating on shared layouts, and Make Read-Only / Allow Editing on collaborative ones. A read-only layout is tagged Read-Only.
- Group Dashboards: for a superuser or a holder of Dashboard Share as a Global Role, the dashboards of Groups they are not in, with the same menu. A dashboard whose Group was deleted is listed here as Unowned until it is transferred.
- Shared Templates โ browse curated and team-published layouts grouped by category, and click Use Layout to clone one into your own space.

Shared templates
DefectDojo ships ready-to-use shared templates you can clone as a starting point, among them:
| Template | Purpose |
|---|---|
| Default Dashboard | The classic home view โ 12 at-a-glance counts, severity charts, and top/bottom-graded assets. This is the starter every new user receives automatically. |
| Priority Layout | A triage-focused board built around finding priority and risk. |
| Mitigation Layout | A remediation-velocity board (closure trends, MTTR/MTTD, aging). |
| Tool Layout | A scanner-effectiveness board built around test types and recent scan activity. |
| EU CRA | The Cyber Resilience Act at a glance: the CRA row of Regulatory Scope (Assets in scope, open, past-SLA and CISA KEV findings, support-period warnings) above CRA Article 14 Deadlines. Listed only while the Regulatory Profile feature is on. See Setting Up EU CRA. |
๐ก Tip: Cloning a template makes an independent copy. Customize the clone freely โ you will not affect the template or anyone else who clones it. A collaborative layout is the exception by design: it is used live rather than copied, so edits made to it are visible to everyone. Take your own copy of a collaborative layout only when you want a private version that no longer follows the shared one. A read-only collaborative layout works the same way, except that only a Maintainer or its owner can change it.
The empty state
A brand-new layout with no widgets shows a “Build a Dashboard” prompt. Click Add Widget to jump straight into edit mode and start choosing widgets.

The widget catalog
Customizable Dashboards ship with the following widget types, organized into four categories. Most widgets read one of four models โ finding, product (Assets), engagement, or test โ and are scoped by filters you choose. The fully detailed configuration options for each widget are documented in the API guide.
Numbers
Single-glance metrics โ counts, KPIs, and gauges.
| Widget | What it shows |
|---|---|
| Count | A single number from a filtered query โ e.g. “Open Critical Findings” or “Active Engagements.” Works with finding / asset / engagement / test. For findings, the Measure option can count unique CWEs or unique vulnerability IDs instead of rows. |
| KPI / Trend | A headline number plus its change versus the prior period, with an optional sparkline. The change is red when it is bad news (more open findings) and green when it is good news; for a count with no better direction (Assets, Engagements, Tests, submitted findings) it stays gray. With the Snapshot source it can instead show a chart of open findings at the end of each month or week (see Open findings at each month end). |
| Gauge | A ratio drawn as an arc gauge โ a “universe” filter as the denominator and a “pass” filter as the numerator. Use for SLA compliance, mitigation rate, or scan coverage, with configurable warning/OK thresholds. |
| License Usage | Your account’s license-usage status with a per-signal breakdown (database size, weekly finding volume, and so on). Requires the Maintainer role. |
| Scan Coverage | What fraction of assets were scanned within 30 / 90 / 180 / 365 days, as a multi-window rollup. |
Open findings at each month end
A management pack usually reports how many findings were open at the end of each month, split by severity. A Graph widget cannot show that: it counts the findings as they are now. The KPI / Trend widget can, because its Snapshot source reads the nightly metrics snapshots, which record the open findings of every severity each night.
To chart the last six months with Critical and High as one line and Medium and Low as another:
- Enter edit mode, choose Add Widget, and pick KPI / Trend.
- Set Source to Snapshot and Show As to Chart.
- In Severities, keep Critical, High, Medium and Low (remove Info if you do not want it).
- Leave Series on Critical and High, Medium and Low, Info. Choose One Series per Severity instead to draw a line for each severity.
- Leave Period on Month and Periods Shown at 6. Week charts the end of each week instead.
- Pick Line or Bar in Chart Type, keep Show Values to print each count on its point, and change a series color if you need to (by default Critical and High is red, Medium and Low is green, and Info uses the Info severity color).
- Submit. The widget is saved as soon as you submit; click Done to leave edit mode.
How to read the chart:
- Each point is the number of findings open on the last night of that month: the month end for a closed month, and the latest night for the current one. Hover a point to see which night it was read from.
- A month with no snapshot is left as a gap rather than drawn as zero. If the snapshots stopped partway through a month, the point shows the last night that was recorded, and the tooltip names that night.
- The numbers count the findings of the Assets you can view, so two people with different access can see different numbers on the same dashboard.
- History starts with the first nightly snapshot. Until then the widget says that history arrives after it.
Charts
Time-series and distribution visualizations.
| Widget | What it shows |
|---|---|
| Graph | A general-purpose chart over any model and group-by dimension: bar, line, area, pie, or doughnut. E.g. Findings by Severity, Findings by Month. For findings, the Measure option charts unique CWEs or unique vulnerability IDs per group, such as unique CWEs by severity for one Asset. Split By draws one series per value of a second dimension, such as new findings per month by Severity Group (see Graph options). For a chart by month, filter its date with Full Months (for example Last 6 Full Months) so that every month on the chart is complete; see date filters. |
| Sankey | A flow diagram from a source dimension to a target dimension, for example Severity โ Status. Severity, status and risk values take their own colors (the severity colors for severities), and each column lists its values in their own order. |
| Sunburst | A one- or two-level radial breakdown, for example Severity, then Test Type within each severity. Severity, status and risk slices take their own colors; a slice of a dimension without colors (a test type) takes a muted shade of the slice it sits in. |
| Risk Matrix | An EPSS-probability ร risk heatmap of findings. The hue marks the zone (bottom-left green is safe, top-right red is dangerous), and each cell’s fill deepens in steps with its share of the findings in the matrix, so the cells where findings concentrate stand out. |
| Priority Histogram | The distribution of finding priority scores from the prioritization engine, auto-binned. |
| Rate by Category | A per-category ratio (numerator / denominator) โ e.g. False-Positive Rate by Tool or Mitigation Rate by Asset. |
| Finding Velocity | Findings created versus closed over time, showing whether the backlog is growing or shrinking. |
| MTTR / MTTD | Mean Time to Remediate and Mean Time to Detect, as paired time-series. |
| Vulnerability Aging | Open findings bucketed by age band (0โ30d / 30โ90d / 90โ180d / 180d+), stacked by severity. |
| Activity Heatmap | A GitHub-style calendar of daily activity over a rolling window. |
| Portfolio Treemap | Nested rectangles for a portfolio rollup (Organization โ Asset), sized by count and tinted by the average severity of the findings in each rectangle, on the Low to High scale its legend shows: an Asset with a few Critical findings reads hotter than a bigger one full of Low findings. |
Lists & Feeds
Ranked lists, feeds, and embedded tables.
| Widget | What it shows |
|---|---|
| Top-N Leaderboard | A ranked list in one of two modes: aggregate (top dimension buckets by count, e.g. Top 10 CWEs, each named with its CWE number and title, such as CWE-79 Cross-site Scripting) or records (top individual records by a metric, e.g. Top 10 Assets by Grade). |
| Embedded Table | A list (Findings, Assets, Engagements, Tests, Risk Acceptances, Organizations, or Test Types) with preset filters and ordering, as compact rows that fit the widget. The Full Table switch shows the whole list view, with column filters, sorting, paging and CSV export. |
| Recent Activity | A feed of the most-recently updated records, clickable through to detail pages. |
| SLA Burndown | Findings approaching SLA breach, ranked by days remaining, with countdown badges. |
| My Work | Everything waiting on the viewer in one queue, soonest deadline first: findings assigned to the viewer or their team, reviews waiting on them, and their risk acceptances. Always scoped to the viewer. |
| Saved Reports | One-click access to your saved Report Templates. Requires the Reporting feature and permission to view generated reports, from a global role or an Organization role (a role on an Asset alone does not grant it). |
| Top Root Causes | The highest-ranked Root Cause clusters, with the number of Findings each groups, the Assets affected, and their priority and risk band. Requires the Root Cause Correlation feature. |
My Work merges its sources into one list, one row per Finding or Risk Acceptance, ordered by days left before the SLA or expiry date, then by severity. A Finding that several sources hold is listed once. The chips above the list turn each source on or off for the viewer and show its total; Requested Reviews (reviews the viewer asked of someone else) starts off and shows as a count. A row’s menu, the first control in the row, opens the Finding or Risk Acceptance and offers its next step: Close Finding, Claim Review, Clear Review or Edit Risk Acceptance. Each step opens its form, and nothing changes until the form is submitted. A step the viewer has no permission to take is not offered. On a wide tile the next step also shows as a Next Step column. In Edit Widget, Sources picks the sources and their order, and Rows per Source sets how many rows each source loads (1 to 50).
An Embedded Table shows as many rows as fit the widget, with a pager below them, so a taller widget shows more rows. Every list shows compact rows whose columns give way as the widget narrows: each Finding names its Asset under its title, each Organization counts its Assets and tags its active Findings by severity, and each Test Type shows whether it is active and how many Tests use it. The Full Table button in the widget’s toolbar switches to the whole list view, with its column filters, column picker and paging; its Page Size is the one set in Edit Widget. Your choice of compact rows or Full Table is remembered for you, per widget. The Export Button display option shows the whole Export menu (CSV export and Quick Report), and it is off by default.
An Embedded Table’s filters are where the table starts, not a fixed scope. Anyone viewing the dashboard can change them from the Filters button, or from the column filters in the Full Table. To keep a change, save it to your own table preference (Save as New Preference, then Save Filters and Sort Order): the widget opens with your saved filters from then on, for you only. A filter your preference leaves empty keeps the widget’s own. To change what every viewer starts from, choose Edit Widget and change the filters there.
Static & Utility
Notes, shortcuts, and structure.
| Widget | What it shows |
|---|---|
| Favorites | User-curated quick links to specific pages in the app. |
| Section Break | A labeled divider for grouping related widgets under a heading. |
| Markdown / Notes | An inline rich-text panel for headers, context notes, or reference links. |
| Quick Actions | One-click action buttons that navigate to a chosen page. |
Widgets that need a feature, license or permission
Some widgets read data that only exists when a feature is turned on, the license includes it, or the viewer holds a permission. Add Widget offers such a widget only when everything it needs is in place. A widget already on a dashboard whose requirement goes missing (a feature turned off, a license without it, a viewer without the permission) stays in place but shows a placeholder naming what is missing instead of its data, and loads nothing; remove it in edit mode if it is no longer wanted.
| Widget | Needs |
|---|---|
| Scan Cadence | The Scan Cadence Assurance feature |
| License Usage, Ingest Health | The global Maintainer role |
| Saved Reports | The Reporting feature, and permission to view generated reports, from a global role or an Organization role, held directly or through a group (a role on an Asset alone does not grant it) |
| Top Root Causes | The Root Cause Correlation feature |
| PCI Quarter Status | The PCI DSS feature |
| Onboarding | The Onboarding Inbox feature (on for every instance unless an administrator turned it off) |
| Sensor Coverage | The Shogun feature, and a license that includes Shogun |
| PSIRT: Am I Affected?, PSIRT: Triage SLA, PSIRT: Feed Health, PSIRT: Our Advisories | The PSIRT feature, a license that includes the PSIRT Advisory Engine, and the PSIRT View permission |
| Ingestion Health Status | The Ingestion Health feature, and the global Connector View permission |
| Shadow AI, AI Footprint | The AI Inventory and Governance feature |
| CRA Article 14 Deadlines | The Regulatory Profile feature |
Regulatory Scope needs no feature: its rows are the regulations assigned to your Assets, which every instance can record. Only its support-period column reads the Regulatory Profile, and it counts nothing where no support period was recorded. Its CISA KEV column counts each regulation’s open findings marked Known Exploited (listed in the CISA KEV catalog).
Charting scans by category
Every Test Type belongs to a category that says what kind of scan it is: SAST, DAST, SCA, API, Container, IaC, Secrets, Cloud, Infrastructure, Mobile or Penetration Test. Charts and lists can group and filter by it, so a report of scans per category does not need a list of tools kept by hand.
- On a Graph widget with the Test model, choose Category as the group-by dimension to count tests (scans) in each category. To count scans per month in each category, group by Created with a Month time bucket and set Split By to Category (see Graph options); to chart one category on its own, filter the widget on Category instead.
- On the Finding model, the same breakdown is the Test Category dimension: findings grouped by the category of the test that reported them.
- The Tests list has a Category column (hidden by default; add it from the column picker) and a Category filter. The Findings list has a Test Category filter. Clicking a bar or slice of a chart grouped by category opens the matching list filtered to that category.
Where a category comes from
Built-in scanners have a default category, chosen from the Test Type’s name (for example, ZAP Scan is DAST, Semgrep JSON Report is SAST, Trivy Scan is Container, Checkov Scan is IaC). A Test Type whose name no default covers, such as a custom tool, takes SAST when it is marked Static, DAST when it is marked Dynamic, and otherwise Uncategorized.
Uncategorized is a category of its own: its tests show as their own bar or slice and can be selected in a filter, so no test is left out of a chart because its tool is unknown.
Setting a Test Type’s category
- Go to Settings > Test Types. The Category column shows each Test Type’s category, marked (default) when it comes from the default rather than from a choice someone made.
- Open a Test Type’s menu and choose Edit Test Type.
- Pick a Category and click Submit.
The change applies to every test of that type, including tests imported before it, and charts show it the next time they load. To go back to the default, clear the Category field and submit. The placeholder names the default the Test Type returns to.
Changing a category needs permission to edit Test Types.
Next steps
- Automating Dashboards with the API โ discover the widget catalog, create and update layouts, and render widget data over the REST API, with a complete script.
- Building Dashboards with an LLM โ let an LLM design and build dashboards for you (the dashboards API was built with AI agents in mind).
- MCP Server โ Dashboards Toolset โ connect an AI assistant to the MCP Server with
?toolsets=dashboardsto summarise, diagnose, build and share dashboards from the chat, with no script.