Sharing a Dashboard
Vincent Depassier · September 1, 2026
A dashboard has three visibility levels, and the difference between them is who has to prove who they are.
Visibility | Who can open it |
Private | People in your workspace, subject to their access |
Protected | People who authenticate — your end users |
Public | Anyone with the link. No login |
Private and protected both have a reader whose permissions can be checked. Public does not, and that single fact is what the rest of this page is about.
Before you publish publicly
A public dashboard is served anonymously. To draw its widgets, it also serves the data behind them — and it serves the tables those widgets point at, not merely the aggregates on screen.
Three consequences follow, and all three surprise people:
Every column travels, not just the charted ones. A chart of order counts sits on a table that may also hold margins, contact details or internal notes. The chart shows counts; the table behind it is what is being served.
Every row travels, not just the visible ones. A widget showing this month is reading a table that holds every month.
A reader is not limited to the view you designed. The page fetches its own data, and anything the page can fetch, a person holding the link can fetch — filtered and paged as they choose, not as you laid out.
None of this is a defect. Public means public; the platform is doing exactly what you asked. It is simply a bigger ask than most people realise they are making.
How to publish safely
The reliable pattern is to publish over data prepared for publication, not over the operational table:
Build a table that holds only what is meant to be seen — the aggregate, the public figures, the anonymised rows.
Keep it filled by an automation from the real table on whatever cadence suits.
Point the public dashboard's widgets at that table only.
It costs one table and one automation, and it converts "is this safe" from a judgement you re-make every time somebody edits a widget into a property of the design.
If that is more than the situation needs, the alternative is protected visibility: your end users authenticate, and the dashboard is only as open as their accounts.
Status matters too
A dashboard is only reachable publicly when it is both public and active. Setting it back to draft or archived takes it offline, which is the fastest way to pull a published dashboard without dismantling it.
Revoking works the same way as publishing: change the visibility and the link stops resolving.
Versions
A published dashboard keeps serving its published version while you work on a draft. That is what lets you rebuild the page without breaking the view of everyone watching it — the change appears when you publish, not while you are mid-edit.
Next
Dashboards in Praxsuite
Dashboard Widgets
Permissions in Praxsuite
End Users
Files
What it looks like
Privacy and status live in the dashboard's top bar. In edit mode they are two dropdowns; in view mode the same two values are shown as plain text, so you can always read a dashboard's exposure without entering edit mode.
The Public View button appears only once privacy is Public — it opens the dashboard exactly as an anonymous visitor sees it, which is the check worth doing before you hand the link to anyone.
Those two values currently render in English in every language. It is a known gap in the interface, not a difference in behaviour.