Passing multiple SAML userRole values is now supported
When configuring SAML, it is now possible to pass in multiple userRole values. The first valid account type in the list of userRole values will be assigned. See Configure your IdP in Set up single sign-on with SAML.
Workbook features
Transpose a table (Beta)
Transposing a table is now supported from rows to columns or columns to rows. This feature allows you to pivot or unpivot data according to your use case.
Limit the number of values displayed in a grouped table, pivot table, or chart, and group the remaining values in an "Others" category. You can transform an existing column or use the VisibilityLimit function with a sorted table.
Custom totals and subtotals for pivot tables and grouped tables (GA)
In a pivot table or grouped table, you can change the way that totals and subtotals are calculated by choosing to change the aggregate used for a subtotal, or modifying the formula for a grand total or subtotal directly.
With this update, the default names of subtotals and totals update to Column Name total for subtotals or Grand total for totals. You can change the label of any subtotal or grand total.
After deactivating a SCIM user, the folder created to contain the deactivated user's documents no longer includes a UUID and matches the behavior described in Deactivated user documents.
When revoking access to a connection, database or catalog, schema, table, or stored procedure in Sigma, you can now only revoke access from the level to which the access was granted.
When a user has inherited access to a document from a version-tagged folder, the version tag is now shown in the Share Workbook or Share Data Model modal.
When sharing a workbook, version tags now appear for all access levels as expected.
When a user has access to specific version tagged documents in a folder, you can now grant access to all versions of documents in the Share Folder modal.
Allow users with View license to ask natural language queries with Ask Sigma
The Use Ask Sigma permission can now be enabled for users with the View license (or Lite license). See Account type and license overview. No existing account types were changed. To enable Ask Sigma for users who did not previously have access, update their account types to add the permission.
To continue analysis in a workbook, a user's account type must also have the Create, edit, and publish workbooks permission enabled.
Allow users with View license to browse connections
The View connections permission can now be enabled for users with the View license (or Lite license). See Account type and license overview.
Users with this permission enabled on their account type can view database or catalog, schema, or table names that they have access to. This permission does not grant access to data in connections. See Manage access to data and connections.
New permission for calling stored procedure actions
Manage which users can call stored procedure actions from a workbook with the Call stored procedure actions permission. The permission requires an Act or Essentials license. For more details, see Account type and license overview.
Input table support on BigQuery connections (Beta)
Input tables are now compatible with BigQuery connections. The dynamic workbook elements support structured data entry, allowing you to integrate new data points into your analysis and augment existing data from your data platform.
For more information about input tables and how to use them, see the following documentation:
Use the Update row and Delete row actions to modify input tables. Update row allows user interaction to update values in an existing row, while Delete row removes an entire row. These actions are designed to support form functionality but can be used in other ways to accommodate different data app use cases.
Use multi-select columns in input tables to enable users to add one or more discrete values to a single cell. You can create and manage a predefined list of custom values or choose an existing data source or element in the workbook to populate the list. Values are displayed as individual pills and can be assigned different colors for visual differentiation and clarity.
Add custom context menu items in tables, pivot tables, input tables, and charts to provide clear, discoverable triggers for actions relevant to selected cells and data points. You can add standalone menu items or create nested submenus that execute any action effect, including calling stored procedures, generating iframe events, and opening modals.
Data models provide a semantic layer for your data, letting you organize and store data in a structured governed way without modifying raw data. You can create and manage reusable data elements with visual semantic modeling in an entity relationship diagram, empowering business users to independently model and explore data.
Add relationships between tables in a data model to enable business users to work with related data without performing ad hoc joins. A relationship defines the join logic for Sigma to use to join the tables, making the columns from both tables available to the source table for analysis and exploration on demand. When a user analyzes the source table in a workbook and adds a related column, Sigma performs the join.
Relationships between data model tables only support many-to-one or one-to-one joins, and are not automatically created between tables from a connected data source, even if the table has primary and foreign keys defined.
Newly available functionality:
Use related columns in data models
Add relationships to elements disabled as a source
Adding metrics to data models is now generally available. Metrics are dynamic and reusable calculations that are specific to a data source. As such, metrics usually reference specific columns. Create a metric to provide reliable and efficient aggregate calculations, abstracting complex formulas away from business users.
When defining a metric on a data model, you can reference other metrics in your formula. Metrics propagate downstream, so a metric defined on one data model is also available to any data elements that use that data model as a source.
Applying column-level security (CLS) to elements in data models is now generally available. Column-level security restricts access to column-level data, ensuring that sensitive and confidential information is secure and accessible only to authorized users. Configure CLS in a data model element for specific users or teams.
Updated behavior when targeting a data model source parameter from a workbook control
When passing values from a workbook control to a data model, you no longer need to target the source parameter with a specific data model table element. Instead, you can associate a control element in the workbook with a control element in the data model itself.
Existing workbook control elements that target data model elements with source parameters continue to work.
When you publish a data model with changes that could break downstream elements, you are now prompted to map changed columns to prevent errors such as Unknown column [columnID] or Column [ColumnID] does not exist.
When chatting with a Sigma support engineer, you can now click and drag the handle on the top left corner of the live chat window to move it to a more convenient location on your screen. This helps you more easily interact with Sigma Support and access key parts of your screen at the same time.
Add shortcuts to documents (GA)
If you want to save links to documents in more than one location, you can add a shortcut. Use shortcuts to make specific data sources easier to find in the source picker, or to organize documents to make key workbooks and data models easier to access.
When working with data elements in data models and workbooks you can organize columns into folders, letting you nest columns into relevant groups. Folders that you create in a data model or parent element are available to downstream elements, like a data element that uses a data model as a data source, or a child element.
Use popovers to display information in containers anchored to specific elements. Popovers allow you to present relevant content (tables, charts, controls, etc.) only when needed, creating a more efficient and simplified workbook interface.
More precise formatting of grand totals and subtotals
You can now format the grand totals and subtotals of a pivot table or grouped table separately from other values in the column. For example, format the grand total row of a pivot table to display numbers in SI units, while the values columns display whole numbers.
When adding date data in an input table, the format of the data now respects the locale of the Sigma organization. For example, if your Sigma organization uses a locale of English (Great Britain) and you paste a date value of 10.05.2025 into an input table, the date correctly appears as May 10, 2025.
When adding a version tag to a data model and swapping sources from one connection to another in cases where the table is available at a different path in each connection, the data sources no longer fail to swap with the error "Failed to find the table in connection".
Users in an embed can no longer open the source of a data model.
SAML configuration values now available in Administration portal
When setting up single sign-on with SAML, you can now copy and paste your SAML configuration values (e.g. prefix, RelayState) from the Administration portal. Go to Administration > Authentication > Edit, and your configuration values will be available under Authentication Method & Options. Your prefix will already be included in any relevant fields.
If users attempt to run a query with OAuth credentials that do not exist, they are now shown an improved error message.
When sharing a template containing input tables across organizations, the input table data entry permissions in the shared template now matches what was defined in the source document.
Admins who create teams are no longer automatically added as members of that team. Teams now start empty, allowing the admin to choose whether or not to include themselves as a member.
Data apps
Copy and paste actions and sequences
Copy and paste individual actions or entire sequences to easily reuse action configurations across your organization. You can paste a copied action or sequence to the same element, a different element in the same workbook, or an element in a different workbook.
In the action or sequence menu, click Copy action or Copy sequence, then use the Paste action within (a sequence), Paste action below (another action), or Paste sequence option to paste the configuration to a specific location.
Prevent whitespace from triggering actions
By default, actions configured on charts can be triggered when a user clicks on whitespace within the element. You can disable this to prevent unwanted initiation of actions.
In the Actions panel, click More and select Allow whitespace to trigger actions. If there is no checkmark displayed on the setting, whitespace is disabled as a trigger.
Workbook elements
Change to underlying data grouping for cartesian charts
Previously, underlying data was grouped for cartesian charts (bar, line, area, scatter, combo, box, and waterfall charts) regardless of whether the chart values were aggregated. With this update, when viewing underlying data, the grouping will match the chart aggregation. For example, if Aggregate values is unchecked, the underlying data is not grouped.
Set up dependent materialization schedules in workbooks and data models. If you materialize both parent and child elements in a workbook or data model, you can set up materialization schedules that include child elements to run after the parent materialization schedule completes.
This functionality is not available for dataset materializations.
Export from Amazon Redshift connections to S3 buckets (Beta)
You can now export data from a Redshift connection to an Amazon S3 bucket. For more details, see Export to cloud storage (Beta).
Updated user requirements for creating shared views
The ability to share saved views is now limited to users who are assigned account types with the Create, edit, and publish workbooks permission enabled. Users who are assigned account types with the Full explore permission enabled (without Create, edit, and publish workbooks) can create and save custom views but cannot share them.
Existing shared views will remain shared regardless of the account type assigned to the user who created them. For more information about saved views, see Create and share saved views.
Bug fixes
Dynamic text in text elements now correctly displays line breaks (newline characters) and whitespace characters (tabs or spaces).
In OAuth-enabled embedded workbooks, OAuth connections are no longer disabled when external OAuth tokens are passed in an embed URL.
When an action sequence on a chart has a condition referencing the Selection variable, triggering the sequence by clicking whitespace on the chart no longer generates an error.
When an action sequence is configured with the On select trigger type for a column, the sequence is no longer initiated when a user clicks the column header.
The Update member (PATCH /v2/members/{memberId}) endpoint includes two new options to better manage scheduled exports when deactivating a user:
Set archiveDocuments to true to archive all documents associated with a user that you deactivate, including scheduled exports associated with those documents.
Set archiveScheduledExports to true to archive only the scheduled exports associated with the documents owned by the deactivated user.
Admin
Require all email exports to run as recipient
Sigma admins can now choose to require all email exports to run queries as recipients. After enabling this setting, all new and modified email export schedules run queries as the recipients. For more details, see Manage export frequency and authentication settings.
Data modeling
Materialization support for version-tagged data models
Customize the styling of data elements such as tables, input tables, visualizations, and UI elements. Add or remove padding, change the corner style, add a border, and change the text alignment for text elements.
Set default styles in an organization theme, customize styles for an entire workbook in the workbook settings, or style individual elements.
Authenticate secure embeds using JSON Web Tokens (JWTs) (GA)
Sigma supports authenticating secure embeds using JSON Web Tokens (JWTs). JWTs are compact, URL-safe tokens that can be digitally signed, ensuring that the data they contain is tamper-proof. Using JWT-signed URLs for your embeds offers several advantages, including offering a secure way to embed content that can be accessed by both external users and internal users.
The URL parameters hide_menu and hide_folder_navigation are now supported in secure embed URLs signed with JWTs.
Scheduled materialization bypass on Snowflake connections
When using materialization with a Snowflake connection, Sigma detects data updates in materialized elements in workbooks and data models. If the underlying data hasn’t been updated since the last successful materialization, Sigma bypasses the scheduled materialization to reduce unnecessary compute time and costs.
Add the legend control element to your workbook to target multiple charts with one legend and align colors across charts. The legend control functions as an interactive legend, letting you filter and highlight corresponding data points in targeted charts. Any categories not represented in the list are collected as an extra category, "Others", which can be turned off.
Use the Clear control action to bulk clear all controls in a tabbed container element or a specific tab. When configuring the action, select the tabbed container element, then choose the All tabs option or select a specific tab that contains the controls you want the action to clear.
Materialization with Snowflake dynamic tables (GA)
Materialization with Snowflake dynamic tables is now generally available (GA). If your Sigma organization has a Snowflake connection, you can configure materialization to use dynamic tables for materialization. New connections to Snowflake use dynamic tables for materialization by default.
Three separate feature permissions now allow admins to configure which account types can use AI features.
The Explain charts with AI feature permission allows users to see and use the Explain this chart option on any visualization. This feature permission is available in the Act license tier in the View/Act/Analyze/Build license model and in the Essential license tier in the Lite/Essential/Pro license model.
The Use AI with formulas feature permission allows users to use the AI-powered formula assistant to write new formulas, correct formula errors, and explain existing formulas. This feature permission is available in the Analyze license tier in the View/Act/Analyze/Build license model and in the Pro license tier in the Lite/Essential/Pro license model.
The Use Ask Sigma feature permission allows users to ask natural language queries with Ask Sigma. This feature permission is available in the Build license tier in the View/Act/Analyze/Build license model and in the Pro license tier in the Lite/Essential/Pro license model.
The use of AI-powered features also requires an admin to configure an AI provider for the organization.
You can now apply column-level security (CLS) to elements in data models. Column-level security restricts access to column-level data, ensuring that sensitive and confidential information is secure and accessible only to authorized users. Configure CLS in a data model element for specific users or teams.
You can now add metrics to data models. Metrics are dynamic and reusable calculations that are specific to a data source. As such, metrics usually reference specific columns. Create a metric to provide reliable and efficient aggregate calculations, abstracting complex formulas away from business users.
When defining a metric on a data model, you can reference other metrics in your formula. Metrics propagate downstream, so a metric defined on one data model is also available to any data elements that use that data model as a source.
Data elements in data models and workbooks that were materialized before April 1, 2025 might not work with metrics. If columns that use metrics produce an Invalid Query error, and the table or an upstream table is materialized, manually re-run the materialization. If the error persists, contact Sigma Support.
Add relationships between tables in a data model to enable business users to work with related data without performing ad hoc joins. A relationship defines the join logic for Sigma to use to join the tables, making the columns from both tables available to the source table for analysis and exploration on demand. When a user analyzes the source table in a workbook and adds a related column, Sigma performs the join.
Relationships between data model tables only support many-to-one or one-to-one joins, and are not automatically created between tables from a connected data source, even if the table has primary and foreign keys defined.
The ArrayExcept function returns an array of all unique elements from one specified array not included in another specified array. The output array is unordered.
After you receive an initial answer from Ask Sigma, you can continue your exploration. Ask Sigma provides related charts underneath its primary answer to offer avenues to analyze related data.
Ask Sigma now supported in secure embeds signed with JWT (Beta)
Secure embedding with JWTs now extends to the Ask Sigma page. Embed Ask Sigma in your own application to offer your end users the ability to ask natural language queries of the data they have permission to access. Apply custom theming and remove Sigma branding for seamless integration.
Custom totals and subtotals for pivot tables and grouped tables (Beta)
In a pivot table or grouped table, you can change the way that totals and subtotals are calculated by choosing to change the aggregate used for a subtotal, or modifying the formula for a grand total or subtotal directly.
With this update, the default names of subtotals and totals update to Column Name total for subtotals or Grand total for totals. You can change the label of any subtotal or grand total.
Tagging a data model with a CSV uploaded no longer results in an error.
Secure embed users no longer see an “Invalid Databricks access token” error when accessing a workbook with OAuth credentials on a Databricks connection.
X-axis labels in trellis charts now display correctly when the y-axis title is displayed ( Format > Y-Axis > Axis title) and shared x-axis is enabled (Format > Trellis > Shared > X-Axis).
The home page header has been redesigned to match the recently updated workbook and data model UI. The change is aesthetic and does not impact any functionality. The new updated homepage header has rolled out for some organizations, and will continue to be incrementally rolled out over the coming weeks.
Workbook elements
Input tables now supported on Amazon Redshift connections (GA)
Input tables are now compatible with Amazon Redshift connections. These dynamic workbook elements support structured data entry that allows you to integrate new data points into your analysis and augment existing data.
For more information about input tables and how to use them, see the following documentation:
If you want to remove an element as a target of a control, you can now detach the control from the element from the element's filter menu.
Bug fixes
Materialization schedules owned by users deactivated after March 25, 2025 transfer to the admin performing the deactivation, or if specified, the user chosen to receive the deactivated user's documents. Materialization schedules owned by users deactivated prior to that date fail to run and materialized elements might display an error.
On the Developer access page in the Administration portal, the owner of each set of developer credentials is now identified by email instead of by user name. As a result, admins can now determine which API token is assigned to whom when there are multiple users with the same user name.
API
Allowlist IP addresses for API access (GA)
Restrict access to the Sigma API for your organization by adding IP addresses and IP address ranges using CIDR notation to an allowlist. With an allowlist configured, only users making API requests from allowed IP addresses can make successful requests.
The following endpoints are now available in a v2.1 version. The new version uses pagination for the API response by default, allowing you to retrieve large responses in manageable segments.
The equivalent endpoints in v2 continue to work, but might not use pagination by default for all customers.
New option for Export data from a workbook endpoint
When exporting an entire workbook or workbook page using the Export data from a workbook (POST /v2/workbooks/{workbookId}/export), the format parameter now supports the xlsx option to support the Excel file format.
Bug fixes
Users are no longer signed out of Sigma if they attempt to run a query with OAuth credentials that do not exist.
For connections that use OAuth, users can now see and use stored procedures that they have access to.
Add a tabbed container to your workbook pages when you want to offer multiple sets of content in the same section of your workbook canvas. A tabbed container has multiple tabs at the top of the container, which can either be visible or hidden for end users. By placing content on different tabs and configuring logic about which tab should display, you can allow users to experience different views in the same space without scrolling or navigating elsewhere.
You can now change the density of the grid within a container or tabbed container element. By default, a container's grid has twelve horizontal grid spaces, which expand and contract to fit the container size. Using the new Column density setting, you can opt to configure a lower or higher density, depending on your layout. Higher density gives you a finer grain of control over element positions in large containers.
Use the Update row and Delete row actions to modify input tables. Update row allows user interaction to update values in an existing row, while Delete row removes an entire row. These actions are designed to support form functionality but can be used in other ways to accommodate different data app use cases.
Create an action to display a specific tab in a tabbed container element. Configure these actions based on user actions and optional conditions to customize what your tabbed container displays. The tabs in a tabbed container can be visible or hidden from the end user. If they are hidden, the Select tab action is the only way to display tabs other than the default tab.
When a table, input table, or pivot table with conditional formatting is exported as an XLSX-formatted (Excel) file, the conditional formatting is retained. Conditional formatting includes single color, color scale, and data bar formatting.
Bug fixes
In secure embeds that use OAuth to access data, new embed users no longer need to reload the embed to clear a "no valid refresh token" error. Instead, the embed loads for a newly-created embed user on the first try.
API endpoints that return information about tagged workbook versions now return an accurate sourceWorkbookVersion. Previously, the API returned the highest sourceWorkbookVersion even in cases where a lower sourceWorkbookVersion had been tagged more recently.
