This QuickStart lists all the new and public beta features released, as well as bugs fixed in October 2026.
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 those wanting to see what Sigma is doing on each week, release notes are now also available on the Sigma Community site. There, you can opt in to receive notifications about future release notes in order to stay on top of everything new happening at Sigma. You can also subscribe to automated updates in any Slack channel using the Sigma Community release notes RSS feed.
For more information on how to subscribe to release note notifications, see About the release notes
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

The AI usage dashboard and table now show email addresses as user names instead of External User, which helps attribute AI usage to embed users. Search indexing is now available as a filter, so you can identify the tokens used to create document embeddings in Sigma.
The Sigma Audit Logs connection now includes a USER_CREATED event type that records when new users are added to the organization.
For more information, see Audit log events and metadata
A Sigma organization can now connect to an Amazon Redshift Serverless workgroup for use with dashboards, Sigma Assistant, and agents. Write access, such as input tables and materialization, is not available.
For more information, see Connect to Redshift
Admins can create frequency presets that recommend materialization schedules. Presets appear in the Frequency dropdown, and users can still choose Custom.
For more information, see Manage materialization schedules with frequency presets
Admins can create key sets for OAuth connections to rotate JSON Web Token signing keys before the active key expires, without changing the JWKS URL.
For more information, see Manage JWT bearer OAuth key sets
When you deny a request to tag a document version with a protected tag, you can now include a reason. The reason is added to the email sent to the requesting user.
For more information, see Create and manage version tags
A new admin setting removes users' ability to send document attachments or dynamic text in exports, and limits export destinations to email, Slack, and Microsoft Teams.
For more information, see Restrict data in exports
All new SCIM bearer tokens generated through SCIM provisioning are now tied to an automatically created service account.
For more information, see Manage SCIM bearer tokens with a service account
Administrators can now choose between write-only and read/write permission levels for the Microsoft integration.
For more information, see Manage the Microsoft integration
If you use OpenAI as your AI provider, you can now set a data residency region to use a region-specific endpoint.
For more information, see Manage external AI integrations
Users can now set a display language and formatting region on their profile page. The language changes the text shown in the Sigma interface, and the region controls how numbers, dates, and currency appear.
For more information, see Set your language and formatting region
Sigma is now deployed in the AWS ap-south-1 region in Mumbai, providing lower latency for organizations in the area.
For more information, see Region, warehouse, and feature support
Sigma is now deployed in the AWS eu-central-2 region in Zurich, providing lower latency for organizations in the area.
For more information, see Region, warehouse, and feature support

The AI usage dashboard now writes to its dashboard tables using the service account credentials instead of individual user credentials, which simplifies tracking of embed users.
For more information, see Configure the AI usage dashboard

Anthropic API keys can now be used as an AI provider for Sigma AI features. A secondary embeddings provider is required.
WHY IT MATTERS:
Organizations often standardize on a specific model provider for cost, compliance, or performance reasons. Supporting Anthropic alongside other providers lets teams run Sigma's AI features on the model they have already approved, with Sigma's governance applied to how it is used.
For more information, see Add Anthropic as an AI provider
Sigma Assistant in build mode can now color bar, scatter, combo, and waterfall chart marks by conditional rule, adding visual emphasis without needing extra series.
For more information, see Use AI to build dashboards and apps

Sigma Assistant in build mode can now create and configure more of a workbook from a conversation:
WHY IT MATTERS:
Layout, charting, and page-setup details are often what slow a first draft down. Building them through conversation lets analysts and builders reach a polished, shareable workbook faster, with Sigma's governance applied from the start.
For more information, see Use AI to build dashboards and apps
When Sigma Assistant builds a KPI from a governed metric, it now automatically applies the metric's configured timeline, precision, and comparison period.
Sigma Assistant in build mode now supports additional capabilities:
Move column and Swap column actions that target rows, columns, or values.Snowflake accounts hosted on Azure now use GPT 5.1 as the LLM.
For more information, see Supported AI models

