Saved queries
Every query worth running twice belongs in the Saved Queries library: a workspace-wide, searchable catalog of SQL with its source binding, tags, and usage tracking.
What’s in a saved query
Section titled “What’s in a saved query”Name, description, the SQL text, the data source it runs against, an optional model binding, tags, and a favorite flag. Save from the SQL editor’s Save dialog — either as a new entry or updating an existing one.
The library
Section titled “The library”The Saved Queries page is a filterable table — search across names, descriptions, and SQL text; filter by tags, source, model, dashboard, favorites, or unused (queries no dashboard references); sort by recency or name.
Per query: Run, open in the editor, edit, duplicate (carries its source and model bindings), copy SQL, add to dashboard, favorite, delete. Bulk actions cover tagging and deleting several at once, and the current view exports to CSV.
The detail drawer shows the SQL, a tag editor, and — the governance part — “Used in N dashboards” with links, so you know exactly what breaks before editing a query.
Queries on dashboards
Section titled “Queries on dashboards”Add to dashboard (or the canvas’s SQL insert card) places a saved query on a dashboard as a live card: it re-queries on refresh and participates in the dashboard like any other card. This is the escape hatch for logic that doesn’t fit the model — with the query still centrally managed in the library.
Related
Section titled “Related”- SQL editor
- Canvas basics — the SQL insert card.