Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-03

Tutorial: publish and share a dashboard

From draft to audience — publish a version, share it with the team, generate a public link and understand what each option exposes.

On this page (11)

Publishing separates what you edit (draft) from what others see (published). Sharing is deciding who sees it and how: workspace members, an unguessable public link, or an open web page. This tutorial covers the three routes and what each one exposes.

Example workspace: Comércio Aurora Ltda (aurora).

Draft × published#

  • Draft: what you edit. Only people with edit permission see it.
  • Published: the frozen version readers see. You can edit the draft freely without affecting consumers, and see the pending-changes diff between draft and published before releasing the new version.
  • Up to 20 versions kept, with a per-widget diff and restore — see Editor, pages, layouts and themes.

Step by step — publish#

  1. Review the draft

    Check visuals, filters and the model. Use Refresh now to get the latest data.

  2. See what will change

    The badge next to the name says Unpublished changes when the draft is newer than the published version. More actions ▸ versions compares the versions.

  3. Publish

    Click Publish in the editor header. A new version is created; the previous one stays in the history. The badge changes to Published.

  4. Check how the reader sees it

    View dashboard leaves the editor without publishing and shows the read-only view.

  5. (Optional) Restore if needed

    In versions, Restore ▸ Confirm restore goes back to a previous version.

The three ways to share#

1. With workspace members (recommended)

Give people in the workspace access according to their role (RBAC) and apply RLS so each one sees only their own slice. This is the safest route — authenticated session, RLS, PII masking. See Roles (RBAC) and Tutorial: configure RLS.

A link with a random slug that opens the snapshot with PII always masked and zero cost for the visitor (no query runs). Copy it from More actions ▸ share ▸ 1 · Secret link. On the same screen, copy TV link gives you the big-screen version (?tv=1) — see TV link.

Warning

The public link is permanent by design today: no password and no expiration. Anyone with the link sees the dashboard. Don't use it for data that must not circulate. To cut off access, the owner uses generate new link (Tools ribbon ▸ Publishing).

3. Open web page (/painel/[slug])

Open publishing, indexable by search engines. To turn it on, the owner reads the warnings, clicks I want to publish to the web, types the dashboard name to confirm and clicks Publish to the web; the action is audited. Remove from the web turns it off. It's meant for promoting an institutional dashboard.

To embed in a website/portal#

That's embedding (with a token and an origin allowlist), covered in Tutorial: embed a dashboard.

Expected result#

  • Readers see the published version, not your draft.
  • The /d/<slug> link opens anonymously with PII masked and at no cost.
  • Authenticated members see their RLS slice.

Security#

  • Every output applies RLS + PII masking + a confidentiality stamp.
  • Public links do not require sign-in — that's why they always mask PII and never run a new query.

Limits and caveats#

  • No password/expiration for public links today: to cut off access, generate a new link.

Related#


Last reviewed: 2026-10-03.

Related links