Status
In private development. Early access by invitation.
Platforms
Account and data
Also on this site
Platforms
Account and data
Also on this site
Status
In private development. Early access by invitation.
Publishing a dashboard turns it into a link that other people can open in a browser. Publishing is the one step that stores your data with Emolysis, and it happens only when you choose it. Publishing is part of the paid plans; building dashboards on your machine does not need a paid plan. See Plans and pricing.
In the app, choose Publish, or ask the agent to publish. You need to be signed in. Emolysis uploads the dashboard's charts and the data behind them as a new revision and returns the dashboard's stable link, of the form emolysis.com/d/<id>. The published data is the table the charts read, not your full source tables.
You choose one of three settings when you publish:
| Setting | Who can open the link |
|---|---|
| Link | Anyone with the link, signed in or not |
| Organization | Signed-in members of your Emolysis organization (default) |
| Only me | Only you, when signed in |
The setting is fixed for the life of the link. To change who can open a dashboard, revoke its link, then publish the dashboard again with the setting you want. When you revoke a link, the old URL stops opening and the revisions kept under it are deleted. Publishing again makes a new link with a new URL, starting from the revision you publish, so send the new link to the people who should have it. A dashboard has one link at a time. If you publish it with a different setting from the one its link has, Emolysis stops and says so before anything is uploaded.
Important
Anyone the link reaches can open a dashboard with Link visibility, and a link can be forwarded. Use it only for data you would share that way.
The browser viewer opens dashboards with Link visibility. Organization and Only me dashboards open in the Emolysis app until signing in on the website opens.
A dashboard keeps one stable link. Each publish, or a refresh with publishing on, adds a revision: a fixed snapshot of the rows its charts show. People with the link see the latest revision, and the most recent revisions are kept and stay readable. The link you sent stays the same, and each revision shows exactly what was published at that time.
Charts published on their own, rather than as a saved dashboard, get a snapshot link. A snapshot link never changes: publishing the charts again creates a new link.
You can revoke a link at any time, which deletes its published data; for a stable link, that is the dashboard and every revision kept under it. The person who published it, and their organization's owners and admins, can revoke it.
Revoking a dashboard's link does not touch the dashboard on your machine, and you can publish it again: the next publish makes a new link. The same happens when the link was revoked somewhere else, for example by an owner or admin of your organization. The next time you publish the dashboard from the app, Emolysis makes a new link, open to your organization unless you choose another setting, and tells you the old link was replaced. A refresh with publishing on never makes a link: it stops, and says why, until a person publishes the dashboard again.
A snapshot link can also have an expiry date, after which it stops working. A dashboard's stable link has none. Set an expiry on any snapshot link you share outside your company.
A loading state while the dashboard opens, then the dashboard, or a clear message when a link is not found, has been revoked, has expired, or needs sign-in. A chart that cannot be drawn shows its problem in place, and the other charts still draw. Every chart has its data in a table below it, so a figure can be read and checked, not only seen.
A link you cannot open never shows whether a dashboard exists behind it. Without signing in, a link limited to an organization or to one person asks for sign-in, and so does a link that points to no dashboard; once you are signed in, both say "not found".
A published dashboard holds up to 50 MB of data in total. Large tables should be aggregated before publishing; a dashboard rarely needs raw rows. The gold table behind a dashboard is already aggregated to a declared grain, which keeps it small.
When you publish, the dashboard's charts and the data behind them are uploaded and stored by Emolysis. Which people can open the link depends on the visibility you chose. Publishing is separate from the agent's prompts: with a paid plan's included usage or usage credits (on Enterprise, metered usage), prompts and responses pass through Emolysis's metering service on the way to the model provider. That service is designed not to store or log their content. See Data handling for the complete list.
Dashboards from a question describes how a dashboard is built, and Chart types lists what it can show. You can open the sample dashboard to see how a published dashboard looks; it runs on synthetic data.
Previous
Dashboards from a question
Next
Chart types