Dashboards
Describe who a dashboard is for and what they do with it. The analyst plans it, builds it while you watch, and every number on it stays a query you can open.
A dashboard in OpenDash is built by the analyst for one job: a revenue review, a renewals desk, a support queue to work through. You say who it's for and what they decide with it. The analyst shows a plan, builds the dashboard on its page while you watch, and checks it before it calls it done.
Each dashboard has its own layout, written for its job, instead of a grid of standard tiles. It reads your data only through named queries, and the server checks and runs every one of them as the person viewing.
Build one
Describe the job
Open Dashboards and press New dashboard, or pick a start: Customer health, Revenue review or A queue to work through. Either opens the analyst beside the page with the request begun, for you to finish. You can also ask for one from any conversation: "Build me a dashboard for the success team: who's at risk and who needs a call this week."
Say who will use it and what they decide with it. A sketch or a screenshot of a dashboard you like helps: attach it to the question.
Review the plan
Before it builds anything, the analyst replies with a plan: what the dashboard is for, the data it reads, and each page with the pieces on it, in the order a reader meets them. The plan also says what your data lacks, and anything a row's button would change in a connected service.
Press Build it, or reply to change the plan. A plan you haven't built yet waits in the list as Planned.
Watch it build
The dashboard opens with the conversation beside it, and you watch it take shape. Every save is built and checked before it reaches the page: each query against your data, and the layout at phone, tablet and desktop widths. Stop keeps the last draft that passed.
Publish
What the analyst built is a draft that only you see. Look it over, then Publish it. If any of its queries read data no admin has verified (the analyst's own SQL, a definition not released yet, or a connected service), OpenDash lists them and asks you to confirm first.
Change it
- Continue opens the conversation it was built in. Ask for the change there: "add churn beside MRR".
- Select lets you click a piece of the dashboard to point the analyst at it, then describe the change in the panel beside it. Esc leaves.
- ⌘J (Ctrl+J) opens the analyst beside the dashboard from anywhere on its page.
Changes go into the draft, and the published version stays as it is until you publish again. Undo these changes, under the answer that made them, puts the draft back as it was before that run, as long as nothing was saved over it or published since.
Versions keeps every published version. The owner can restore any of them.
Read it
- Every number opens its rows. Click a figure to see the records behind it.
- Each chart and table says where its numbers come from in a quiet line beneath it, such as Warehouse · Accounts. Hover it to see whether the data is verified.
- Filters such as a period or a plan narrow the whole dashboard, and stay in the page's address, so a link opens with the same view.
- A dashboard can also hold a written summary of its numbers, which says what it's written from.
Freshness
Each query runs as the viewer, under that person's access, through the same read-only query gateway as a question. Results are cached for up to five minutes.
Work from it
A dashboard can be a place to get work done, not only to read:
- Work on records. A queue or a list can give each record an owner, a status, a note and a follow-up date. These are kept in OpenDash, never written to your database, with who changed what and when. Viewers can read them but not change them.
- Act in a connected service. A row can have a button that changes something in a connected service, such as Move to Done in Jira. Every press is confirmed on OpenDash's own dialog and runs with the presser's own account. Tools that may delete or overwrite are never used.
Data it can read
A dashboard can read any of your sources, not only the one its conversation started on, and combine them, say tickets from one and accounts from another. In order of preference it uses:
- a released dataset or metric (verified);
- a dataset not released yet, its numbers marked Unverified;
- the analyst's own SQL over the tables a source has learned;
- a connected service, such as Jira or HubSpot, read live each time the dashboard opens.
Sample data never mixes with your own.
Data from a connected service
A dashboard reads a connected service only with the tools an admin allowed for dashboards. On a server where each person connects their own account, every viewer sees what their own account can see, and is asked to sign in first. On a server with one account for everyone, everyone sees the same data. See Connected services.
Sharing
Who sees it sets who can open it: Only you, Its project, or Everyone in the workspace. Specific people… shares it by name, each to View or Can edit.
- Editors change the draft from their own conversations, and see the draft and the build the owner sees. Only the owner publishes, restores a version, changes sharing, or deletes it. Owners and admins can delete any dashboard.
- A shared dashboard shows each reader the data their own access allows.
- When someone leaves the workspace, their shares end.
Export
Dashboards are read in OpenDash and aren't exported. To send numbers to someone, download an answer as a PDF from its conversation, or set up a routine.
Learning loop
How a correction from anyone on the team becomes a checked, tested and reviewed learning that applies to everyone, and when it's released without waiting.
Connections
Connect services such as Jira, HubSpot or Fullstory over MCP, so the analyst and your dashboards can read what lives only there, and change things only when you allow each call.