This QuickStart lists all the new and public beta features released, as well as bugs fixed in May 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's how to contact Sigma support

Alerts before OAuth sessions expire

Users now see an alert message 20 minutes before their connection-level OAuth session expires, prompting them to re-sign into the connection.

For more information, see Configure OAuth

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).

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:

For more information, see Account type and license overview

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).

Users with this permission enabled on their account type can view database or catalog, schema, or table names that they have access to.

For more information, see Manage access to data and connections

New permission for calling stored procedure actions

Administrators can now manage which users can call stored procedure actions from a workbook with the Call stored procedure actions permission.

For more information, see Account type and license overview

The permission requires an Act or Essentials license.

For all requirements, see Create actions that call stored procedures (Beta)

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.

For more information, see Configure your IdP in Set up single sign-on with SAML

Warehouse AI model integration (Beta)

If your organization is connected to Snowflake or Databricks, you can now use warehouse-hosted AI models to power Sigma AI features.

For information about selecting your data platform as your organization's AI provider, see Configure warehouse AI model integration

1: 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.

2: 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".

3: Users in an embed can no longer open the source of a data model.

4: 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.

5: 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.

6: 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.

7: When sharing a workbook, version tags now appear for all access levels as expected.

8: 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.

9: Archived connections no longer cause unexpected errors in shared templates.

10: Changing organization level authentication from OAuth to another authentication method no longer causes independent OAuth configuration options to disappear in Administration.

11: The More menu for tables has been updated to remove a nonfunctional Make owner option.

12: When using connection-level OAuth, your email is no longer checked to see if it matches the email used for signing in to Sigma.

13: Previously, in Snowflake OAuth connections with service accounts enabled, if the serviceAccountWarehouse was not set in Sigma, it would be evaluated as undetermined (resulting in an error). Now, if the warehouse is set by a user attribute, the service account will use the default value of the user attribute.

14: When pressing Tab to navigate between elements in a container, the navigation order matches the position of the elements within the container.

15: When a container is selected, pressing Tab correctly changes selection from the container to the top-left-most element in the container.

16: When the top-left-most element in a container is selected, pressing Shift + Tab selects the parent container.

17: When selecting an element in a workbook to navigate to with the Navigate in this workbook action, the list of elements for a page matches the order of the elements on the page.

18: Sigma now uses improved logic for presenting the initial workbook page from a URL with the :nodeId parameter when the page includes conditional visibility rules. If the user cannot view the page, the first visible page is shown.

19: Sigma did not support workbook deletion for JWT-signed secure embeds. Now a user can delete a workbook from the menu and get redirected to an error page with the document browser to navigate to another workbook.

20: For JWT-signed embeds, errors are now sent when the JWT token cannot be parsed and when the current user is not invited to the workbook they are attempting to access.

Column order enforced when dynamically moving columns

When you use a multi-select list control to dynamically move columns into and out of groupings or properties (via the Move columns action), the column order in the table now matches the order of the values defined in the control.

The Move column action moves columns into or out of a table grouping, pivot table property (row, column, or value), or chart property (axis, color, tooltip, etc.) in the target element. Columns can be moved based on a static selection or when column names match selected control values in the trigger element.

For more information, see Move columns

Custom context menu actions (Beta)

You can now 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.

This unlocks really interesting workflows to get users the detail they need quickly.

For more information, see Create custom context menu actions (Beta)

Formula support in image URL

When configuring an image element, you can enter dynamic text in the Image URL field to source the URL from a formula.

For example, Lookup([Team/Profile Image URL], CurrentUserEmail(), [Team/Email]) references the Profile Image URL column in an existing Teams table to dynamically display profile images based on the current user.

For more information, see Add hyperlinks and images to columns

PostgreSQL support for calling stored procedure actions

You can now call a stored procedure on a PostgreSQL connection from a workbook action.

For more information, see Create actions that call stored procedures (Beta)

Update row and Delete row actions for Input Tables (GA)

You can now update and delete input table rows using actions.

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.

