> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.sigmacomputing.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.sigmacomputing.com/_mcp/server.

# What's new in Sigma

## AI

### Assistant in workbooks: governed metric timelines in KPIs

In workbooks, Sigma Assistant automatically applies a governed metric’s configured timeline, precision, and comparison period when building a KPI element from that metric in your data model.

### New model used for Snowflake Azure AI providers

If you use a Snowflake account hosted on Azure as your AI provider, Sigma now uses GPT 5.1 again as the LLM.

For more details, see [Supported AI models](/docs/supported-ai-models).

## API

### New `language` and `languageVariant` options for some workbook export endpoints

The following endpoints include new `language` and `languageVariant` options to apply a workbook translation to exported content:

* [Export data from a workbook](/reference/export-workbook) (`POST /v2/workbooks/{workbookId}/export`)
* [Export a workbook](/reference/send-workbook) (`POST /v2/workbooks/{workbookId}/send`)
* [Add workbook schedule](/reference/post-workbook-schedule) (`POST /v2/workbooks/{workbookId}/schedules`)
* [Update a workbook schedule](/reference/update-workbook-schedule) (`PATCH /v2/workbooks/{workbookId}/schedules/{scheduleId}`)

### New options available for member endpoints

The [Get a member](/reference/get-member) (GET /v2/members/\{memberId}), [List members](/reference/list-members) (GET /v2/members), [Create a member](/reference/create-member) (POST /v2/members), and [Update a member](/reference/update-member) (PATCH /v2/members/\{memberId}) endpoints now include the following fields:

* `language`
* `formatRegion`

Use these fields to set or retrieve a member’s preferred display language and formatting region programmatically.

### Represent buttons with icons in the code representation of a workbook (Beta)

You can now represent buttons with icons in the code representation of a workbook.

For more information on buttons with icons, see [Button elements](/docs/button-elements). For more information on the representing workbooks as code, see [Manage workbooks as code (Beta)](/docs/manage-workbooks-as-code).

## Admin

### Connect to Redshift Serverless (Beta)

You can connect a Sigma organization to an Amazon Redshift Serverless workgroup. Query data to use with dashboards, Sigma Assistant, or agents.

Write access, such as using input tables or materialization, is not available for Redshift Serverless. For details, see [Connect to Redshift](/docs/connect-to-redshift).

### Restrict data in exports (Beta)

Admins can use the **Restrict data in exports** toggle to remove users’ ability to send document attachments or dynamic text in exports. This is useful for preventing sensitive data from leaving your organization. This option also restricts available export destinations to email, Slack, and Microsoft Teams.

See [Restrict data in exports (Beta)](/docs/restrict-export-recipients#restrict-data-in-exports-beta).

### Sigma now supports the AWS Europe (Zurich) region

Sigma is now deployed in AWS Europe (eu-central-2) region. This region, located in Zurich, gives customers lower latency and enhanced performance when connecting to Sigma.

See [Supported regions, data platforms, and features](/docs/region-warehouse-and-feature-support).

### Sigma now supports the AWS Asia Pacific (Mumbai) region

Sigma is now deployed in AWS Asia Pacific (ap-south-1) region. This region, located in Mumbai, gives customers lower latency and enhanced performance when connecting to Sigma.

See [Supported regions, data platforms, and features](/docs/region-warehouse-and-feature-support).

## Resources

### AI-accessible audit log documentation

[Audit log and event metadata](/docs/audit-log-events-and-metadata) details and descriptions are now text tables accessible to AI tools, instead of embedded content. If you use an AI tool with the Sigma documentation MCP server or provide Markdown-formatted pages to an AI tool, your AI tool can retrieve details about specific audit log events and categories.

For more details, see [Access Sigma documentation from AI tools](/docs/use-documentation-mcp-server).

## Templates

### New AI cost monitoring templates

If you want to monitor your AI costs in Sigma, you can use one of the following templates:

* [Claude Platform spend template](/docs/claude-platform-spend-template)
* [Cursor spend template](/docs/cursor-spend-template)
* [Databricks spend template](/docs/databricks-spend-template)

> **Info**
>
> The templates visualize all AI costs for the associated AI tool and are not specific to Sigma-incurred costs.

## User profile

### Set your language and formatting region (Beta)

You can now set your preferred display language and formatting region from your user profile page. Your language changes Sigma UI text, and your formatting region controls how numbers, dates, and currency are formatted for you.

For more information, see [Set your language and formatting region](/docs/set-your-language-and-formatting-region).

## Workbook features

### Apply translations in workbook or report export attachments (GA)

The ability to apply translations added to a workbook or report to an export of that document is now generally available.

See [Apply translations in workbook or report export attachments (Beta)](/docs/manage-workbook-localization#apply-translations-in-workbook-or-report-export-attachments-beta).

### Create custom email export templates (GA)

Custom email export templates are now generally available. You can create reusable sets of success, failure, and suspension messages for your organization’s email exports.

See [Create custom email export templates](/docs/create-custom-email-export-templates).

### Split a download by the values of a specific control (GA)

You can split a download by the values of a specific control. This can be helpful when you want to send customized data to different recipients.

See [About splitting a download by control values](/docs/download-workbook-data#about-splitting-a-download-by-control-values).

## Bug fixes and improvements

* For organizations that have a large number of datasets, some queries would timeout and freeze the **Dataset migration** page of the Admin portal.

* Previously, [getting the code representation of a workbook](https://help.sigmacomputing.com/reference/get-workbook#get-the-code-representation-of-a-workbook-beta) returned an incorrect value for the `inputMode` of input tables that were editable in draft. Now, the endpoint returns the correct value.

* When a dataset is migrated to a data model with **Update references** selected, users actively editing a document that uses the old dataset as a source can’t publish the document until they select **Update to latest version** to switch to the new data model, which prevents the published version from incorrectly reverting to using the dataset.

* When an admin configures a Google Cloud Storage (GCS) external storage integration, Sigma now validates settings that previously caused CSV uploads to fail. The **Warehouse storage integration name** field is now required, and the **Path prefix** field no longer accepts a leading or trailing `/`, wildcard characters `*` and `?`, or `..` path segments.

* When migrating a dataset to a data model, some references failed to update to using the newly-created data model.

* You can now add multiple data sources to a document without closing the source picker by hovering over a source and selecting ![](https://sigma-docs-screenshots.s3.us-west-2.amazonaws.com/Icons/add.svg) Add source.