Build shared context with your team

Shared data understanding often lives partly in version-controlled models and partly in informal communication. You can store structured documents in the workspace that describe table relationships, ownership, and conventions. These documents are available alongside query context and can be listed and updated as your team’s understanding evolves.

How it works

Step 1 — Publish the shared map

Generate the workspace data model file, then publish it so the whole team shares one map of tables and joins.

Step 2 — Add workspace-specific context for the team

We keep internal notes on who owns metrics and naming rules—publish those next to the shared data model so teammates see both.

Step 3 — Confirm both documents are live

List what’s published, then show the data model and the team notes so I can confirm both are there.

Who uses this

• Platform leads publishing a central data model while workspaces add local rules.
• Product analytics groups recording metric ownership at workspace scope.
• Hosts passing both schema-oriented and team-policy context into agents or codegen.