Semantic Catalog
Create and manage semantic layers so teams share the same definitions and reuse logic over time.
Shipped: layers and publishing workflow
- Create semantic layers per connection with a namespace (e.g., finance.revenue).
- Work with drafts and versions.
- Publish changes with explicit modes (view/edit/publish).
Semantic catalog overview
Preview image coming soon
Browse layers by connection, create new layers, and search your catalog.
Layer view: versions + draft
Preview image coming soon
View versions, work in draft, and publish changes with clear modes.
What data leaders get out of it
Consistency
- Shared definitions reduce dashboard drift.
- Metrics become reusable building blocks, not one-off SQL snippets.
- Namespaces make it clear what’s “official” versus ad-hoc.
Velocity
- Agents and notebooks can use the same definitions.
- Teams iterate safely via drafts and publishing.
- Less rework for data teams when stakeholders ask the same questions weekly.
Why it matters
Self-serve breaks when definitions drift. A semantic catalog makes shared context explicit so answers are consistent across notebooks, conversations, and teams.