AI-generated dashboard prototypes created in Claude can be exported to Sigma as governed, shareable workbooks and apps using the Sigma MCP server.
WHY IT MATTERS:
AI-generated prototypes often stall before anyone can safely share them. Exporting to Sigma turns a prototype into a governed workbook, with permissions and audit logging applied, so teams can move from idea to shared app without rebuilding it.
For more information, see Use the Sigma MCP server

With API impersonation, you can run Sigma agents as the impersonated user, including agents you run on behalf of your embedded application's users. If an agent uses a Call API action as an action tool and the API connector requires per-user OAuth, the action fails when impersonating a user.
For more information, see Impersonate users
AI assistants connected to the Sigma MCP server can now create workbooks from natural language requests.
For more information, see Use the Sigma MCP server
Three new endpoints, GET, PATCH, and DELETE, let you manage the organization's custom SMTP server settings programmatically.
For more information, see Get the SMTP settings for an organization, Update the SMTP settings for an organization, and Delete the SMTP settings for an organization
New endpoints let you create, rotate, and delete the JSON Web Key sets that sign JWT bearer tokens for a connection, so you can monitor and rotate them programmatically.
For more information, see Create a JWK set, List JSON Web Keys, Create a JSON Web Key, Activate a JSON Web Key, Delete a JSON Web Key, Delete a JWK set, and List all JSON Web Keys
Two new endpoints swap the source elements of a workbook (POST /v2/workbooks/:workbookId/swapSourceElements) or a data model (POST /v2/dataModels/:workbookId/swapSourceElements).
For more information, see Swap workbook source elements and Swap data model source elements
Three endpoints now support the exportDestination, dynamicExportSettings, and dynamicRecipientSettings parameters: the Export workbook endpoint (POST /v2/workbooks/:workbookId/send), and the create and update schedule endpoints.
For more information, see Export workbook
The List data model sources, List workbook sources, and List report sources endpoints now include a customSqlSourceId field for sources with a type of custom-sql.
For more information, see List data model sources, List workbook sources, and List report sources
language and languageVariant options for workbook export endpoints (GA)Four endpoints now accept the language and languageVariant options, which apply a workbook translation to exported content.
For more information, see Export workbook, Send workbook, Create workbook schedule, and Update workbook schedule
The Swap report data sources endpoint (POST /v2/reports/{reportId}/swapSources) now includes a customSqlSourceId option to swap from a custom SQL source. The response includes unswappedSources for any sources that were not swapped.
For more information, see Swap report data sources
Four member endpoints now include language and formatRegion fields for setting or retrieving a member's display language and formatting region.
For more information, see Get member, List members, Create member, and Update member
The Export workbook endpoint (POST /v2/workbooks/:workbookId/send) now accepts a new request body shape, configV2.
For more information, see Export a workbook
The code representation of a workbook can now include buttons with icons.
For more information, see Button elements and Manage workbooks as code (Beta)
The Sigma API can now read and write the code representation of stack containers in workbooks.
For more information, see Manage workbooks as code (Beta)
Eight new endpoints cover general storage integration management, as well as storage integrations used for audit logs.
For more information, see List storage integrations for an organization, Create a storage integration, Update a storage integration, Delete a storage integration, Get the audit logging storage integration, Create the audit logging storage integration, Update the audit logging storage integration, and Delete the audit logging storage integration

