> 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

### New model used for Gemini and BigQuery AI providers

If you use Gemini as your AI provider through an API key or a BigQuery connection, Sigma now uses Gemini 3.6 Flash as the LLM.

For more details, see [Set up an AI provider](/docs/configure-ai-features-for-your-organization#set-up-an-ai-provider).

## API

### New options for the Get a workbook endpoint

The [Get a workbook](/reference/get-workbook) (`GET /v2/workbooks/{workbookId}`) endpoint includes a new query string parameter: `includeTaggedSourceUrlId`.

When that query string parameter is included, the `taggedSourceUrlId` is included in the response for version tagged workbooks that were deployed from a parent or another tenant organization, making it possible to easily identify the source document for a deployed document.

## Admin

### Set formatting region in Administration portal (Beta)

You can now specify an account formatting region for your Sigma organization in the Administration portal. The formatting region affects how numbers, dates, and currency are formatted in Sigma for all users in your organization.

For more information, see [Set organization language](/docs/manage-organization-language).

## Templates

### Snowflake Cortex AI spend template

Sigma now provides a template to visualize the costs associated with all Snowflake Cortex AI tool usage. For more details, see [Snowflake Cortex cost template](/docs/snowflake-cortex-cost-template).

## Workbook features

### Ad hoc email burst exports (Beta)

You can now export as email burst as needed, instead of as a scheduled export.

See [Send an ad hoc email burst (Beta)](/docs/export-as-email-burst#send-an-ad-hoc-email-burst-beta).

## Bug fixes and improvements

* When you use a data model as a data source in a workbook and then swap to a different tagged version of the data model, columns added through relationships no longer display as errors.