Dashboards and sharing
Every dataflow has a dashboard: a page of its own that shows only the nodes you pin, ready to present. Share its link and people see your charts and maps and can try other values of the controls you pin, or share the dataflow's link so they can open the whole canvas.
Pin nodes
Each node has a small circle labelled Pin to dashboard among the buttons in its header, which show while the pointer is over the node. Click it on the charts and maps you want to show, and it turns into a red dot; click it again (Unpin from dashboard) to take the node off. Pinning also means the data behind those nodes is saved to your Data Catalog when the dataflow runs, and that saved data is what the dashboard draws.
After pinning, run the dataflow and save it. The dashboard shows the nodes that are pinned, drawn from the outputs your latest runs saved.
Agents know which nodes are tiles, so you can ask one whether a chart is on the dashboard; only you pin and unpin. A specification an agent writes for a pinned Autark map is sent back when it loads data of its own, and the agent loads that data in a node before the map instead. An agent's Solve stops on such a map, says why and leaves it to you. The card of a plan that removed pinned nodes marks each as a dashboard tile and says how many left the dashboard.
Open the dashboard
On the canvas, choose Share > Open dashboard. The dashboard opens in a new tab at an address of its own, and its tiles draw from the saved outputs, with nothing to press. A tile whose nodes have no saved output runs them when the page opens, and says Computing... until its results are ready. Open dataflow, at the top, takes you back to the canvas. A guest on a hosted Curio opens the dashboard the same way, and it shows the dataflow as that guest changed it, to that guest alone.
As the owner, click Edit layout to move tiles by their title bar and resize them, then Save layout. This arranges the dashboard only: nodes keep their places on the canvas. If nothing is pinned yet, the page says so and links back to the dataflow.
A map made with Autark draws in the viewer's own browser, so it needs a browser with WebGPU. Text that a code node prints is not shown on the dashboard.
Try other values
Anyone viewing the dashboard can change its pinned controls, the widgets of every pinned node: a Python node's tile shows them in place of its code, and a Vega-Lite or Autark tile above its chart or map. Text, text list and file widgets keep their saved value.
- A chart or map draws again with a new value of its own widget. Any other change runs the nodes it reaches once you stop changing it, with no Run button: they run on the server with the owner's data, models and packages, and none of the owner's keys, and the tiles below show the result.
- A viewer never changes the dataflow or the owner's Data Catalog, and putting a value back shows the saved results again.
- What such a run makes is kept for 7 days, so the next viewer who picks the same values sees it at once.
- A node that only a browser runs, such as an Autark computation on the GPU, runs in each viewer's own browser.
Share a link
The Share menu offers two links, and both need the dataflow to be saved first:
- Copy dashboard link copies the dashboard's address. Visitors see the pinned tiles and can change the pinned controls, with no account.
- Copy dataflow link copies the canvas address. The editors you invite edit the dataflow with you. Anyone else sees the whole dataflow, read-only, and File > Save dataflow saves a copy, with its saved results, to their own workspace.
Anyone who can sign in to that Curio server can open a dataflow link. If the server allows guests, the sign-in page also offers Continue as Guest. The dashboard has the same Share menu, with both links.
To edit a dataflow with other people at the same time, see Collaboration.


