TattvaDocs
Core concepts

Workspace library

The shared definitions and sources every project in your workspace uses, curated by your data analysts.

The Workspace Library holds the definitions and sources your whole company should share: what "net revenue" means, which table is the source of truth for orders, how the financial year runs. Every project uses it, so two teams asking the same question get the same number.

Your data analysts curate it. Everyone else uses it, and can propose changes.

Workspace Library

Why it exists

Without a shared library, every project defines "net revenue" on its own. One subtracts returns, another also subtracts discounts, a third forgets cancelled orders. The quarterly review then spends an hour reconciling three numbers that should have been one. The library gives you one definition, owned by named people.

Where to find it

Sidebar → Ontology → Make → Workspace Library.

The page lists what is published, in draft, and deprecated. Tabs:

  • Metrics: the shared metric definitions. Search by name, formula or alias, and filter by kind and importance. Each row shows the metric, its definition, formula, kind, importance and status.
  • Concepts: shared business concepts, such as what counts as a new customer.
  • Conventions: shared rules, such as the financial year or currency.

In a normal project the library is read-only. Data analysts edit it from the workspace's library project, which appears in the workspace switcher as Workspace Library for those allowed to curate it.

What your project gets automatically

  • Metrics, concepts and conventions from the library. Answers use them unless your project overrides one.
  • Workspace sources, marked with a Workspace chip on Sources. If one is not relevant, hide it; Hidden sources brings it back.
  • Seeded skills, the platform's built-in analyses.

What stays inside your project: your own uploads, trackers, goals, decisions, boards and reports.

When the library definition doesn't fit your project

Sometimes a project really does need a different definition. For example, a growth team may count a "new customer" over 90 days, while finance counts first-ever purchases.

In the Metrics tab, click Override on the row. Enter the Formula (project version) and Description (project version), then Save override. The override is submitted for review. An Ontology Admin accepts or rejects it; until then your project keeps using the library definition. Once accepted, your project uses its own version; the library and every other project are unchanged. The row's status shows a pending marker while the override waits for review.

The Override column appears for workspace admins and Ontology Admins. If you don't see it, ask one of them.

Override sparingly

Two projects using two definitions of net revenue will not reconcile. If your version is better for everyone, ask a data analyst to change the library instead.

Share a source with every project

If you uploaded a source every project should use, open it on Sources and click ↑ Promote to workspace. Give a reason and Submit request. The request goes to the Promotion Inbox (Ontology › Maintain › Promotion), where a data analyst approves or rejects it.

See Use the workspace library for the full steps.

Who curates the library

Members with the Ontology Admin role, and workspace admins. They approve promotion requests, review new definitions, and edit library metrics. See Workspaces & members and, for their day-to-day work, For data analysts.

Tips

  • Trust the library. If an answer uses a library metric, the definition has been reviewed.
  • Check your overrides now and then. An override written six months ago may no longer be needed.
  • Promote, don't copy. If a source already exists in the workspace, use it instead of uploading your own copy.
Workspace library — Tattva Docs