Save, preview, and publish
Move a dashboard from a draft to a published user experience.
Studio separates the editable draft from the published dashboard. The draft is where the team works. The published version is what the web application loads.
- Edit the dashboard.
- Wait for the draft save.
- Try important pages and interactions in preview.
- Check mobile, tablet, and desktop.
- Review bindings, empty states, setup pages, and permissions.
- Choose Publish and confirm.
- Open the web application and verify the published experience.
| State | Meaning |
|---|---|
| Draft | The editable version in Studio. |
| Published | The version available to the web application. |
| Unpublished changes | The draft differs from the published version. |
An autosaved draft is still a draft. Refreshing the web application will not show it until you publish.
Before publishing, confirm that pages have clear navigation, bindings use the right source, charts and tables have useful results or empty states, controls have correct access, layouts work at all breakpoints, setup pages still have their required controls, and long or missing values do not break the page.
After publishing, test with a user who can access the device. Compare live values with device status and Console monitoring. If the page is unchanged, confirm that the latest draft was published and that the web application opened the same dashboard and device template.