Sigma tables overview (Beta)

This documentation describes one or more public beta features that are in development. Beta features are subject to quick, iterative changes; therefore the current user experience in the Sigma service can differ from the information provided in this page.

This page should not be considered official published documentation until Sigma removes this notice and the beta flag on the corresponding feature(s) in the Sigma service. For the full beta feature disclaimer, see Beta features.

Sigma tables are currently free to use in public beta but will be a paid feature when generally available (GA).

Sigma tables are warehouse-native tables you can create, use, and edit directly in Sigma. They’re backed by database tables in your data platform, so edits you make in Sigma are automatically written to the underlying database table. This makes every Sigma table an editable data source, with local Sigma tables being available within the workbook containing it, and organization-wide Sigma tables being shareable across multiple Sigma documents (including workbooks, data models, and reports) and external tools connected to your data platform.

Because Sigma tables are writable, multiple users can contribute to the same table, making Sigma tables the foundation for collaborative apps that capture structured input, manage reference data, and build editable datasets shared across teams and systems.

This page provides an overview of Sigma tables, including how they work, example use cases, and links to related documentation about what you can do with them.

Sigma tables are currently supported by Snowflake, Databricks, and PostgreSQL connections. On Databricks, Sigma tables require Unity Catalog and Delta Lake.

Before users can create, use, or edit Sigma tables, an admin must configure access on relevant connections. See Configure access for organization-wide Sigma tables.

How Sigma tables work

Every Sigma table belongs to a connection. When you add a row, delete a row, change a value, or update the schema, Sigma writes the change directly to the underlying database table in that connection’s data platform.

Since data in a Sigma table is stored as a standard table in your data platform, it can be queried, referenced, and reused by anything connected to your data platform, including Sigma workbooks and external systems. In Sigma, multiple users can simultaneously edit a specific Sigma table in the same workbook or across different workbooks using it. All users with access can see the changes, whether they’re working in the draft or the published version.

Local and organization-wide Sigma tables

A Sigma table you create in a workbook starts as a local table, meaning only that workbook can use it, and it doesn’t appear in the data catalog or in search. When other workbooks or documents need to reference the same data, you can promote the local Sigma table to make it available across your organization. An organization-wide Sigma table appears in the data catalog, and any user with access to the table can add it as a data source in their workbooks, reports, and data models.

A Sigma table you create from an input table, and a connection table you enable write access on, are organization-wide from the start. For more information, see Promote a local Sigma table.

Example use cases

Sigma tables are writable and stored in your data platform, making them an ideal shared, editable data source for multiple teams or systems. The following use cases demonstrate this pattern.

Cross-team planning: In Sigma, Sales Ops enters pipeline projections by region in one app. Finance reviews and adjusts those projections in their own app. Both apps write to the same Sigma table, so when Finance adjusts a projection, Sales Ops sees the updated number in their app.
External system integration: A customer success team logs renewal commitments in a Sigma table. A reverse ETL pipeline running against the data platform reads from the underlying database table and syncs the commitments to the team’s CRM as opportunities. The pipeline reads the Sigma table data the same way it reads any other table in the data platform.
Cross-workbook data sharing: A recruiter enters new hire details in an onboarding workbook. Without requiring a warehouse view or custom SQL, a facilities planning workbook reads from the same Sigma table to assign desks and equipment ahead of each new hire start date.

How to enable Sigma tables

If you’re an admin, configure each relevant connection for Sigma tables, and optionally set up audit logging to track edits in your data platform.

Task	Description
Enable a service account for Sigma tables on an OAuth connection	Use a service account, rather than individual users, to own the underlying database tables. (OAuth connections only.)
Configure access for organization-wide Sigma tables	Ensure users have the data platform and Sigma access needed to create and manage Sigma tables.
Enable write access on a connection table	Make an existing database table editable in Sigma.
Configure audit logging for Sigma tables	(Optional) Keep a history of Sigma table edits, recorded in your data platform.

What you can do with Sigma tables

You can create, use, edit, own, and audit Sigma tables to build and govern shared, editable data sources for collaborative apps and external tools.

	Task	Description
Create	Create a local Sigma table	Start with an empty Sigma table or a CSV file. The table is local to the workbook until you promote it.
	Promote a local Sigma table	Make a local Sigma table available organization-wide so other workbooks, data models, and reports can use it as a data source.
	Create a Sigma table from an input table	Reuse and edit an input table’s data across workbooks, data models, reports, and other tools.
Use	Add an existing Sigma table to a Sigma document	View or edit an existing Sigma table’s data in a workbook, data model, or report.
Use	Add an input column to a table	Capture new data to supplement existing data in tables that are otherwise uneditable.
Edit	Edit Sigma table data	Change cell values or paste new data into an existing Sigma table.
Edit	Use actions to edit Sigma tables	Insert, update, or delete rows in a Sigma table based on user interaction or automated triggers.
Own	Modify a Sigma table’s schema	Add, rename, or delete columns, or rename a Sigma table.
	Change a Sigma table primary key	Use columns from your own data to uniquely identify rows in a local Sigma table.
	Use version tagging with Sigma tables	Tag a workbook that contains local Sigma tables, and choose whether each table’s data carries over to the tagged version.
	Grant access to a local Sigma table	Allow others to edit or own a local Sigma table.
	Grant access to an organization-wide Sigma table	Allow others to use, edit, or own an organization-wide Sigma table.
Audit	Audit changes to Sigma tables	Identify who made a specific data or schema edit, when it occurred, and what it changed.