For more information, see Create actions that modify input table data

Data models (GA)

Data models are now generally available.

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.

For more information, see:

Get started with data modeling
Create and manage data models
Navigate data models

There is a also a QuickStart: Fundamentals 10: Data Modeling

Add metrics to data models (GA)

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.

For more information, see:

About metrics
Create and manage metrics
Navigate data models
Use metrics in a workbook

Column-level security for data models (GA)

Applying column-level security (CLS) to elements in data models is now generally available.

Column-level security restricts access to column-level data for or one or more users or teams using the data model table downstream. This ensures that sensitive and confidential information is secure and accessible only to authorized users.

For more information, see Configure column-level security

Define relationships in data models (GA)

You can now 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

For more information, see ​​Define relationships in data models

For guidance using related columns in a workbook or data model, see Use related columns in a workbook or data model

Map changed columns in a data model

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.

For more information, see Map changed columns in a data model

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.

For more information, see Create and manage a control element

New connection_oauth_tokens JWT claim

The connection_oauth_tokens JWT claim is now available.

This is an optional claim that allows you to pass OAuth tokens through JWT-signed URLs for connection-level OAuth.

For more information, see JWT claims

New outbound event emitted for deleted workbooks

When a workbook is successfully deleted from the embed menu, an outbound workbook:ondelete event is emitted.

For more information, see workbook:ondelete

There is also a QuickStart: Embedding 16: Secure Embedding with JWT

Created at/by columns in input tables (Beta)

You can now add Created at and Created by columns to input tables to record metadata associated with each row's creation.

This is in addition to and different than the current Last updated at/by columns.

Created at: Date and time the row was added to the input table.

Created by: Email address of the user who initially added the row to the input table.

For more information, see Add row edit history

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:

Intro to input tablesCreate new input tablesEdit existing input table columns

There is a also a QuickStart (Snowflake based, but any supported connection will work too): Sigma Input Tables: Use Cases

Multi-select columns in input tables (Beta)

You can now 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:

For more information, see Configure multi-select columns on input tables

Snowflake Summit 2025 - Hands on Lab

In this QuickStart (which was launched at this year's Snowflake Summit) you will create an analysis using AI, and leverage a data application and forecast out product performance. You will act as a category manager at a retail company building out an ad-hoc analysis from an AI-generated jump-off point to determine your category plan for the year.

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.

The shortcut icon looks a little different than a standard workbook:

For more information, see Add shortcuts to documents

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 also change the label of any subtotal or grand total.

For more information, see Customize totals and subtotals

Drag to move the live chat window

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.

Export to webhook supports PDF files

Send PDF-formatted files to a webhook endpoint from Sigma.

For more information, see Export to webhook

Limit display values in a data element (Beta)

You can now 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 using the VisibilityLimit function with a sorted table.

Different from a Top N filter , limiting the display values lets you change which values are displayed without affecting the calculated totals and other values.

For example, to only show the top 3 performing stores in each store region in a pivot table, you can limit the displayed stores to the top 3 sorted by total products sold:

VisibilityLimit([Store Name], 3)

For more information, see Limit displayed values in a data element

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.

For more information, see Format and customize a table

Organize columns into folders (Beta)

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.

For more information, see Organize columns into folders

Popovers (Beta)

You can now 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.

Reference data elements in custom SQL statements (Beta)

You can now reference data elements and other custom SQL elements in SQL statements in Sigma using the sigma_element(‘Element Title') syntax.

For example:

SELECT * FROM sigma_element('Fiscal Year Forecast')
WHERE "Revenue" > 100000

For more information, see Write custom SQL

Transpose a table (Beta)

Sigma now supports transposing a table from rows to columns, or columns to rows.

Transposing data can be useful for data analysis, as it allows you to pivot or un-pivot your data according to your individual use case.

This can be especially useful for visualizations, as you may want to reshape your data to suit specific chart types –such as needing date values oriented in a single column for line charts.

For more information, see Transpose a table

Additional Resource Links

Blog
Community
Help Center
QuickStarts