Send the link. Keep the work.
A published dashboard opens for somebody with no account and nothing installed. A single widget can have its own link. And a design can be handed to another account outright.
Four shapes
Four ways to let somebody in
Publish a page
It goes to the web with a link you can send. The reader needs no account and installs nothing. Ten pages on Pro, fifty on Team.
Link one widget
Lift a single tile out of a design and give it its own address — the chart, not the dashboard around it. Useful when the thing worth showing is one number.
Hand it to someone
Share a widget or a whole page with another account. Sharing is always the owner's choice; nothing here is public because a default said so.
Put it in the League
Three leagues — apps, dashboards and widgets — where what people build is visible to other people building. Opt in, per thing, whenever you want.
The part most tools skip
What a shared page can and cannot show
A tile that reads your account's data cannot show that data to a stranger.
And dash-b says so, rather than quietly rendering an empty box that looks like a bug in your dashboard.
There are two kinds of tile, and the difference decides what a visitor sees:
- Tiles bound to something your account owns — your database, your bookings, your uptime monitor. A stranger opening the link gets the tile, empty, with a reason.
- Tiles bound to whatever the reader has connected — their weather, their calendar, their own connected account. A stranger gets theirs, which is usually the point.
Knowing which is which before you send the link is the difference between a demo and an accident. The designer tells you before you publish, not after somebody replies asking why the chart is blank.
And if you would rather not share it through us at all.
Export the whole designer with your work in it and host the result yourself. That has never needed a plan and never will.