1: The IANA time zone database used for CSV uploads is updated, so date and time values are processed correctly for recently modified time zones such as Vancouver and Edmonton.
2: After copying and pasting an element sourced from an input table or custom SQL, an error displayed and the page failed to load.
3: Sigma Assistant in the workbook now keeps a column folder and its columns together when grouping a table by that folder, instead of splitting them into separate keys.
4: Table header and cell formatting, including color, font, and banding selections, is now preserved when exporting to Excel and Google Sheets.
5: Tagging a workbook that contains an input table failed with an error.
6: Tagging a workbook with a version tag named Published failed with a duplicate item key error.
7: User interactions with Explain this chart now appear in the AI usage table with user attribution and token usage details.
8: When Sigma Assistant builds a chart from a table's governed metric, the chart now resolves and displays the metric even when the columns used in its formula are hidden on the parent table.
9: When exporting, tables with groupings and totals now render subtotals as rows, matching pivot table exports. Previously, exported subtotals appeared as additional table columns.
10: When you configure an Insert row(s) action that uses the Source data insert type, the source table list now shows only tables on the same data platform provider as the target. Existing actions with a source on a different provider show a warning in the configuration modal.
11: On the admin portal Dataset migration page, queries could time out and freeze the page for organizations with many datasets.
12: In the code representation of a workbook, inputMode for input tables that are editable in draft returned an incorrect value. The endpoint now returns the correct value.
13: When you run a dataset migration with Update references, users who are actively editing a document that uses the old dataset must now select Update to latest version before they can publish. This prevents the published version from reverting to the dataset.
14: For Google Cloud Storage external storage, the Warehouse storage integration name field is now required, and the Path prefix field rejects a leading or trailing /, the wildcards * and ?, and .. path segments. Settings that previously caused CSV upload failures are now validated.
15: When you migrate a dataset to a data model, some references failed to update to the newly created data model.
16: When you add sources to a document, you can now add multiple data sources without closing the source picker by hovering over a source and selecting Add source.
17: Archiving a tenant failed with a Failed to archive tenant(s) error for some tenants because of inconsistently archived deployment records.
18: Badges now use sentence case instead of all caps. For example, Beta instead of BETA.
19: Sigma now enforces the Manage agents permission when users create agents through the Sigma MCP server.
20: Sparklines now display correctly for data with null y values instead of showing an error.
21: Tagging a data model version no longer fails with a writeback schema error when the draft has an input table on a non-OAuth connection.
22: Tagging a version and swapping the source of a workbook that contains a Databricks Genie Agent tool for a Sigma agent no longer fails with a Path not found error.
23: When selecting a source, users now see only the tagged data model versions they have access to.
24: Selecting Stop in Sigma Assistant now cancels any running query, and Assistant queries time out after 120 seconds.

Embedding Sigma documentation now requires the embedded=true query parameter, for example https://help.sigmacomputing.com/welcome?embedded=true.

This QuickStart shows how to run a small local MCP server so Claude Desktop can find a Sigma workbook by name and open it, live and interactive, in Claude's browser pane.
This QuickStart shows how to build an application where users choose Sigma elements, place them in zones on a canvas, and generate a real Sigma workbook from their selections, using workbook as code and the REST API while Sigma continues to supply the governed data.
This QuickStart shows how to use the excel-to-sigma Claude Code skill to migrate an Excel rolling forecast to a Sigma data model and workbook, keep the forecast inputs editable with input tables, and verify that Sigma's totals tie to Excel's.

Three new templates monitor AI spending for Claude Platform, Cursor, and Databricks. Each template shows all AI costs for that tool, not only the costs incurred through Sigma.
For more information, see Claude Platform spend template, Cursor spend template, and Databricks spend template

Control changes made in a custom view can now be applied to scheduled exports using a new option.
For more information, see Configure additional options for exports
Translations added to a workbook or report can now be applied to exports of that document.
For more information, see Apply translations in workbook or report export attachments
Organizations can now create reusable success, failure, and suspension messages for email exports.
For more information, see Create custom email export templates
Build a progress bar or ring to show a value as a percentage or proportion of a target value.
For more information, see Build a progress bar and Build a progress ring
Workbook downloads can now be split by the values of a list control. Sigma returns a zipped file containing a separate download, with data customized for each selected value.
For more information, see Download workbook data

Containers can now use a stack layout, which arranges elements automatically using a flexbox-inspired model to produce responsive layouts.
WHY IT MATTERS:
Dashboards are viewed on many screen sizes, and manual positioning rarely holds up across them. Stack layouts adapt automatically, so builders maintain one layout instead of several and viewers get a consistent experience.
For more information, see Use stacks to make responsive layouts
Segmented controls now use a Surface color, rather than a Highlight color, to show the selected segment.
Icons across Sigma now have a thinner stroke, some match the surrounding text color, and several have new designs. The change is visual only.

Additional Resource Links
Blog
Community
Help Center
QuickStarts
