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.
Sigma's license model now includes four tiers: View, Act, Analyze, and Build. This structure applies to all organizations created on or after March 4, 2025. Organizations created prior to this date will continue using Lite, Essential, and Pro license tiers and will be scheduled for a license migration at a later date.
AI features have been split into separate permissions as opposed to requiring a Use AI features permission in the highest license tier. The Use AI features permission has been removed.
All users with Basic explore permissions now have access to the Explain this chart functionality.
All users with Full explore permissions now have access to the AI-powered formula assistant. Users can ask AI to explain what is happening in an existing formula, or ask AI to write a formula for them.
The use of these AI-powered features also requires an admin to configure the OpenAI integration for the organization.
When accessing the Sigma public API documentation, you can request an API token from any endpoint documentation page, instead of first accessing the Get access token documentation page.
The endpoint for retrieving a token and refreshing an existing token is unchanged. This is not a code change to the API.
New option for List workbook pages for a workbook and List elements in a workbook endpoints
You can now retrieve pages and elements for a saved view, formerly known as a bookmark, using the API.
The List workbook pages for a workbook (GET /v2/workbooks/{workbookId}/pages) endpoint and the List elements in a workbook (GET /v2/workbooks/{workbookId}/pages/{pageId}/elements) endpoint now include the bookmarkId query parameter.
New writebackSchemas options for Create a connection and Update a connection endpoints
When adding a Snowflake or Databricks connection that uses OAuth with the Create a connection (POST /v2/connections) endpoint or updating one with the Update a connection (PUT /v2/connections/{connectionId}) endpoint, you can use the new writebackSchemas option to provide multiple write-back schemas for the connection to use.
Multiple write-back schemas helps keep content created by different teams or users with different permissions in different schemas.
Search and discovery
Shared view limitations
Each workbook is now limited to 10 shared views (previously known as shared bookmarks). If a workbook has version tags, the limit applies per tagged version. There is no limit on the number of personal saved views (personal bookmarks) per workbook.
Organizations with more than 10 existing shared views will be able to keep their existing shared views, but not be able to make more.
Workbook elements
Legend control element (Beta)
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.
Redesigned user interface for workbooks and data models
The workbook and data model UI has been redesigned to simplify the creation experience in Sigma. The redesign includes the following changes:
A unified header: A simplified header and new menu that consolidates the available workbook and data model options for easier access.
New ways to create and edit elements:
An Add new element bar where you can add elements at any time.
A simplified editor panel with tabs to access element properties, format, and actions.
For an overview of the new workbook UI, see Navigating a workbook (link).
Views: Views include custom views and saved views. Custom views allow you to explore and make changes to your workbook, without affecting the published or tagged version of your workbook. Saved views replace bookmarks, and allow you to return to changes you’ve made on top of a published workbook at any time.
To learn how to create custom views and leverage them for ad hoc data analysis, see Create custom views.
The new UI has been rolled out for all new Sigma organizations, and will continue to be enabled in a multi-stage rollout for all existing organizations.
Call stored procedures defined in a Snowflake, BigQuery, or Amazon Redshift connection using an action. If the stored procedure returns non-tabular results like a string, number, or Boolean value, you can work with the output as an action variable. With this release, you can also grant users and teams access to use existing stored procedures from a specific schema without granting those users access to the entire connection.
For example, if you have an existing stored procedure in your data platform that you use to perform a complex calculation, rather than recreating the logic in a Sigma custom function or formula, you can call the stored procedure and use the output in Sigma.
Interactive chart legends support map and funnel charts
Map and funnel charts that have a color by category set support the following interactive filtering capabilities in the legend:
Hover over a legend entry to highlight corresponding data points.
Click a legend entry label to isolate corresponding data points.
Select or clear the checkbox of one or more legend entries to show or hide corresponding data points.
Click anywhere (within the element) outside of the plot area or legend to reset the chart display.
Keyboard shortcut for cell selection
When you select a single cell in a table, you can add adjacent cells to the selection using the keyboard shortcut ⌘+⇧+arrow (Mac) or ctrl+⇧+arrow (Windows).
Bug fixes
Actions with conditions based on hidden columns now trigger as expected.
The Workspaces page no longer displays a "Too many results resolved" error when attempting to load a very large number of workspaces.
The List workbooks (GET /v2/workbooks) endpoint now includes the excludeExplorations query parameter to be used with the skipPermissionCheck query parameter to exclude explorations from the response.
For example, if an admin wants to return all workbooks in an organization, but exclude ad hoc explorations, they could send a GET request to https://api.sigmacomputing.com/v2/workbooks?skipPermissionCheck=true&excludeExplorations=true.
New filtering options for List connections and List user attributes endpoints
The following endpoints now support optional query parameters to allow you to filter the results:
The List connections (GET /v2/connections) endpoint now includes the search query parameter.
The List user attributes (GET /v2/user-attributes) endpoint now includes the name query parameter.
Workbook elements
Copy and paste container format
Copy the format of a container, then paste it to a destination container in any workbook. Select Copy/Paste > Copy format from the element menu, or use keyboard shortcuts ( ⌘+⌥+C to copy and ⌘+⌥+P to paste for Mac OS, or Ctrl+Alt+C to copy and Ctrl+Alt+P to paste for MS Windows).
Workbook features
Selection criteria for action conditions
When configuring a column condition on an action sequence, use the Selection matches criteria option to run the sequence only when a user selects a table, pivot table, or input table row containing a specific column value, or when the user selects a data point representing that value in a chart.
Dynamically move columns with actions
Use the Modify element > Move columns action to dynamically move columns into and out of groupings and properties when column names match selected control values in the trigger element. This action can be configured on List value and Segmented controls only.
Use different OAuth configurations for authenticating users to your connections than you use for your Sigma organization (Beta)
Sigma now supports authenticating a connection with OAuth without re-using OAuth credentials used for authenticating users to your Sigma organization. As a result:
You no longer need to use OAuth as your authentication method for your Sigma organization in order to authenticate a connection with OAuth.
If you use multiple IdPs and data platforms, you can create connections with different OAuth configurations as needed.
When authenticating Snowflake connections with OAuth, you can configure Proof Key for Code Exchange (PKCE) and/or JSON Web Tokens (JWTs) to secure your connection.
Modals help simplify workbook design and allow you to build a streamlined, app-like experience. An open modal overlays and obscures a workbook page to provide a focused view of the modal content. This reduces visual clutter and allows you to present form fields, provide customized drilldowns, display controls and filters in a dedicated container, etc.
Expanded options for the Add workbook schedule endpoint
The Add workbook schedule endpoint (POST /v2/workbooks/{workbookId}/schedules) now supports options that were previously available only from the UI, such as creating a conditional export, repeating pivot header labels, compressing attachments to a zip file, and specifying control values for the export.
Updated application of the On close action trigger for modals
The On close trigger type for modals has been updated to only initiate actions when a user clicks the Close icon or anywhere outside the modal. The trigger no longer applies when the Close modal action is configured for the primary or secondary button.
If you configured actions for the On close trigger that are intended to initiate when a user clicks a button to trigger a Close modal action, you can move the actions to the applicable button trigger.
Bug fixes
The Create connection endpoint (POST /v2/connections) and Update connection endpoint (PUT /v2/connections/{connectionId}) no longer fail when creating or updating connections with OAuth. Note that for non-OAuth connections, the API validates that you can connect to the newly created or updated connection with your credentials. In the case of an OAuth connection, this validation step does not apply. Instead, manually validate that you can connect with your OAuth credentials after you create or update the connection.
When the value of a grouping key is null, applying the Selection variable to an Open link action no longer returns a null value that opens a blank page.
