Sharing dashboards (permalinks)
Public permalinks, JSON export/import, and production considerations.
dashboardssharingpermalinkexportimport
Sharing and export
- Public permalink — generate a secret-token kiosk URL that renders the dashboard without login (optionally locked to a fixed time range and variable values, with an expiry and revoke). Anyone with the link can view the data, so treat it as a shared secret.
- Export — export the dashboard configuration as JSON for backup or migration.
- Import — import dashboard JSON to recreate a dashboard in another environment.
Create a shareable permalink (step by step)
- Open the dashboard and click Share (top right).
- In the Permalink manager, click Create link.
- Choose what the link captures — the current variables and time range — so the recipient sees exactly your view.
- Copy the link and open it to confirm it renders read-only.
- Revoke a link any time from the same manager when it should stop working.
Version-control your dashboards. Export important dashboards as JSON and commit them to a repository. You get change history, review, and a clean path to promote the same board fromstagingtoprodvia import.
Production considerations
- Access and sharing. A share link exposes the dashboard's data — confirm the audience is appropriate before sending it.
- Imported dashboards showing no data: the source environment's metric names, services, or data sources differ from the target. Confirm the target environment emits the same metrics, and parameterize environment-specific values with variables before exporting.
- Retention. Widgets can only show data within your data retention window; a 30-day panel on 7-day retention shows gaps.
Tips
- Use a permalink for a read-only executive view you embed in a wiki or TV dashboard (combine with an Iframe widget elsewhere, and the dashboard's fullscreen TV mode).
- Pin a "launch room" permalink in your release channel so everyone watches the same board during a deploy.
- For internal collaborators, sharing the dashboard URL plus access is enough; permalinks are best for external/embedded, range-locked views.