Verified charts and dashboards

Mark charts and dashboards as verified so your team can instantly identify trusted, approved content. Verified content gets a green checkmark badge that shows who verified it and when, and verification is automatically removed if the content is edited.

This feature is currently in beta.

Verified charts and dashboards let organization and project admins sign off on specific content so the rest of your team knows at a glance which charts and dashboards are trusted and approved.

Each verified item gets a green checkmark badge that shows who verified it and when. Verification always reflects the current state of the content. If a chart or dashboard is edited after being verified, the badge is automatically removed and an admin will need to re-verify the updated version.

Who can verify content

Only organization admins and project admins can verify or unverify charts and dashboards. All other users can see which content is verified, but cannot change verification status themselves.

Verifying a chart or dashboard

Admins can verify content directly from the chart or dashboard, or from the verification panel in project settings.

Admins also have a dedicated verification panel under Project settings that lists all verified content and provides a central place to manage verification across the project.

Where users see verified content

Once a chart or dashboard is verified, the green checkmark badge appears wherever that content is surfaced, including:

• The homepage, so users can quickly spot approved content to start from
• Chart and dashboard listings
• Inside the chart or dashboard itself, along with the verifier’s name and verification timestamp

This makes it easy for teams to distinguish between exploratory or work-in-progress content and content that’s been reviewed and approved.

Verification is automatically removed when content changes

Verification is tied to the exact state of the content at the time it was verified. If anyone edits a verified chart or dashboard, the verification badge is automatically removed. An admin will need to review the updated version and re-verify it.

This guarantees that a verified badge always reflects content that an admin has explicitly approved in its current form.

Verification in charts and dashboards as code

Verification status is included in charts and dashboards as code. When you run lightdash download, verified content includes verification metadata right in the YAML, so you can see which downloaded files represent approved content.

Verification metadata is currently read-only in content-as-code workflows. Running lightdash download includes verification status in the YAML, but lightdash upload does not write verification back. To apply or remove the verified badge, use the three-dot menu on a chart or dashboard in the Lightdash UI.

Full CLI support for writing verification status is being tracked in this issue.

Even though verification is read-only in the CLI today, you can still build on top of verified content. Anything marked as verified in the UI is visible in the downloaded YAML, so your trusted repository can reference those charts and dashboards as the source of truth for downstream work. This is especially useful when you’re using an AI agent, the Lightdash CLI, or agent skills to build on top of trusted content.