> 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

> Sigma release notes for Oct 16, 2026: Anthropic as an AI provider, bursting on export endpoints, SCIM service accounts, and splitting downloads by control values.

## AI

### Anthropic as an AI provider (GA)

Add an Anthropic API key to use models from Anthropic with Sigma AI features. When you set up Anthropic as your external AI provider, you use Anthropic for the large language model (LLM) and must also configure a second AI provider that has an embeddings model.

For more details, see [Add Anthropic as an AI provider](/docs/manage-external-ai-integrations#add-anthropic-as-an-ai-provider).

### AI usage dashboard uses the service account

If you configure the AI usage dashboard to write to a connection with a service account configured, Sigma uses the credentials of the service account (instead of individual user credentials) to write to the table. When a service account is available, Sigma tracks embed user activity without additional configuration.

For more details, see [Configure the AI usage dashboard](/docs/configure-ai-usage-dashboard).

### New model used for Snowflake AI providers hosted on Azure

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

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

### Assistant in build mode: color chart marks by rule

In workbooks, Sigma Assistant in build mode can now color bar, scatter, combo, and waterfall chart marks by a conditional rule, so dashboards can highlight values (like increases vs. decreases) without stacking extra series.

## API

### New options for bursting on some export endpoints

The following endpoints now include the `exportDestination`, `dynamicExportSettings` and `dynamicRecipientSettings` options to support bursting:

* [Export a workbook](/reference/send-workbook) (`POST /v2/workbooks/:workbookId/send`) endpoint
* [Add workbook schedule](/reference/post-workbook-schedule) (`POST /v2/workbooks/:workbookId/schedules`) endpoint
* [Update a workbook schedule](/reference/update-workbook-schedule) (`PATCH /v2/workbooks/:workbookId/schedules/:scheduleId`) endpoint

### New request body shape for the Export a workbook endpoint

The [Export a workbook](/reference/send-workbook) (`POST /v2/workbooks/:workbookId/send`) endpoint includes a new `configV2` shape for the request body.

## Admin

### SCIM service accounts for bearer tokens

All new SCIM bearer tokens generated through SCIM provisioning are now tied to an automatically created service account, instead of the account of the Sigma admin that generated it. This prevents SCIM provisioning breaking if the admin is deactivated or has their license type changed. For organizations with existing SCIM configurations, no changes are made to your existing SCIM configuration.

See [Manage SCIM bearer tokens with a service account](/docs/manage-users-and-teams-with-scim#manage-scim-bearer-tokens-with-a-service-account).

## Resources

### Embed the Sigma documentation

Embedding the Sigma documentation site, such as in an embed element in a workbook, now requires a query string parameter. When embedding the Sigma documentation, add the `embedded=true` query string to the URL. For example, `https://help.sigmacomputing.com/welcome?embedded=true`.

## Workbook features

### Apply control changes in a custom view to a scheduled export

You can now apply control changes from a custom view to your scheduled export. When configuring your scheduled export, the **Apply custom control values** option appears if you have made changes to controls in a custom view.

See [Filter by control values](/docs/configure-additional-options-for-exports#filter-by-control-values).

### Select Microsoft integration permission levels (GA)

When setting up a Microsoft integration, you can now select between write only and read/write access levels.

See [Permission levels](/docs/manage-microsoft-integration#permission-levels) in [Manage Microsoft integration](/docs/manage-microsoft-integration).

### Split a workbook download by control values (GA)

When downloading workbook data, you can split the download using list control values, and receive a link to a zip file with one filtered file per value. Use this to send customized data to different recipients.

For more information, see [Download workbook data](/docs/download-workbook-data#about-splitting-a-download-by-control-values).

## Bug fixes and improvements

* After copying and pasting an element sourced from an input table or custom SQL, an error displayed and the page failed to load.
* Assistant in the workbook now keeps a column folder and its columns together when grouping a table by that folder instead of splitting it into separate keys.
* Table header and cell formatting, including color, font, and banding selections, are now preserved when exporting to Excel and Google Sheets.
* Tagging a workbook that contains an input table failed with an error.
* Tagging a workbook with a version tag named "Published" failed with the error "React ErrorBoundary Error: \[Phi (Node)] Detected duplicate item key: 'Published'".
* User interactions with **Explain this chart** now appear in the AI usage table with user attribution and token usage details.
* When 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.
* When exporting, tables with groupings and totals now render subtotals as rows, matching pivot table exports. Previously, exported subtotals appeared as additional table columns.
* 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. For more information about source table requirements and moving data to a different data platform instance, see [Create actions that modify input table data](/docs/create-actions-that-modify-input-table-data).