This QuickStart lists all the new and public beta features released, as well as bugs fixed in April 2025.
It is summary in nature, and you should refer to the specific Sigma documentation links provided for more information.
Public beta features will carry the section text "Beta".
All other features are considered released (GA or generally available).
Sigma actually has feature and bug fix releases weekly, and high-priority bug fixes on demand. We felt it was best to keep these QuickStarts to a summary of the previous month for your convenience.
New first Friday features QuickStarts will be published on the first Friday of each month, and will include information for the previous month.
For more information on Sigma's product release strategy, see Sigma product releases
If something is not working as you expect, here is how to contact Sigma support
The Sigma Audit Logs connection now features a STORED_PROCEDURES
event category that records events related to the execution of stored procedures.
For more information, see Audit log events and metadata
Sigma now supports secure connections to Azure SQL Database, SQL Server 2022 and Azure SQL Managed Instances.
For more information on how to set up these connections, see Connect to Azure SQL Database (Beta) and Connect to SQL Server and Azure SQL Managed Instance (Beta)
Three separate feature permissions now allow admins to configure which account types can use AI features.
Settings for this are found in Administration
> Account Types
and scrolling down to AI
:
For more information, see Account type and license overview and Configure AI features for your organization
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.
To set this up for an existing connection, see Connect to Snowflake
For more information, see About materialization
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 information, see Manage export frequency and authentication settings
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
:
For more information, see: Set up single sign-on with SAML
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.
For more information, see Scheduled materialization bypass
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.
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.
Sigma's approach to integrating AI is really innovative and accelerates the time it takes to create meaningful content.
Checkout our unique approach here
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.
You can now set 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.
For more information, see Clear one or more control values
Individual actions or entire sequences can now be copy/pasted to allow rapid reuse 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:
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:
The Update member
PATCH /v2/members/{memberId} endpoint includes two new options to better manage scheduled exports when deactivating a user:
archiveDocuments
to true
to archive all documents associated with a user that you deactivate, including scheduled exports associated with those documents.archiveScheduledExports
to true
to archive only the scheduled exports associated with the documents owned by the deactivated user.1: Tagging a data model with a CSV uploaded no longer results in an error.
2: Secure embed users no longer see an "Invalid Databricks access token" error when accessing a workbook with OAuth credentials on a Databricks connection.
3: X-axis labels in trellis charts now display correctly when the y-axis title is displayed ( Format
> Y-Axi
s > Axis title
) and shared x-axis is enabled (Format
> Trellis
> Shared
> X-Axis
).
4: In a custom view of a workbook embed when :responsive_height
is set to true
, the lineage view now displays correctly without being truncated.
5: When exporting grouped tables with totals, the totals now appear in a separate column with a correct header, for example, "Column Name" (Grand Total)
.
6: Dynamic text in text elements now correctly displays line breaks (newline characters) and whitespace characters (tabs or spaces).
7: In OAuth-enabled embedded workbooks, OAuth connections are no longer disabled when external OAuth tokens are passed in an embed URL.
8: 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.
9: 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.
10: If users attempt to run a query with OAuth credentials that do not exist, they are now shown an improved error message.
11: 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.
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.
For more information, see: View underlying data
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.
For example, the image below shows one legend targeting two charts with the Others
category hidden:
For more information, see Create and configure a legend control
Sigma has made significant changes to the way users can model data. Data Models represent the next iteration of Datasets. We're investing heavily in Data Models over the coming months and years, with plans to add a whole suite of functionality outlined in this post.
In April, we are releasing several new features in this area to beta.
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.
For more information, see:
About metricsCreate and manage metricsNavigate data modelsUse metrics in a workbook
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.
CLS in a data model element allows configuration for specific users or teams.
For example, we may not want to allow users to see the Cost Amount
column in a sales table:
For more information, see Configure column-level security
You can pre-configure 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 video below shows selecting an existing data model relationship and opening the Edit relationship
modal to view more details, such as relationship name, description, and keys:
For more information, see Define relationships in data models (Beta)
For guidance using related columns in a workbook, see Use related columns in a workbook (Beta)
You can now schedule materialization for each tagged version of a data model.
For more information, see Schedule materialization for a version-tagged data model
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.
For example:
For more information, see Embed Ask Sigma (Beta) and Ask natural language queries with Ask Sigma
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.
For more information, see Create an embed API with JSON web tokens
There is also a QuickStart on this topic: Embedding 16: Secure Embedding with JWT
The ArrayExcept function returns an array of all unique elements from one specified array not included in another specified array.
For example, consider a table that lists all available colors of different clothing items. To see all colors available for each item, *excluding the colors black and white, use the ArrayExcept formula:
ArrayExcept([Colors], Array("black", "white"))
This can be a big time saver!
For more information, see ArrayExcept
Fundamentals 10: Data Modeling
In this QuickStart, we explore how to build a Sigma data model, join and organize tables, create calculated fields and metrics, apply column-level security, and improve usability through folders and materialization. With these tools, you're ready to deliver clean, consistent, and secure data to your users—all without writing SQL.
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.
For more information, see Customize totals and subtotals (Beta)
You can now customize the styling of data elements such as tables, input tables, visualizations, and UI elements.
For more information, see Customize element background and styles and Workbook settings overview
You can now 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.
For more information, see: Schedule materialization for a data model or workbook
You can now add formatting to Slack messages, such as hyperlinks and text formatting which help the notification gain visibility in Slack.
For more information, see Export to Slack
You can now export data from a Redshift connection to an Amazon S3 bucket.
For more information, see: Export to cloud storage (Beta)
Additional Resource Links
Blog
Community
Help Center
QuickStarts