Turn a recorded session into a shared dashboard

Worked example

Example: a furnace event and its recorded readings

Use a fictional furnace temperature and status recorded around an event. Save the selected session as an analysis, then let another authorized reader inspect the result.

Procedure

Follow the task in order

1. 1
   Check prerequisitesUse the component versions above once available in your installed Runtime. You need a closed Capture session, eligible observations archived into QuestDB, matching history mappings, a reachable API and permission to read the selected source. Updating these guides does not upgrade an installation.
2. 2
   Open the recorded sessionGo to Automations → Captures & sessions. Open the capture with Edit capture, then Recent sessions and choose Explore for a closed session. This is the current entry path even when you only want to inspect results. Check the session and exact time bounds before interpreting its observations.
3. 3
   Choose the columns you needAuto focuses on observation time and useful measurement fields. Use All or Custom to inspect technical event, session or archive fields. This changes presentation only: it does not delete stored fields, convert units or collapse duplicate-time observations.
4. 4
   Save a repeatable analysisUse Save for your own view, or Save as for another analysis. Saving a shared view owned by someone else creates your own copy through the existing Save-as form, initially Private. Give it a useful name and reopen it to check its session, series, sources, columns and time mode. Fixed historical bounds stay fixed; a live range moves and may later contain no archived values.
5. 5
   Create a dashboard panelOpen Dashboards → New dashboard, then Add panel. Choose the saved view or a supported direct Table source. A saved view panel follows its saved selection and presentation; a direct Table panel reads its declared source. Inspect Chart and Table modes, timestamps, units and missing observations. Save the dashboard, then reopen it.
6. 6
   Keep draft changes deliberatelySave layout or time changes before leaving. When prompted about unsaved changes, Cancel keeps the draft open and Discard leaves without saving it. A pending save must finish before you leave. The owner can rename a dashboard through its existing More menu.
7. 7
   Review three independent sharing boundariesThe owner can change dashboard visibility from Private to Team through More. Team means all signed-in users, not a selected subgroup. Review every referenced saved view separately: sharing a dashboard does not share a Private view. Sharing a view reveals its name, topic paths and settings, but still grants no underlying topic read permission. Copy link grants neither visibility nor data access.
8. 8
   Verify as an authorized readerReopen the shared dashboard as a reader. A Private or unavailable view displays a neutral message and Retry; ask its owner to review visibility. A source access-denied message requires a permission review, not repeated service restarts. A service or database failure is a different condition: check Services diagnostics. Readers cannot edit the owner’s dashboard by adding an edit flag to its URL.
9. 9
   Refresh after visibility changesDashboard refresh rechecks access to its saved views and clears previously displayed data when the dependency is no longer available. Retry after the owner restores access. This is refresh-driven revalidation, not a promise of an immediate pushed withdrawal notification.
10. 10
    Use Explore for a deliberate exportDashboard Table reads are bounded raw observations. Explore chart mode may sample or aggregate, so its results can differ. Open the view in Explore, inspect the time and query settings and select the intended export. Check row limits and truncation; a bounded panel is not an unlimited archive export.

Expected result

What you should have

Boundaries

Important boundaries

• No archived values in this time range means this request returned no rows. Check the session, fixed bounds, selected source and archival availability; do not interpret it as zero or as proof of a service outage.
• Saved views and dashboards are reusable selections, not immutable evidence snapshots. Retention, source availability and current permissions still apply.
• Team visibility exposes names and selections to all signed-in users. Review Private dependencies and source-topic rights before sharing.

Related guides

Continue from here