Skip to content

Clarify that verification is read-only in CLI workflows #553

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
torimwhaley merged 2 commits into from
Apr 21, 2026
Merged

Clarify that verification is read-only in CLI workflows #553

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f8be06
Clarify that verification is read-only in CLI workflows
mintlify[bot] Apr 21, 2026
d24b3d9
Remove redundant tip from verified content page
mintlify[bot] Apr 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions guides/verified-content.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,10 @@ This guarantees that a verified badge always reflects content that an admin has

Verification status is included in [charts and dashboards as code](/guides/developer/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.

This is especially useful when you're using an AI agent, the [Lightdash CLI](/references/lightdash-cli), or [agent skills](/guides/developer/agent-skills) to build on top of trusted content. You can point your agent at your verified charts and dashboards as a source of truth for approved patterns, metrics, and layouts.
<Note>
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.

<Tip>
If you're building content with AI agents, starting from verified charts and dashboards is a great way to make sure new content is grounded in patterns your team has already reviewed and approved.
</Tip>
Full CLI support for writing verification status is being tracked in [this issue](https://github.com/lightdash/lightdash/issues/22138).
</Note>

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](/references/lightdash-cli), or [agent skills](/guides/developer/agent-skills) to build on top of trusted content.
Loading