Sigma is a modern cloud-native business intelligence (BI) and analytics platform that allows organizations to explore, analyze, and visualize data directly from their cloud data warehouses without requiring complex data modeling or extracts. Sigma provides an intuitive, spreadsheet-like interface for building dashboards, datasets, and data models, empowering both business and technical users to collaborate seamlessly.
When you integrate Sigma with Collibra, you bring Sigma’s metadata, including workspaces, dashboards, datasets, data elements, and data source connections, into the Collibra Data Catalog. You can also generate technical lineage (in preview) for Sigma assets, providing end-to-end column-level lineage across your Sigma workspaces.
Only Sigma workspaces and datasets that are accessible through the configured Sigma API credentials are ingested. Restricted or private workspaces without access for the service account are skipped during synchronization.
The integration collects and maintains the latest Sigma metadata and lineage information available through the Sigma API at the time of synchronization.
The resulting assets represent your Sigma metadata model in Collibra, enabling governance, lineage tracking, and cataloging for analytics content created within Sigma.
Sigma considerations and limitations
Before you configure or use the Sigma integration, review the following considerations and limitations. Some limitations apply only to column-level lineage (in preview).
Column-level lineage between Data Models is not supported
Column-level lineage between two Data Models is not supported. The Sigma API identifies cross-Data-Model column references by using display labels, for example, [ElementName/ColumnLabel], instead of stable unique identifiers. Unlike warehouse (Sigma Data Entity) columns, which use stable inode-based identifiers, display label references break when a column is renamed. To ensure accurate lineage, Collibra generates column-level lineage only for the following paths:
- Warehouse → Data Model (Data Entity is part of / contains Data Model)
- Data Model → Workbook Element (BI Report contains / is contained in BI Data Model)
Workbook Element lineage is incomplete when the source Data Model is in an unselected workspace
Workbook Element lineage is generated only for Data Models in the selected workspaces. If a Workbook Element references a Data Model in a workspace that is not selected, Collibra cannot resolve the upstream columns, and no column-level lineage is generated for that Workbook Element. To generate complete lineage, include all workspaces that contain both the consuming Workbooks and their upstream Data Models in the Workspaces filter.
Technical Lineage tab availability
After technical lineage is generated, you can navigate to the technical lineage graph from the technical lineage browser. The technical lineage tab is not yet available for Sigma assets.