Knowledge
Glossary terms, guides, verified queries, skills and memory. What each one teaches the analyst, when it's used, and who can change it.
Knowledge is how OpenDash learns the way your business talks. It lives under Knowledge and comes in five kinds:
| Kind | Teaches the analyst | Used |
|---|---|---|
| Glossary term | What a word means at your company | On every question |
| Guide | How to approach a topic or a table | Pinned: every question. Otherwise when search finds it |
| Verified query | How a question like this was answered correctly before | When a question matches |
| Skill | A step-by-step procedure | When it fits the question |
| Memory | One person's preferences | That person's questions only |
Everything except memory is shared by the workspace, versioned, and changed only by owners and admins. Saving creates a new draft version; the released version keeps answering until the new one is approved.
Glossary terms
A term says what a word means here, and optionally which column and values it maps to:
term: SMB
means: Small businesses, here accounts with up to 50 employees.
synonyms: [small business, small businesses, SMBs]
maps_to:
column: "public.accounts.employee_band"
values: ["1-10", "11-50"]maps_to can also name a metric, and not lists tables the term must never be read from. A mapping is checked against the catalog. A term can apply to one source or to the whole workspace.
The glossary pays off quickly
On DashBench, questions that only a company's own definitions settle ("SMB", "last fiscal quarter") went from 3 of 6 right to 6 of 6 with the glossary, in half the model calls. See DashBench.
Guides
A guide is Markdown advice: how your company counts churn, which table is the source of truth, what to watch out for.
- Pinned guides are in front of the analyst on every question (up to 1,500 characters).
- Unpinned guides (up to 8,000 characters) are found by search when relevant: by keyword, and by meaning when embeddings are on.
- A guide can be attached to a table, and is given to the analyst whenever it reads that table.
Verified queries
When an answer took the metric path and is right, an owner or admin can save its query as a verified query, with the question and other ways of phrasing it. Saving is the review.
When a similar question comes in, the analyst gets the closest verified queries and follows one as a template, adapting the period rather than replaying it. Only metric queries can be verified, not raw SQL.
Skills
A skill is a named procedure: a one-line "use it when", and Markdown steps. The name and the "use it when" line are in front of the analyst on every question; it reads the steps only when the skill fits. One skill ships built in: investigate-a-change. The analyst also has its own reference skills for building dashboards, read only when it builds one.
Memory
Memory is personal: only its owner's questions use it, and only its owner sees it. The analyst saves a short note when you ask it to ("remember…", "from now on…"), correct it, or state a preference. Up to 50 notes are kept.
Goals
Under Settings → Goals, owners and admins set a target on a verified metric, with a due date and whether it's a floor or a ceiling. Home shows progress and a forecast, and a routine can alert you when a goal is at risk.
Datasets and metrics
OpenDash's semantic layer. Datasets describe your tables in small YAML files, metrics name the numbers that matter, and both compile to safe SQL.
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.