Semantic model

Open Team spaces → Model → Semantic model ("Unified data. Clear context."). The semantic model describes your data in business terms: what a customer, an order, or a branch is, which table holds it, how tables connect, and what people call things. Chat, dashboards, and Relays use it to join data correctly and to understand questions in your team's own words.

The left side lists the model's parts with counts: Entities, Relationships, Conformed dimensions, Dimension fields, Attributes, Measures, and Synonyms. Select an entity to see its related entities as a diagram, with details on the right.

Entities

An entity is a business object backed by a table. Click New entity and set its Name, Table, Synonyms (comma-separated words people use for it, like "outlets" for branches), its Attributes & dimensions, Measures, and Relationships.

A measure can be a formula, for example DIVIDE(SUM([revenue]), COUNT([order_id])).

Relationships

A relationship says how two entities join. Set:

• Key(s) and Cardinality (such as one-to-many)
• Join — Keep unmatched or Matches only
• Key matching — Exact match, Trim spaces, or Trim + ignore case

A data check runs against the real tables and reports Duplicate keys, Orphan keys, and what the data says the cardinality actually is. Agent Serve can also suggest relationships, and verified ones are marked on the diagram.

Conformed dimensions

A conformed dimension is a dimension shared across entities — such as Market or Date — so filters line up across tables. Each has a Type (text or date), a grain for dates (day through year), and value maps that reconcile different spellings of the same value.

Drafts and versions

With model drafts on, you change the model in a private draft and publish it when it is ready. Everyone else keeps reading the published model until you do.

Start a draft

The banner at the top of the model page holds your draft. Start draft copies the published model. Start from tables picks up to 50 tables and proposes entities, measures (a row count and sums of numeric columns) and joins (from foreign keys and matching column names), which you then review.

Each person has at most one open draft per team space. Nobody else can see your draft.

Without a draft, saving a change publishes it straight away and records a version. A team space that requires a second approver refuses that save, so start a draft there.

Draft mode

Draft mode decides what your own work reads while the draft is open. With it on, your semantic queries, dashboards, dashboard chat, workbook Semantic cells and the model page read your draft, so you can test a change on real panels before anyone else sees it. Turn it off to see the published model again.

Draft mode never affects anyone else. Work that runs for nobody in particular — workspace API keys, schedules, shared viewer links and Relays running unattended — always reads the published model.

Views

The model page has five views:

You can also work with the model from the terminal: agentserve model pull writes the published model or your draft to agentserve.model.yaml, and agentserve model diff shows what the file would change. See agentserve model.

Publish

Publish draft asks for an optional note ("What changed and why") and publishes your draft as the next version. The draft then closes. Discard draft throws your draft away and leaves the published model unchanged.

An admin can set Publishing approval to Require a second approver under Reviews. Then Publish draft becomes Send for approval: your draft waits, locked, until a workspace admin other than you approves it, which publishes it as the next version, or rejects it, which hands it back to you to keep editing.

Roll back

Roll back on a version publishes that version's model again as a new version, so the history keeps every step. When publishing approval is required, only an admin can roll back.

Who can do what