Publishing gives a review group a stable dashboard URL while the metrics remain connected to their governed sources. Readers see the same approved definitions without receiving a copied data extract.
A publish action records the target audience, the metric set, the refresh rule, and the stale-data behavior. Editors can keep working on draft changes while the published view remains tied to the approved version.
curl https://api.signallake.test/v1/dashboards/revenue-weekly/publish \
-H "Authorization: Bearer sk_test" \
-H "Content-Type: application/json" \
-d '{"audience":"executive-review","metric_set":"revenue-v3","refresh":"hourly","stale":"warn","exports":"disabled"}'
A published dashboard still reads from the approved metric set. If a source becomes stale or a definition changes, SignalLake marks the issue on the review page instead of hiding it in an exported deck.
That distinction matters during weekly reviews. The audience gets a stable page, while editors keep the ability to prepare the next review cycle without overwriting the current one.