Sigma
Sigma
Catalog your Sigma workbooks, reports, data models, and datasets - and trace elements and columns back to the warehouse tables that power them.
Overview
Catalog your Sigma workbooks, reports, data models, and datasets, and trace how data flows between Sigma elements and back to the warehouse tables and columns that power them.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Authentication | ✓ | API Client Credentials (Client ID and Client Secret) |
| Catalog Discovery | ✓ | Folders, Workbooks, Reports, Data Models, Datasets, Elements, Columns |
| Table-level Lineage | ✓ | Links Sigma elements to the elements they source from, and Custom SQL elements to upstream warehouse tables |
| Column-level Lineage | ✓ | Parses Custom SQL to trace columns to warehouse columns, and column formulas to trace columns to other elements' columns |
| Supported Warehouses | ✓ | Snowflake |
| Usage Statistics | — |
Prerequisites
Before connecting Sigma, you need:
- A Sigma account with Admin privileges, to create API client credentials
- A Snowflake asset already connected in Matia - this is required to enable lineage between Sigma and your warehouse
What gets cataloged
Matia syncs the following Sigma objects into your catalog:
| Sigma Object | Cataloged as | Notes |
|---|---|---|
| Folder | Asset | Nested folder hierarchies are preserved |
| Workbook | Asset | Holds the workbook's elements |
| Report | Asset | Holds the report's elements |
| Element | Asset | Tables, pivot tables, visualizations, and Custom SQL elements within a workbook, report, or data model |
| Column | Field | Carries its Sigma formula and data type |
Elements that share a name within the same container are given a unique suffix, so each one gets its own catalog page. For example, Sigma names every new SQL element "Custom SQL" by default, so a workbook with several of them will show each one separately in the catalog.
The resulting lineage chain in Matia runs:
Warehouse Table → Custom SQL Element → Element (workbook or data model) → Element
Column-level lineage narrows this further, in two ways:
- Custom SQL - Matia parses the SQL behind each Custom SQL element to link its columns to the specific warehouse columns they select.
- Column formulas - When a column's formula references another element's column (for example,
[Orders/Revenue]), Matia links the two columns.
Next Steps
- Setup Guide — Connect Sigma
- Release Notes — See recent changes