CSV upload using customer-owned cloud storage (Beta)
CSV upload can now use a customer-owned cloud storage data flow instead of the default data flow through Sigma's infrastructure.
When customer-owned cloud storage is enabled, raw and processed CSV files are staged in a customer-owned bucket (instead of a Sigma-owned bucket) before loading to the data platform. Your company controls the bucket region, access, TTL, etc., helping your organization meet security and compliance requirements.
When exporting to cloud storage, you can now generate files directly in Sigma, instead of in your data warehouse. This allows for more supported file types and data platforms, and more reliable export formatting.
When you migrate a dataset to a data model from the Administration > Dataset migration page, related datasets now correctly show that they have been migrated as well.
You no longer need to wait for a dataset migration to complete before starting another migration from the Administration > Dataset migration page.
You can enable audit logs for tenant organizations. When audit logs are enabled for tenant organizations:
Admin users in each tenant organization can review their own audit logs.
Admin users in the parent organization can review audit logs for the parent organization and each tenant organization with audit logging enabled.
Audit logging is not automatically enabled on tenant organizations, even if the parent organization has audit logging enabled. To enable audit logging in a tenant organization, follow the instructions to open a tenant organization as an admin from the parent organization, then enable audit logging.
Configure a BigQuery connection to use OAuth (Beta)
You can now authenticate to BigQuery from Sigma using connection-level OAuth.
Customer managed keys supported for Google Cloud Platform
Sigma now supports the use of customer-managed keys for all GCP regions, allowing you to use your own key management services to encrypt the secrets and data that Sigma uses.
View usage details for Sigma Tenants on the Tenants tab of the usage dashboard.
For example, review the following details:
Organization type: Whether the organization is the parent or a tenant.
Organization name and slug
Total queries performed over the last 90 days
User activity over the last 90 days, such as total users and total active users.
Document activity over the last 90 days, such as number created and number queried.
Embed activity over the last 90 days, such as number of embedded documents and number of embed sessions.
Export and materialization activity, such as total exports and total materializations.
Types of connections in each organization.
Only users with access to view usage dashboards in a parent organization can view the Tenants usage dashboard.
Data modeling
Migrate a dataset to a data model (GA)
Create a data model from a dataset and its links by choosing to migrate a dataset. Optionally choose to update documents that reference the dataset automatically.
When you migrate a dataset, the dataset is unchanged and the contents of the dataset are recreated in the data model. You can also track the status of all datasets in your organization.
For more details about how to migrate a dataset and what is and isn't migrated to the new data model, see Migrate a dataset to a data model.
Validate metrics and relationships in a data model (Beta)
Changes made to metrics and relationships in a data model can affect users that use those metrics and related columns in their documents. If you make changes such as changing columns, deleting metrics, deleting relationships, or swapping sources, you can validate content in the data model to prevent breaking documents that use those metrics and related columns.
Use the form element to create a clear interface for user data entry. Create a form manually, or based on an existing input table or stored procedure.
Forms can submit data to multiple data sources at the same time, and trigger action workflows at the time of submission, allowing you to centrally manage user input in AI apps.
The layout of chart tooltips has been improved. Additionally, a new divider line has been added to certain tooltip configurations to make tooltip values easier to read.
New chart tooltip formatting options available
New formatting options are available for chart tooltips:
Show all column names: You can now choose to hide column names in a tooltip. If Sigma detects that hiding a column name reduces a user's ability to discern between tooltip values, the column name is not hidden in the tooltip.
Show multiple series: For bar, line, and area charts, you can now choose to show a single series or multiple series in the chart tooltip.
Workbook features
Manage locales panel no longer displays default workbook locale
The Manage locales panel in Workbook settings no longer lists the workbook's default locale. Only manually added locales and custom translations now display in the Manage locales panel.
Workbooks that have custom translations added to their default locale still display the locale in the Manage locales panel.
You can configure page background color, background images, and widths at the level of individual pages. These settings override workbook layout and theme settings, enabling more customization options.
With the latest Chrome update to version 144, embedded content with the :responsive_height query string parameter in the embed URL could not be scrolled in an iframe.
If you use AI tools to work with Sigma and want to enrich agent behavior or questions with context about officially supported Sigma functionality, the Sigma documentation can now be accessed using the model context protocol (MCP) server at https://help.sigmacomputing.com/mcp.
Single-select and multi-select columns in input tables (GA)
Single-select and multi-select columns in input tables are now generally available, except for on Databricks connections, which don't support multi-select columns.
Use single-select and multi-select columns to enable users to add discrete values as follows:
Single-select: Users can select one value in each row from a predefined list of options. A new selection replaces the existing row value.
Multi-select: Users can select one or more values in each row from a predefined list of options. New selections are added to the existing row values.
You can manually create and manage a list of distinct and repeatable options, or you can populate the list of options from a column in an existing data source or element in the workbook. Values can then be formatted as pills and assigned different colors for visual differentiation and clarity.
You can create and manage data models programmatically using the Sigma API. The endpoints use a JSON representation of the data model to retrieve contents, make updates, and create new data models. For information on the JSON representation, see Create and manage data models from code.
The following endpoints are now available to read, create, and update data models programmatically:
Set up a multitenant architecture with multiple Sigma organizations to centralize governance while supporting self-contained and isolated tenants. You can create tenants in the same region or different regions.
Example use cases for Sigma Tenants include:
Comply with data residency requirements with different tenants in different regions
Fully isolate data for different customers as a managed service provider.
Centralize governance for multiple business units, but isolate the business units from each other.
Different deployment architectures are supported. Deploy content from the parent organization to tenants or from one tenant to other tenants. See Deploy content to tenant organizations.
Sigma Tenants is a premium feature. For more details, see Sigma Tenants.
Reports
Add and manage multiple report headers and footers (Beta)
You can now create and manage multiple headers and footers for each report.
You can now aggregate cells in pivot tables by highlighting them. Previously, this ability was only available in level tables. For both pivot and level tables, you can now select from multiple aggregation methods.
Pick from an existing organization locale when adding a workbook locale
When adding a workbook locale, you can now select from a dropdown of existing organization locales, instead of manually entering a custom translation file.
Write Python code that performs complex tasks like data transformation, data analysis, forecasting, prediction, or retrieve and send data to third-party API endpoints. When writing Python in Sigma, you can also:
Reference data elements like tables, pivot tables, and input tables as DataFrames.
Incorporate user input into your code by referencing control values.
Build tables and charts with the output from your Python code.
Use autocomplete to reference data sources available in your connection.
Import libraries available in your Databricks or Snowflake account.
Run Python code directly on the Python element, or trigger the code to run from an action. Workbooks with a Python element can be exported and embedded. For more details, see Write and run Python code and Python method reference.
Bug fixes
Deployment policies with more than 50 documents no longer error.
When sharing templates from one organization to another, the data sources failed to swap to the correct data source when the data source used OAuth to authenticate to the connection.
Clicking a pivot table subtotal now correctly passes the subtotal/total value and row/column context into actions (e.g., actions that set control values from the selected subtotal).
Use other supported IdPs for Databricks OAuth via OAuth token federation
Using OAuth token federation, you can now use other supported identity providers to authenticate to Databricks. Previously, you could only authenticate with Databricks as your identity provider.
The following sections of the product have been renamed:
My documents is now Documents
Shared with me is now Shared with you
The functionality of these sections remains the same.
User profile
Added warning banner for OAuth token expiration
If you access data from a connection that uses OAuth to authorize you, a banner now appears 3 days before your OAuth session expires. You can sign in from the banner to reauthorize your session and avoid losing access to data.
Workbook elements
Create ad hoc calculations (Beta)
Adding ad hoc calculated rows in pivot tables is now supported. This allow you to perform one-off calculations in a pivot table row, without modifying the underlying dataset or restructuring your pivot table.
The repeated container is a layout element that connects to a data source. For each row in the data source, the repeated container generates a layout card, allowing you to quickly generate identical, dynamic layouts from your data.
The single row container is a layout element that connects to a data source. By selecting a key column and value, you can choose a row from the data source to display inside the container, allowing for dynamic, focused views at individual rows.
Add a value list element to create an organized display of details from a data source. You can customize the value list to show custom formula results, control values, static values, and more. When paired with a single row container, you can create a dynamic list that shows individual records from a data based on user input.
File upload columns, controls, and form fields (Beta)
Use file columns in input tables to upload images, documents, and videos directly to Sigma. You can also use file upload controls to select files and upload them to destination input tables.
File columns can accept the following file types, which can be restricted at the column level or in the control properties, if applicable.
Images: JPEG/JPG, PNG, GIF, TIFF, BMP, WebP, SVG
Documents: PDF, CSV, DOC/DOCX, XLS, XLSX, Pages, Numbers, Keynote, JSON, Text file, XML
You can use the Shape setting on an image element to change the shape of an image uploaded to Sigma. For more information, see Image elements.
Workbook features
Copy input table data when swapping sources and applying version tags (GA)
When changing the connection used by input tables in a document or applying a version tag to a document with an input table, you can copy the input table data to the new connection or tagged version.
You can create warehouse views from a tagged version of a workbook or data model. By creating a warehouse view from a tagged version, you can maintain a stable query for a virtual table in your warehouse, regardless of changes made to the published version. For more information, see Use warehouse views with version tagging.
Bug fixes
Custom page headers now span the full workbook width, instead of matching the selected page width.
Tagging a workbook or data model version updates the owner of the tagged version to the user who tagged the version of the document.
When tagging a workbook version that uses a data model as a source, selecting the checkbox to Allow user to use data sources when they "Save as" resulted in an error: "Error: Cannot grant access to Hidden inodes".
As part of this change, if you select Allow user to use data sources when they "Save as" when tagging a workbook that uses a data model as a source, you must manually grant access on any data models used in the workbook to any users or teams with whom the tagged workbook version is shared.
You can now export to an external stage when configuring ad hoc and scheduled cloud storage exports. For more information, see Export to cloud storage.
Bug fixes
Updated metrics from Snowflake semantic views to use correct metrics syntax when referenced in the formula bar.
When migrating a dataset that contained a SQL statement that used a user attribute to reference a data model, users received an error indicating "There is a cycle in this element's dependencies" and referenced workbooks were not updated.
Sigma now creates edit logs (also known as write-ahead logs or WALs) at the individual input table level and stores each edit log in the same schema as its corresponding input table data.
For non-OAuth connections, edit logs continue to use the same user configurations or service account credentials to access and write to the destination schema. OAuth connections, however, no longer require a service account and instead use the same OAuth credentials to write input table data and the corresponding edit log.
For chart interactions, data is now correctly scoped in the Selection action variable. By including values from all columns relevant to a chart selection and excluding values that are not applicable, this fix addresses formula evaluation errors and unexpected variable output.
The Update row(s) action in a version tagged workbook now references the correct workbook ID (that of the tagged version instead of the published version) to run as expected.
When migrating a dataset, the migration tool attempted to migrate deleted datasets that referenced the dataset.
When migrating a dataset joined to another dataset sourced from SQL, the SQL was not migrated to the new data model.
Enable multiple identity providers for your organization (Beta)
You can now enable multiple identity providers (IdPs) for your Sigma organization. If you would like to enable multiple IdPs for your organization, please contact Sigma support.
Updated authentication method for Snowflake Partner Connect connections
New and existing connections to Snowflake created from Snowflake Partner Connect are authenticated using key pair authentication instead of basic authentication.
Ability to copy bookmarks when duplicating a workbook
The Duplicate a workbook (POST /v2/workbooks/{workbookId}/copy) endpoint now includes the copyBookmarks parameter that determines if saved views (formerly called bookmarks) are copied from the duplicated workbook.
If set to all (available to admins only), every saved view (bookmark) applied to the workbook is copied.
If set to accessible, only personal saved views and those shared with the user initiating the operation are copied.
If not set, saved views are not copied.
Ownership of all saved views in the duplicate workbook transfers to the user initiating the operation.
Data modeling
Column-level security in data models with user attributes (GA)
Set column-level security (CLS) rules in a data model according to the assigned value of a user attribute. Users and team members assigned a user attribute value that matches the value specified in the CLS rule can view the contents of the protected column. Users assigned other user attribute values, or not assigned a user attribute value, cannot view the contents of the protected column.
ConvertTimezone function accepts dynamic arguments
The ConvertTimezone function now accepts a column of IANA time zones in the timezone and from_timezone arguments. For more information, see ConvertTimezone.
User profile
Set up an app for two-factor authentication (GA)
If you use a username and password to log in to Sigma, you can set up an authenticator app to generate two-factor authentication codes instead of having codes sent to your email address.
You can turn off the app-based two-factor authentication at any time, or an admin can reset it, to receive two-factor authentication codes via email instead.
Aggregate totals across higher grouping levels (GA)
The ability to aggregate totals across higher grouping levels is now generally available. When displaying subtotals in your pivot table, you can now change whether the row subtotals are aggregated and displayed just for the immediate parent pivot rows, or also displayed at higher grouping levels.
Reference multi-select control values in custom SQL
You can now reference the selected values of a multi-select list values control in custom SQL queries. The selected values can be used to filter results in subqueries and CTEs, combined with formulas like ArrayLength, and more. For more information, see Reference multiple values from a multi-select list in SQL.
Set heavier group dividers in pivot tables
When formatting pivot tables, you can now turn on heavier horizontal and vertical group dividers to make the distinction between groups clearer.
Ask Sigma supports data model relationships and Snowflake semantic views
When Ask Sigma responds to questions with a data model or Snowflake semantic view, Ask Sigma can join related tables to provide higher-quality answers.
Ask Sigma now supports asking follow-up questions about your data. After you ask a question in Ask Sigma, you can continue the conversation, asking Ask Sigma to continue the analysis or change the analysis. To start a new conversation, click Reset.
As part of this change, you can no longer pass a prompt to Ask Sigma using a query string parameter and
share questions in a custom URL.
If you have an AI provider configured to use a Databricks connection, or to use Gemini as an external AI provider or through a BigQuery connection, the model version used by Ask Sigma and other AI features has been updated:
Databricks connections now use databricks-claude-sonnet-4-5
BigQuery connections now use Gemini 2.5 Flash
Gemini as an external AI provider now uses Gemini 2.5 Flash
Data models included in the response for the List files and List member files endpoints
The List files (GET /v2/files) and List member files (GET /v2/members/{memberId}/files) endpoint includes data models in the response. Data models are listed with a type of data-model and datasets are listed with a type of dataset.
New options for Lookup a connection and Sync a connection by path endpoints
The Look up connections by path (POST /v2/connection/{connectionId}/lookup) and Sync a connection by path (POST /v2/connections/{connectionId}/sync) endpoints include the option to look up or sync a stored procedure object in your connection.
Unpaginated responses from list endpoints (Deprecated)
This deprecation was previously announced in Sigma's release notes on October 3, 2025. This updated announcement includes an official end of support date.
Returning unpaginated responses from list endpoints is now deprecated. On June 2, 2026, this functionality will reach end of support and the following list endpoints did not return a paginated response will only return a paginated response:
If you use these endpoints, update your API requests to include the limit query parameter to return a paginated response. After the end of support date, requests without the limit parameter return a paginated response of the default page size (50). If you are already using the paginated response from list endpoints, no action is needed.
Admin
Turkish now supported as a workbook locale
You can now set Turkish (tr-tr) as your workbook locale. Apply the Turkish language, date format, and currency to workbook previews and embedded workbooks.
Datasets are now deprecated. On June 2, 2026, datasets will reach end of support and creating new datasets and editing existing datasets will no longer be available. Migrate existing datasets to data models, and update any documents that use datasets as a source to use data models instead.
Migrate a dataset to a data model (Beta)
Create a data model from a dataset and its links by choosing to migrate a dataset. Optionally choose to update documents that reference the dataset automatically.
When you migrate a dataset, the dataset is unchanged and the contents of the dataset are recreated in the data model. You can also track the status of all datasets in your organization.
For more details about how to migrate a dataset and what is and isn't migrated to the new data model, see Migrate a dataset to a data model.
Embeds
Securely embed data models (Beta)
If you securely embed Sigma with a JWT-signed URL, you can embed Sigma data models into your client application. All JWT claims and embed query string parameters are supported for embedding a data model.
The URL structure for embedding a data model is the same as embedding a workbook. Use the following URL structure to embed a data model:
Aggregate totals across higher grouping levels (Beta)
When displaying subtotals in your pivot table, you can now change whether the row subtotals are aggregated and displayed just for the immediate parent pivot rows, or also displayed at higher grouping levels.
Auto-update page anchor names in the navigation element
When the name of a page anchor is changed, the names of any associated navigation options in a navigation element now automatically update to match the new name.
Change divider stroke styles
You can now change the Stroke style for divider elements to Solid, Dashed, or Dotted.
You can use the navigation element to display a list of destinations users can visit. The navigation element shows each option as an individual button, which you can configure to send users to a workbook page, workbook element, or external link when clicked. Submenus allow you to nest additional navigation options under a top-level option. See Use the navigation element to guide user exploration.
Select all search results in list and hierarchy filters and controls
When using search in a list or hierarchy filters and controls, you can now select all values from the search results.
Workbook features
Conditional background colors for containers
You can configure formatting rules that conditionally change the background color of a container. For more information, see Style a container.
Create and filter hierarchies (Beta)
Use hierarchies to group columns categorically and define the order of data granularity. When you create a hierarchy, you can:
Define the order of the hierarchical data.
Easily visualize all parts of the hierarchy together in a pivot table or grouped table.
Format all levels of the hierarchy consistently, such as when applying conditional formatting.
If your hierarchical data is ragged, Sigma visualizes the ragged hierarchy, letting you view your hierarchy in a dense layout instead of empty rows like a non-ragged hierarchical view. For more details about creating a hierarchy column, see Work with hierarchies and the function reference for the RaggedHierarchy function.
After you create a hierarchy, you can filter different levels of the hierarchy using a filter on the data element or with a hierarchy control element. For more details, see Hierarchy control .
Customize page headers GA
You can enable custom page headers to appear on one or more workbook pages. Page headers allow you to repeat contents like titles, filters, or navigation options across multiple pages in a single configuration. Scroll options allow you to create a sticky header that moves with the user as they scroll. See Add custom page headers to a workbook.
Image backgrounds for containers
You can configure background images for containers from an upload, as well as static and dynamic image URLs. For more information, see Style a container.
Legacy workbook layout (Deprecated)
The classic or legacy workbook layout is deprecated. On March 3, 2026, editing of workbooks with legacy (non-grid) layouts will be disabled. On June 2, 2026, this functionality will reach end of support and workbooks will be automatically upgraded when the workbook is opened. You must upgrade workbooks to grid layout.
Worksheets and dashboards (Deprecated)
Worksheets and dashboards are now deprecated (dataset worksheets continue to be supported). On March 3, 2026, editing of worksheets and dashboards will be disabled. On June 2, 2026 this functionality will reach end of support and existing worksheets and dashboards will no longer be available. To ensure continued access to your content, convert worksheets and dashboards to workbooks .
Bug fixes
For a data element sourced from a grouped table with one or more grouping levels collapsed, source columns were unavailable to select instead of being available.
When a data model was embedded, users only had the option to rename a data model from the list of documents instead of from the document menu for the data model.
When a page was duplicated that contained a data element with a data model metric and the element source was located on the same page, the metric displayed an "Invalid Query" error instead of data calculated by the metric.
When sharing workbooks across organizations, users received an "Object Does Not Exist No matching record" error when attempting to replace the source of the shared workbook with a dataset.
When configuring a Snowflake connection, you can add a PKCS#8-formatted key file (.p8) instead of pasting your private key when setting up key pair authentication for the connection or an OAuth service account.
Audit log support for Azure EU (West Europe) region
Sigma now supports audit log events for organizations hosted in the Azure EU (West Europe) region. For a list of all supported regions, see Enable or disable audit logging.
Enable a unique SAML SP entity ID (GA)
When setting up SAML-based authentication for a Sigma organization, you can now assign a unique service provider (SP) entity ID for the SAML configuration. With the unique entity ID for Sigma as an SP, you can configure your IdP to allow SAML authentication to multiple Sigma organizations.
Improved error handling for non-compliant WAL schema
Sigma now detects when input table edits are unsuccessful due to a non-compliant write-ahead log (WAL) schema. This occurs when a user makes one or more changes to the schema in the data platform, leaving Sigma unable to write data to the WAL.
When this error (wrong schema for WAL table) is detected, Sigma sends an email to admins containing information about the error and a link to troubleshooting guidance. For more information, see Troubleshoot input table connection issues .
Workbook elements
Minimum element size removed
Minimum element size is now a suggestion for all elements. When resizing, Sigma indicates when an element is below the recommended size, but allows you to resize it regardless. Elements below the recommended size might experience minor visual issues depending on the element, contents, and display.
Workbook features
Add CC and BCC recipients to emailed exports
You can now specify CC or BCC recipients in ad hoc and scheduled exports by entering a comma-separated list of email addresses or team names.
Bug fixes
Content validation now updates elements from a data model used in a join.
Content validation was incorrectly performed on tagged versions of workbooks that used an untagged version of a data model as the source, causing those tagged versions to display errors. Tagged versions with errors caused by content validation continue to display errors until they are re-tagged.
The :hide_explore_toggle parameter now hides the Show customize panels option in the element menu.
In some cases, the Edit option in securely embedded content was not functional.
