Sharing
Publish a read-only link to chosen datasets, dashboards, newsletters and other resources so people outside the workspace can see them without signing in.
Sharing works at the workspace level. One public link per workspace shows a curated set of tabs: the datasets, dashboards, newsletters, pipelines, alert rules and integrations you choose, and nothing else. Viewers do not need an account.
- Chooseup to 100 resources
- Publishone link per workspace
- Send the linkread-only, no sign-in
- RevokeDisable in the share dialog
Opening the share dialog
The share icon sits in the top bar of every page, next to the theme toggle and the notifications bell. Its tooltip reads Share workspace.
Some items cannot be selected, and the list says why:
| Resource | Condition to be shareable |
|---|---|
| Dataset | Status is ready (it has at least one version). |
| Dashboard | It has 50 widgets or fewer. |
| Pipeline | It has a published statement of work. See Statement of work and steps. |
| Newsletter, alert rule, integration | Always shareable. |
Publishing and updating
- Pick the resources. Tick items in the left pane; they appear on the right. Between 1 and 100.
- Order the tabs. Drag items in the right pane. The first is the tab viewers land on after the overview.
- Publish share. The link is created, the toast reads “Share published”, and you are taken to the public page to check it. The button reads Save changes on later visits and the header Edit share.
The link has the form /share/{token}-{workspace-name}. The token is random and long; the page is not listed anywhere, so only people you send the link to will find it.
Anyone with the link can view. There is no password, no viewer list and no expiry. If you need to stop access, disable the share; a new publish later gets a new link.
What a viewer sees
The public page has your workspace’s icon, name and tagline, an Overview tab, then one tab per shared resource. The overview explains that it is a read-only workspace shared by its owner and that only the listed resources are public. A Get started button invites the viewer to create their own workspace. If you open your own share while signed in, a banner reminds you it is public and offers Copy link.
Datasets
A banner with the dataset’s description and its counts, worksheets and version, then the grid: worksheet tabs, 50 rows per page (25 or 100 selectable), search, sorting, and a View row chevron on each row. Clicking a row opens the row dialog with Data, Provenance and Activity tabs, including fetch content and screenshots, so a reader can check any value against its source. Links in cells render as plain text.
What is exposed, precisely: the active version only; worksheet names, counts and collects labels; column order, hidden columns and formats as set in table settings; the rows; and each row’s provenance. Not exposed: older versions, SQL, exports, editing, runs, integrations, or anything else in the workspace. If the dataset later stops being ready, its tab shows nothing until it is again.
Dashboards
The full dashboard in the same grid layout, read-only, with every widget computed when the page is opened, so viewers always see the current active versions. Table widgets show their first rows with a “N more rows” footer rather than paging. Dashboards with parameters (row-detail dashboards produced by the wizard) have no parameter picker on the public page, so share the overview dashboard rather than a drill-down.
Newsletters
The latest issue, rendered as it was emailed. If no issue has been generated yet the tab says so.
Pipelines, alert rules and integrations
A pipeline tab shows its statement of work. Alert rules and integrations show their names and descriptions; no configuration, addresses or credentials are exposed.
Limits
Revoking access
Open the share dialog and press Disable. The toast reads “Sharing disabled” and the old link returns a not-found page for everyone. Publishing again later creates a new token; the old one never comes back.
Removing a single item and saving keeps the link but drops that tab. Deleting a shared dataset, dashboard or newsletter removes it from the share automatically; if that leaves the share empty, sharing is disabled.
What viewers can and cannot do
| Viewers can | Viewers cannot |
|---|---|
| Read every shared tab without an account | See anything not in the share, including other datasets in the same workspace |
| Page, sort and search a shared dataset | Run SQL, export, edit or delete rows |
| Open any row and read its provenance, fetch content and screenshots | Open older versions |
| See a dashboard’s widgets with current data | Change widgets, pick a drill-down parameter or rearrange the grid |
| Read the latest newsletter issue | See recipients, the schedule or past issues |
| Read a pipeline’s statement of work | Run it, see its runs, settings or inputs |
| Copy the link and open it elsewhere | Comment, sign in to the workspace or see who else has the link |
A visitor who signs in with their own Jsonify account is also offered to clone the shared workspace as a starting point of their own. Pipelines are not copied; alert rules come across switched off and widened to every pipeline; no integrations or credentials are copied.
Embedding
Add ?embed=true to the share link to hide the branding and show only the tabs; useful inside an intranet page or a wiki. The rate limits and the read-only rules are the same.
A share for one dataset
The most common share is a single dataset for a client or a colleague.
- Make sure the dataset is ready. It needs at least one version; a dataset still “building” is greyed out in the dialog.
- Tidy the columns. Hidden columns and formats from table settings apply to the public view, so hide internal columns and set currency formats first. See Dataset pages.
- Open the share dialog from the top bar, tick the dataset under Datasets, and press Publish share.
- Copy the link from the public page banner or from the dialog’s share field, and send it.
The link keeps showing the active version, so when the pipeline publishes next week the reader sees the new rows without a new link.
Troubleshooting
Share the Competitive Market Pulse dashboard and the Live product offers dataset with the retail team, and put the dashboard first.
Jason publishes (or updates) the workspace share with those two items in that order and replies with the link.