Sharing dashboards

What is org-visible

There is no private, personal, or per-team dashboard. Every dashboard a connected repository applies is readable by every member of the organization, at the Viewer role and above, the same as monitors, incidents, and issues. There is no public link, no per-dashboard share button, and no way to restrict one dashboard to fewer people than the whole organization.

If you want a dashboard fewer people can see, that is a question for who is a member of the organization (or, once teams narrow anything, a team question), not a dashboard setting.

The Dashboard Kind is the sharing model

Because a dashboard is declared in the same connected repository as every other resource, "who can add or change a dashboard" is really "who can merge to that repository," reviewed the way your team reviews any other change to it, not a permission granted inside upzero. Read access inside the console (seeing a dashboard once it is applied) and write access to the manifest (proposing a new one) are two different things, controlled in two different places:

• Read: controlled by organization membership and role, inside upzero.
• Write: controlled by repository access and branch protection, in your git host.

See Configuration as code for connecting a repository and how a push becomes an applied dashboard.

Provenance

A dashboard's detail page in the console shows the manifest path it was declared at and the commit that last applied it, so anyone looking at a dashboard can trace it back to the pull request that shaped it, rather than wondering who built it or why a panel looks the way it does.