> 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 ## What's new in Sigma ## AI ### Assistant in build mode: reuse data model metrics In workbooks, Sigma Assistant in build mode now preserves data model sources you attach and reuses their metrics instead of recreating the underlying tables and calculations. When you ask Assistant to build a dashboard from a data model, KPIs and charts use the metrics defined in that data model, keeping values consistent with your governed definitions. For more information about Assistant in build mode, see [Use Sigma Assistant to build dashboards and apps](/docs/use-ai-to-build-dashboards-and-apps). ### Call Sigma agents from the Sigma MCP server Interact with your workbook agents from any AI tool connected to the Sigma MCP server. The server includes two new tools: * List the agents you can access * Call an agent These tools are only available in the Sigma MCP server, not in the plugin or connector. For more information, see [Use the Sigma MCP server](/docs/use-sigma-mcp-server). ### Chat history with customer-owned storage Admins can now choose where chat history is stored: * If your organization grants storage rights to Sigma, you can configure chat history to be stored by Sigma in a Sigma-owned bucket. * If your organization requires more control over storage to meet data governance and compliance requirements, you can instead store chat history in a customer-owned bucket through an external storage integration. For more information, see [Configure chat history](/docs/configure-chat-history). ### MCP connectors for Sigma agents (GA) Admins can add MCP servers to Sigma as MCP connectors so that Sigma agents can retrieve context, fetch ad hoc data, and take actions in third-party tools. For details, see [Configure MCP connectors](/docs/configure-mcp-connectors). ### New models used for AI providers The following LLM models have been updated for the following AI providers: * If you use OpenAI, Sigma now uses GPT 5.6 as the LLM. * If you use Databricks, Sigma now uses Claude Sonnet 5 as the LLM. * If you use Anthropic, Sigma now uses Claude Sonnet 5 as the LLM. For more details, see [Supported AI models](/docs/supported-ai-models). ### Sigma Assistant in the workbook (GA) Sigma Assistant in the workbook is now generally available. In workbooks, Assistant lets you use natural-language prompts to explore workbook data, analyze insights, and build or edit dashboards and apps. This release also includes the following updates: * Chat history: View, resume, rename, and delete your own recent chats with Sigma Assistant. See [Configure chat history](/docs/configure-chat-history). * Code-first architecture: Assistant builds by writing code, which improves accuracy, speeds up builds, and lowers the cost to run. * Broader element support: Assistant can build and customize more workbook element types, including maps, combo charts, navigation, drawers, and single row containers. * More in-chat chart capabilities: Assistant can include more chart types and formatting (like reference lines and trend lines) directly in the chat, and you can immediately add them to the workbook canvas. * Improved look and feel: Assistant builds with better design defaults and supports more theming options. For more information, see [Use Sigma Assistant to explore and analyze workbook data](/docs/sigma-assistant-in-the-workbook) and [Use Sigma Assistant to build dashboards and apps](/docs/use-ai-to-build-dashboards-and-apps). ### Sigma agents (GA) [Build agents](/docs/build-agents) in workbooks that use instructions, data sources, actions, warehouse agents, warehouse search services, and MCP connectors to help users with business tasks. [Chat with agents](/docs/chat-with-agent) in a workbook, prompt them in an [automated action run on a schedule](/docs/create-actions-that-interact-with-agents), or [call agents with the API](/docs/call-agents-with-the-api) or Sigma MCP server. When you chat with agents, you can resume conversations stored in the chat history, approve tasks for the agent to perform, and start new chats. You can also [embed a Sigma agent chat interface](/docs/embed-agent). For real-world use cases, see [Example use cases for Sigma agents](/docs/example-agent-implementations). Admins can review agents across the organization in Administration, reviewing token usage, owners, data sources, access grants, user feedback, and an execution log for every conversation turn. See [Manage Sigma agents for your organization](/docs/manage-agents-for-your-organization). For assistance evaluating agent quality, follow the guidelines in [Build an evaluation suite for your agents](/docs/build-agent-evaluation-suite). Sigma agents are a premium feature. For billing details, see [About billable usage events](/docs/about-billable-usage-events). For more details, see [About Sigma agents](/docs/sigma-agents). ## API ### New options for some workbook endpoints To make it clear which tags on a workbook are inactive when using the API, the `tags` array of the response of the following endpoints now includes an `isArchived` option: * [List workbooks](/reference/list-workbooks) (`GET /v2/workbooks`) * [Get a workbook](/reference/get-workbook) (`GET /v2/workbooks/{workbookId}`) * [Get tags for a workbook](/reference/get-workbook-tags) (`GET /v2/workbooks/{workbookId}/tags`) ### New options for the Create a deployment policy endpoint The [Create a deployment policy](/reference/create-deployment) (`POST /v2/deploymentPolicies`) endpoint includes a new `useDependenciesWorkspace` option to specify a separate workspace when deploying dependent documents. For more details about dependency management in a deployment policy, see [How dependencies are deployed](/docs/deploy-content-to-tenant-organizations#how-dependencies-are-deployed). ### New options for the List workbooks endpoint The [List workbooks](/reference/list-workbooks) (`GET /v2/workbooks`) 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 ### Query variables support for Cortex Agents (Beta) You can now support row-level security set in row access policies when using Snowflake Cortex Agents in Sigma. When you configure query variables on a Snowflake connection, Sigma sets immutable session attributes used for every Cortex Agent interaction, enforcing RLS. See [Specify query variables for a Snowflake connection (Beta)](/docs/specify-query-variables-for-a-snowflake-connection). ## Data modeling ### Revert migrated dataset references When you migrate a dataset to a data model and update references to use the new data model as a source, you can now choose to revert the references so they use the old dataset as a source again. This is helpful when troubleshooting dataset migrations or testing different approaches to a migration. For more information, see [Migrate a dataset to a data model](/docs/migrate-a-dataset-to-a-data-model). ## Workbook elements ### Date support for slider and range slider controls You can now select between **Date** and **Number** value types when configuring slider and range slider controls. See [Slider](/docs/intro-to-control-elements#slider) and [Range slider](/docs/intro-to-control-elements#range-slider) in [Intro to control elements](/docs/intro-to-control-elements) for more information. ## Bug fixes and improvements * If you used OpenAI GPT-5.4 or OpenAI GPT-5.1 as the model, calling an agent as part of an automated action failed to run. * Any user with **Can edit** access to a dataset can now migrate that dataset to a data model. * Previously, an error prevented selecting the **Properties** tab for an element after selecting another tab in the editor panel. Now, you can select the **Properties** tab as expected. * When trying to connect to OpenAI as an external AI provider, Sigma expected the GPT 4.0 model to be available instead of the GPT 5.4 model. * When using the **Call agent** action to automate a Sigma agent on a schedule, the action could return null values when the agent's response was incomplete or had the wrong data type, and actual null values caused an "invalid action variable" error in later actions in the sequence. Missing or incorrect values now trigger a retry, and null values keep their type so later actions can use them successfully. * When using Azure OpenAI as the AI provider, chats with agents and Assistant ended partway through a response with the message "The assistant stopped responding." Responses now finish normally. ## What's new in Sigma ## AI ### Assistant in build mode: pivot table styling In workbooks, Sigma Assistant in build mode now creates pivot tables with automatic heatmap and matrix styling based on the type of measures. Measures that read against a threshold (e.g., profit, variance, margin, and growth) are styled as heatmaps with diverging color scales that help you spot patterns and outliers without reading every value. Measures that are straightforward totals (e.g., revenue and headcount) receive plain matrix styling. For more information, see [Use Sigma Assistant to build dashboards and apps](/docs/use-ai-to-build-dashboards-and-apps). ### Assistant in build mode: cohort retention tables In workbooks, Sigma Assistant in build mode now generates styled cohort retention pivot tables. Assistant recognizes requests for cohort retention analysis and automatically builds the pivot table accordingly, including heatmap styling that makes retention patterns easy to identify. For more information, see [Use Sigma Assistant to build dashboards and apps](/docs/use-ai-to-build-dashboards-and-apps). ### Chat history for Assistant and agents (GA) Chat history is now available for conversations with Sigma Assistant, warehouse agents, and Sigma agents. With chat history, users can now revisit and continue previous conversations instead of starting from scratch each time. Chat history is not yet available for conversations with Assistant in the workbook, or agents on the home page. For organizations that meet certain conditions, an admin can configure chat history storage and retention. Considerations and limitations apply. See [Configure chat history](/docs/configure-chat-history). ### Improved Sigma Assistant Sigma Assistant now includes improved reasoning, faster performance, and higher quality responses. Updates include: * Clarifying questions: Ask a broad business question and Assistant prompts you to narrow it down, sharing its assumptions and flagging caveats * All sources, or a curated shortlist: Admins can open Assistant up to every accessible data source. Role-based access controls still apply. * Visible reasoning and side by side detail inspection: Assistant describes its reasoning as it works, and you can inspect the chosen data sources alongside your chat conversation, including previous prompts in the same conversation. * Export conversations: You can now export a full conversation as an image. For more details, see [Ask natural language queries with Sigma Assistant](/docs/ask-natural-language-queries-with-assistant). ### Use warehouse agents with Assistant and agents (GA) If you have Snowflake Cortex Agents or Databricks Genie Agents, you can use those agents in Sigma. Ask questions from Sigma Assistant, or set up a Sigma agent (Beta) to call one or more warehouse agents as tools. Admins can turn off warehouse agents to use only Sigma Assistant from the home page. For more details about setup requirements and usage, see [Use warehouse agents with Sigma](/docs/use-warehouse-agents-sigma). ## API ### New API endpoints for managing AI chat history settings (Beta) The following endpoints are now available to configure chat history for an organization in Sigma: * [Get the chat history settings for an organization (Beta)](/reference/get-ai-chat-history-setting) (`GET /v2/organizations/settings/aiChatHistory`) * [Update the chat history settings for an organization (Beta)](/reference/update-ai-chat-history-setting) (`PATCH /v2/organizations/settings/aiChatHistory`) ## Reports ### Export and download reports as PowerPoint (GA) The ability to download and export reports as PowerPoint (.pptx) files is now generally available. See [Share and export reports](/docs/share-and-export-reports). ## Workbook elements ### Manually trigger an AI column or cell run (Beta) When configuring an AI column, you can now use the **Don't run automatically** option to configure the AI column to only run when manually prompted instead of automatically. You can re-run an AI column query for a single cell at any time. See [Create AI columns (Beta)](/docs/create-ai-columns). ## Bug fixes and improvements * Version-tagging or source-swapping a workbook with a broken/missing connection reference now returns a clear “connection no longer exists” error instead of a generic failure. * When calling the [List workbooks for a tag](/reference/list-workbooks-for-tag) (`GET /v2/tags/:tagId/workbooks`) endpoint using API credentials assigned to a non-admin user with access only to specific tagged versions of a workbook and not the published workbook, no results were returned. * When having a conversation with Sigma Assistant or a Sigma agent over a dozen messages when using an AI provider that uses Claude Sonnet 5 as the reasoning model, a 400 error "The final block in an assistant message cannot be `thinking`" displayed. ## What's new in Sigma ## AI ### Migrate to Sigma with an AI assistant (Beta) You can use migration skills for Sigma to have an AI assistant rebuild your source content — the dashboards, reports, and data models in another business intelligence (BI) tool — as a Sigma document. Each supported source tool has its own skill, and most also have a read-only assessment skill that inventories your existing content so you can decide what to migrate first. For more information, see [Migrate to Sigma with an AI assistant](/docs/migrate-to-sigma-with-an-ai-assistant). ### New skills for creating workbooks and reports with an AI assistant You can use agent skills published by Sigma to provide reference materials and instructions to your AI assistants. The `sigma-workbooks` and `sigma-reports` skills can be used to support an AI assistant when authoring the code representation of a workbook or report. For more information, see [Install skills for AI assistants](/docs/install-skills-for-ai-assistants). ### Assistant in build mode: new code-first architecture (Beta) In workbooks, Sigma Assistant in build mode now runs on a code-first architecture that improves the overall user experience. Key improvements: * More accurate and consistent outcomes * Faster, more efficient builds with lower token usage * Better data source search * Recent and favorite data source retrieval * Improved output look and feel * Automatic compression for large image uploads The update also includes more native feature support, including: * Value list elements * Embed elements * Chat elements, with support for creating new custom agents, renaming them, and attaching sources * Single row container elements, with support for actions * Dynamic text in button elements * Export actions for downloading data * File columns and file-upload fields, with count, size, and file-type restrictions * Input table data entry permission selection * Additional options for action sequence conditions * Expanded styling for tables and table titles * More workbook and page theme settings * Broader map and combo chart capabilities For more information about Assistant in build mode, see [Use Sigma Assistant to build dashboards and apps](/docs/use-ai-to-build-dashboards-and-apps). ### Chat history for Sigma agents (Beta) Chat history is now available for conversations with Sigma agents. For organizations that meet certain conditions, an admin can configure chat history storage and retention. Considerations and limitations apply. See [Configure chat history](/docs/configure-chat-history-agents). After chat history is configured, conversations with Sigma agents are stored and you can revisit previous conversations that you had with an agent in a chat element. See [Chat with Sigma agents](/docs/chat-with-agent) for more details. ## API ### Manage workbooks from a code representation (Beta) You can use the Sigma API to retrieve, update, and create workbooks based on a JSON or YAML representation. Using this representation with the Sigma API, you can manage, create, and review workbooks without using the Sigma UI. The following endpoints can now be used to manage workbooks based on a code representation: * [Get workbook](/reference/get-workbook#get-the-code-representation-of-a-workbook-beta) (`GET v2/workbooks/:workbookId`) * [Create workbooks](/reference/create-workbook#create-a-workbook-from-a-code-representation-beta) (`POST v2/workbooks`) * [Update a workbook from a code representation](/reference/update-workbook-contents) (`PUT v2/workbooks/:workbookId/contents`) For more information, see [Manage workbooks as code (Beta)](/docs/manage-workbooks-as-code). For examples of various features represented as code, see the [Workbook representation example library](/docs/workbook-representation-example-library). ### New API endpoints to list and run Sigma agents (Beta) Build conversational workflows in your applications by calling Sigma agents programmatically with the API. The following endpoints are now available to list and run Sigma agents in Sigma: * [List agents](/reference/list-workbook-agents) (`GET /v2/workbookAgents`) * [List agents in a workbook](/reference/list-agents-in-workbook) (`GET /v2/workbooks/:workbookId/agents`) * [Run a Sigma agent](/reference/run-agent) (`POST /v2/workbooks/:workbookId/agents/:agentId`) For usage details, including an end-to-end example, see [Call Sigma agents with the API](/docs/call-agents-with-the-api). ### Impersonate a user in API calls (GA) A user assigned the Admin account type can impersonate other users in API calls, for example to retrieve and display the contents of their Documents folder in embedded content. If you use Sigma tenants, you can also perform admin tasks in tenant organizations by impersonating a tenant instead of a specific user with the API. For more details and an example test Python script, see [Impersonate users](/docs/impersonate-users#impersonate-users-for-api-calls). ### New API endpoints to manage email branding The following endpoints are now available to manage email branding for an organization in Sigma: * [Get the email branding settings for an organization](/reference/get-email-branding-setting) (`GET /v2/organizations/settings/emailBranding`) * [Update the email branding settings for an organization](/reference/update-email-branding-setting) (`PATCH /v2/organizations/settings/emailBranding`) * [Reset the email branding settings for an organization](/reference/delete-email-branding-setting) (`DELETE /v2/organizations/settings/emailBranding`) ### Sending and scheduling exports using the API on behalf of another user (Deprecated) The following API request options are now deprecated: * `sendAsUser` option for the [POST /v2/workbooks/\{workbookId}/send](/reference/send-workbook) endpoint. * `ownerId` option for the [POST /v2/workbooks/\{workbookId}/schedules](/reference/post-workbook-schedule) endpoint. Instead, use token-based impersonation to send or schedule an export on behalf of another user. See [Impersonate users to send and schedule exports](/docs/impersonate-users#impersonate-users-to-send-and-schedule-exports) for more details. ## Admin ### View the code representation of a document (Public beta) You can view the code representation of a workbook, data model, or report in the Sigma UI by opening the document menu and selecting **File** > **View code...**. For more information, see [Manage data models as code](/docs/manage-data-models-as-code), [Manage workbooks as code (Beta)](/docs/manage-workbooks-as-code), or [Manage reports as code (Beta)](/docs/manage-reports-as-code). ### Audit log events for AI settings The Sigma Audit Logs connection now includes a new `AI_SETTINGS` event category that records events related to AI provider and source configuration, including the following event types (each recorded with SUCCESS and FAILURE variants): * `AI_SOURCES_UPDATED` * `AI_PROVIDER_CONFIG_UPDATED` * `AI_PROVIDER_CONFIG_DELETED` These events include the following metadata columns: * AI Restrict to Configured Sources * AI Source Updates * AI Provider Config Type * AI Provider Connection Id For more details, see [Audit log events and metadata](/docs/audit-log-events-and-metadata). ### Audit log events for AI conversations The Sigma Audit Logs connection now includes an `AI_CONVERSATIONS` event category that records events related to AI interactions, including the following event types: * `AI_CONVERSATION_CREATED` * `AI_CONVERSATION_OPENED` * `AI_CONVERSATION_MESSAGE_SUBMITTED` * `AI_CONVERSATION_DELETED` * `AI_CONVERSATION_UPDATED` AI\_CONVERSATION audit logs are recorded when you have [chat history](/docs/configure-chat-history-agents) turned on for your organization and for any AI features that support chat history. For more details, see [Audit log events and metadata](/docs/audit-log-events-and-metadata). ## Data modeling ### Choose related datasets when migrating a dataset to a data model (GA) When you migrate a dataset to a data model, you can choose which related datasets to combine into a single data model instead of migrating all linked, joined, or referenced datasets together. Datasets you do not select remain available to migrate later. For more information, see [Migrate a dataset to a data model](/docs/migrate-a-dataset-to-a-data-model). ## Embeds ### Embed Sigma Assistant (Deprecated) Embedding Sigma Assistant as a standalone experience is deprecated and will reach end of support on March 16, 2027. Instead, consider embedding a customized Sigma agent, or Sigma Assistant in the workbook. For more details, see [Embed Sigma Assistant](/docs/embed-assistant). For details on what deprecation means, see the section on deprecated features in [Sigma product releases](/docs/sigma-product-releases). ## Reports ### Manage reports from a code representation (Beta) You can use the Sigma API to retrieve, update, and create reports based on a JSON or YAML representation. Using this representation with the Sigma API, you can manage, create, and review reports without using the Sigma UI. The following endpoints can now be used to manage reports based on a code representation: * [Get report](/reference/get-report#get-the-code-representation-of-a-report-beta) (`GET v2/reports/:reportId`) * [Create report](/reference/create-report#create-a-report-from-a-code-representation-beta) (`POST v2/reports`) * [Update a report from a code representation](/reference/update-report-contents) (`PUT v2/reports/:reportId/contents`) For more information, see [Manage reports as code (Beta)](/docs/manage-reports-as-code). For examples of various features represented as code, see the [Report representation example library](/docs/report-representation-example-library). ## Templates ### App templates (GA) Start building an app in Sigma with app templates. Explore an interactive preview of the app before adding it to your organization as a workbook. Adopt any of the following templates as a starting place for your own app development, or use the app template as an example for building your own app. Each app template includes sample data, input tables, and agents. The following app templates are available: * Project Management * Revenue Forecasting * Demand Planning * Pipeline Forecasting * Budget Variance Analysis * Territory Management * Shift Management * Marketing Analytics * Headcount Planning * Ticket Management For more details, see [Get started with templates](/docs/get-started-with-templates). ## Workbook features ### Apply translations in workbook or report export attachments (Beta) After adding translations to a workbook or report, you can select one of those translations to apply when exporting content. See [Apply translations in workbook or report export attachments (Beta)](/docs/manage-workbook-localization#apply-translations-in-workbook-or-report-export-attachments-beta). ## Bug fixes and improvements * For consistency and clarity, MCP tools used by Sigma agents have been renamed MCP connectors. * Templates shared with your entire organization with the **Share with everyone in your organization** option now appear in the "Shared with you" template gallery. * Users can now swap tables, schemas, and databases/catalogs when tagging a document version without **Can use** access to the entire connection. * When attempting to set up Azure OpenAI as an AI provider, the error "400 Unsupported value: 'temperature' does not support 0 with this model. Only the default (1) value is supported" no longer appears and the AI provider can be set up successfully. ## What's new in Sigma ## Admin ### Connect multiple Sigma organizations to one Slack workspace You can now connect multiple Sigma organizations to the same Slack workspace. See [Manage Slack integration](/docs/manage-slack-integration) for more information. ## AI ### Build workbooks and analyze data in ChatGPT using the Sigma plugin You can use the Sigma plugin for ChatGPT to search, explore, and analyze your data using natural language. When you’re ready to save and share your analysis, the plugin can build a workbook in Sigma. For more information on installing and using the plugin, see [Use the Sigma plugin for ChatGPT](/docs/use-the-sigma-plugin-for-ai-assistants). ## API ### Request and grant access to API connectors Users can now view an overview of all API connectors in their organization and request access to specific connectors. Admins or users with appropriate permissions can approve or deny these requests. See [Manage API credential and connection access](/docs/manage-api-credential-and-connection-access) for more information. ### New API endpoint to configure an AI provider The following endpoint is now available to configure an AI provider for an organization in Sigma: * [Configure the organization's AI provider](/reference/create-ai-config) (`POST /v2/organizations/settings/aiConfigs`) ### New API endpoint to list API credentials The following endpoint is now available to list API credentials in Sigma: * [List API credentials](/reference/list-credentials) (`GET v2/credentials`) The response includes the client ID, owner ID, and scopes of the credential, among other details. The client secret is not returned. ### New API endpoint to update permissions for an account type The following endpoint is now available to update permissions for an account type in Sigma: * [Update account type permissions](/reference/update-account-type-permissions) (`PATCH /v2/accountTypes/:accountTypeId/permissions`) Add or remove permissions from an account type to turn on or turn off access to functionality. Because the license associated with the account type permissions can change depending on the selected permissions, the license type is also included in the response. ### New API endpoint to manage team admins The following endpoint is now available to manage team admins for a team in Sigma: * [Update team admins](/reference/update-team-admins) (`PATCH /v2/teams/:teamId/teamAdmins`) ### New API endpoint to update a user attribute The following endpoints are now available to update the name, description, or default value of a user attribute in Sigma: * [Update a user attribute](/reference/update-user-attribute) (`PATCH /v2/user-attributes/:userAttributeId`) ### New API endpoints to manage comment settings The following endpoints are now available to manage comment settings for an organization in Sigma: * [Get the comment settings for an organization](/reference/get-comments-settings) (`GET /v2/organizations/settings/comments`) * [Update the comment settings for an organization](/reference/update-comments-settings) (`PATCH /v2/organizations/settings/comments`) You can use these endpoints to programmatically turn on or off commenting or annotating images in comments for an organization. ### New API endpoints to manage the time zone for an organization The following endpoints are now available to manage the configured time zone for an organization in Sigma: * [Get the timezone setting for an organization](/reference/get-timezone-setting) (`GET /v2/organizations/settings/timezone`) * [Update the timezone setting for an organization](/reference/update-timezone-setting) (`PATCH /v2/organizations/settings/timezone`) ### New API endpoints to manage sample connections The following endpoints are now available to manage sample connections for an organization in Sigma: * [Get the sample connection settings for an organization](/reference/get-sample-connection-settings) (`GET /v2/organizations/settings/sampleConnections`) * [Update the sample connection settings for an organization](/reference/update-sample-connection-settings) (`PATCH /v2/organizations/settings/sampleConnections`) ### New options for the Update a tag endpoint The [Update a tag](/reference/update-version-tag) (`PATCH /v2/tags/:tagId`) endpoint includes new options to update the description and color of a version tag. ### New options available for connections endpoints For Databricks connections, the [Get connection details](/reference/get-connection) (`GET /v2/connections/{connectionId}`), [List connections](reference/list-connections) (`GET /v2/connections`), [Create a connection](/reference/create-connection) (`POST /v2/connections`), and [Update a connection](/reference/update-connection) (`PUT /v2/connections/:connectionId`) endpoints now include the following fields: * `enableHiveMetastore` * `usePython` * `pythonComputeClusterId` Use these options to configure the Hive metastore and Python features for a Databricks connection programatically. ## Workbook features ### Databricks support for actions that call stored procedures Creating actions that call stored procedures is now supported for Databricks connections. ### Bug fixes and improvements * Materializations that are unable to complete due to an in-progress materialization no longer display as failed and instead indicate they were skipped. * Improved performance when editing large input tables. ## What's new in Sigma ## API ### New API endpoints to manage audit logging for an organization The following endpoints are now available to manage audit logging for an organization in Sigma: * [Get the audit logging setting for an organization](/reference/get-audit-logging-setting) (`GET /v2/organizations/settings/auditLogging`) * [Enable or disable audit logging for an organization](/reference/update-audit-logging-setting) (`PATCH /v2/organizations/settings/auditLogging`) ### New API endpoints to manage CSV upload settings The following endpoints are now available to manage CSV upload settings for an organization in Sigma: * [Get the CSV upload settings for an organization](/reference/get-csv-upload-settings) (`GET /v2/organizations/settings/csvUpload`) * [Update the CSV upload settings for an organization](/reference/update-csv-upload-settings) (`PATCH /v2/organizations/settings/csvUpload`) ### New option for the List datasets endpoint The [List datasets](/reference/list-datasets) (`GET /v2/datasets`) endpoint includes a new option to list datasets owned by a specific user by `ownerId`. ### Represent CSV tables in the code representation of a data model You can represent tables that use a CSV as a date source when reading and updating the code representation of a data model. For limitations, see [Manage data models as code](/docs/manage-data-models-as-code#limitations). For an example, see the [CSV table example](/docs/example-representation-data-model-with-a-csv-table) in the data model representation example library. ## Admin ### Additional account languages available The following new languages are now available to set as your organization's Account language in the Administration portal: * Chinese (Simplified) * Chinese (Traditional) * Dutch * French * French (Canada) * German * Italian * Japanese * Korean * Polish * Portuguese * Portuguese (Brazil) * Russian * Spanish * Spanish (Mexico) * Swedish * Thai * Turkish The account language controls the language of Sigma UI text for users in your organization and consumers of embedded analytics. Previously, only English variants were supported. For the full list of account languages, as well as how to set one for your organization, see [Set organization language and formatting region](/docs/manage-organization-language#supported-languages). ### Restrict Can contribute access to specific version tags When you share a workspace or folder and grant **Can contribute** access, you can now limit the versions that users and teams can explore to specific version tags. Previously, **Can explore** access to all documents and versions in the workspace or folder was granted to users and teams with **Can contribute** access. The version restriction applies to documents that other users create. Users with **Can contribute** access retain full access to the documents they create themselves. For more information, see [Restrict access to a folder using a version tag](/docs/share-a-folder#restrict-access-to-a-folder-using-a-version-tag). ### Select Microsoft integration permission levels (Beta) When setting up a Microsoft integration, you can now select between write only and read/write access levels. See [Permission levels (Beta)](/docs/manage-microsoft-integration#permission-levels-beta) in [Manage Microsoft integration](/docs/manage-microsoft-integration#permission-levels-beta). ## Data modeling ### Choose related datasets when migrating a dataset to a data model (Beta) When you migrate a dataset to a data model, you can choose which related datasets to combine into a single data model instead of migrating all linked, joined, or referenced datasets together. Datasets you do not select remain available to migrate later. For more information, see [Migrate a dataset to a data model](/docs/migrate-a-dataset-to-a-data-model). ## Functions and calculations ### Match on null values when performing a lookup (LookupMatchNulls function) When performing a lookup, you can now select **Match null values** to match rows where the join keys on both sides are `null`. You can also create lookups that match `null` values using the [LookupMatchNulls](/docs/lookupmatchnulls) function when writing a formula. For more information, see [Add columns through lookup](/docs/add-columns-through-lookup). ### TextJoin function (GA) You can use the textjoin function to join multiple strings of text data using a common delimiter. For more information, see [Textjoin](/docs/textjoin). ## Reports ### Export reports in PowerPoint format (Beta) You can now export and download reports as PowerPoint (.pptx) files. See [Share and export reports](/docs/share-and-export-reports). ### Export specific report pages You can now select one or more specific report pages to export. See [Send or schedule report exports](/docs/share-and-export-reports). ## Workbook features ### Drawers (GA) Use drawers to create a side panel that slides in to overlay the workbook page temporarily, allowing you to display new content and information at specific points in a workflow without disrupting other content. For more information, see [Use drawers to manage complex workflows](/docs/use-drawers-to-manage-complex-workflows). ## Bug fixes and improvements * The [Update a data model from a code representation endpoint](/reference/update-data-model-spec) now checks whether the `documentVersion` field matches the most recent document version before updating the data model. * Users assigned an account type with the **Manage users** permission enabled can now invite users as guest users. * When deploying documents that rely on team or user attribute assignments to enforce column-level security (CLS) rules, if the teams or user attributes exist on the tenant organization with the same name, the documents deploy and the CLS rules are enforced. If the teams or user attributes do not exist on the tenant organization, the documents fail to deploy to that tenant with an informative error message. ## What's new in Sigma ## AI ### Allow Assistant to search all sources (Beta) An admin can configure the default behavior of Sigma Assistant to use any data sources available to users or limit Assistant to only specific configured data sources. Users can always manually choose a source for Assistant to use from the sources that they have access to. Assistant performs best with [data models](/docs/data-modeling-best-practices). For more details, see [Configure AI features for your organization](/docs/configure-ai-features-for-your-organization). ### New model used for Snowflake (AWS) AI provider If you use Snowflake as your AI provider, and your Snowflake account is hosted on AWS, Sigma now uses Claude Sonnet 5 as the LLM. When you use Assistant in the workbook (Beta), or if Sonnet 5 is unavailable in your account, Sigma continues to use Claude Sonnet 4.5. For more details, see [Supported AI models](/docs/supported-ai-models). ## API ### Allow users with a Build license to generate client credentials (Beta) The **Create API key** account type permission is now available to allow non-admins to generate client credentials. See [Generate Sigma API client credentials](/reference/generate-client-credentials) and [Generate embed client credentials](/docs/generate-embed-client-credentials) for information on generating client credentials, and [Account type permission availability matrix](/docs/account-type-and-license-overview#account-type-permission-availability-matrix) for permission information. ### New API endpoints for managing organization settings The following endpoints are now available to programmatically manage organization settings in Sigma. Manage bulk copy settings, license upgrade request settings, and public embed settings: * [Get the bulk copy setting for an organization](/reference/get-bulk-copy-setting) (`GET /v2/organizations/settings/bulkCopy`) * [Update the bulk copy setting for an organization](/reference/update-bulk-copy-setting) (`PATCH /v2/organizations/settings/bulkCopy`) * [Get the license upgrade request setting for an organization](/reference/get-license-upgrade-requests-setting) (`GET /v2/organizations/settings/licenseUpgradeRequests`) * [Update the license upgrade request setting for an organization](/reference/update-license-upgrade-requests-setting) (`PATCH /v2/organizations/settings/licenseUpgradeRequests`) * [Get the public embeds setting for an organization](/reference/get-public-embeds-setting) (`GET /v2/organizations/settings/publicEmbeds`) * [Update the public embeds setting for an organization](/reference/update-public-embeds-setting) (`PATCH /v2/organizations/settings/publicEmbeds`) ### New API endpoints for managing plugins The following endpoints are now available to programmatically manage plugins in Sigma: * [List plugins](/reference/list-custom-plugins) (`GET v2/plugins`) * [Create a plugin](/reference/create-custom-plugin) (`POST v2/plugins`) * [Get a plugin](/reference/get-custom-plugin) (`GET v2/plugins/:pluginId`) * [Update a plugin](/reference/update-custom-plugin) (`PATCH v2/plugins/:pluginId`) * [Delete a plugin](/reference/delete-custom-plugin) (`DELETE v2/plugins/:pluginId`) ## Admin ### Materialization usage dashboard updates The **Materializations** tab in the **Usage** dashboard now reports materialization utilization ratio to help admins compare a materialization's compute cost against how often it's actually used. For every materialized element, Sigma tracks the number of queries that used it and divides that by the number of refreshes, giving you the average queries served per refresh. This data is available in two places: * The **Leaderboard** section now includes a *Utilization Ratio per Materialization* bar chart. * The **Documents** section's table now includes two new columns: **Queries** and **Utilization Ratio**. ## Reports ### Rename report pages You can now rename report pages to make them easier to identify. See [Rename report pages](/docs/edit-report-page-setup-headers-and-footers#rename-report-pages). ## Workbook features ### Convert deprecated hierarchies to hierarchy columns Hierarchies created in the deprecated **Manage hierarchies** popover can now be easily converted to hierarchy columns. Navigate to an existing hierarchy created from the popover, and select **Convert to new hierarchy** from the popover. See [Work with hierarchies](/docs/hierarchies) for more information on hierarchy columns. ## Bug fixes and improvements * Adding a tenant organization in the Azure AU region did not add a tenant in the correct region. * Duplicate action tools in agents no longer reference the same configuration as the action they were copied from, so changing a setting (like a connector, dynamic text URL, or stored procedure) on one action no longer overwrites that setting on the other action. * Formulas that return a date now display as expected in columns and list controls. * In workbooks, Sigma Assistant in build mode no longer crashes intermittently when asking the user a variety of question types. * Waterfall charts no longer throw errors when you hover an axis tick label with a numeric x-axis category. ## What's new in Sigma > Sigma release notes for Aug 21, 2026: Sigma CLI GA, materialization schedule and shortcut endpoints, data model CLS, and incremental plugin data fetching. ## API ### Access Sigma from the command line using the Sigma CLI (GA) You can access the Sigma REST API programmatically from your terminal using the Sigma command-line interface (CLI) tool. The Sigma CLI (`sigma`) simplifies interaction with the Sigma REST API by providing quality-of-life features to developers, such as authentication management, typed commands, and profile-based configuration. For more information, see [Sigma CLI](/docs/sigma-cli). ### Databricks HTTP path included in connection API responses For Databricks connections, the [Get connection details](/reference/get-connection) (`GET /v2/connections/{connectionId}`) and [List connections](/reference/list-connections) (`GET /v2/connections`) endpoints now include `httpPath` in the response. The field provides the HTTP path of the SQL warehouse and is not included when a user attribute sets the HTTP path. ### New API endpoints for managing materialization schedules (Beta) The following endpoints are now available for creating. updating, and deleting scheduled materializations of workbook and data model elements: * [Create a materialization schedule for a workbook element](/reference/create-materialization-schedule) (`POST /v2/workbooks/:workbookId/elements/:elementId/materializationSchedules`) * [Create a materialization schedule for a data model element](/reference/create-data-model-materialization-schedule) (`POST /v2/dataModels/:dataModelId/elements/:elementId/materializationSchedules`) * [Update a materialization schedule for a workbook element](/reference/patch-materialization-schedule) (`PATCH /v2/workbooks/:workbookId/elements/:elementId/materializationSchedules`) * [Update a materialization schedule for a data model element](/reference/patch-data-model-materialization-schedule) (`PATCH /v2/dataModels/:dataModelId/elements/:elementId/materializationSchedules`) * [Delete a materialization schedule for a workbook element](/reference/delete-materialization-schedule) (`DELETE /v2/workbooks/:workbookId/elements/:elementId/materializationSchedules`) * [Delete a materialization schedule for a data model element](/reference/delete-data-model-materialization-schedule) (`DELETE /v2/dataModels/:dataModelId/elements/:elementId/materializationSchedules`) Use these endpoints to create and manage materializations programmatically. For more details on scheduling materializations of workbook and data model elements, see [Schedule materialization for a data model or workbook (Beta)](/docs/schedule-materialization-for-a-data-model-or-workbook). ### New API endpoint for creating shortcuts The following endpoint is now available for creating shortcuts to documents and other items in Sigma: * [Create a shortcut](/reference/create-shortcut) (`POST /v2/shortcuts`) Use this endpoint to surface documents and other items in other folders or workspaces without duplicating them. For more details on creating and using shortcuts in Sigma, see [Add shortcuts to documents](/docs/add-shortcuts-to-documents). ## Data modeling ### Restrict access to data model elements (Beta) You can now configure data security rules for an entire data model element using column-level security (CLS). When configuring CLS in a data model, you can now select **All columns**, or select each column in the element individually, to restrict and hide the entire element for users who do not have access. Users editing the data model can still see the element while in the draft of the data model, regardless of if they have access to it according to the CLS rule. Users who do not have access to the element cannot see it in the data model overview page or source picker, and cannot access it in workbooks or data models that use it as a source. For more information, see [Restrict access to data model elements using CLS](/docs/column-level-security#restrict-access-to-data-model-elements-using-cls-beta). ### Update selected references when migrating a dataset to a data model After you migrate a dataset to a data model, you can now update the documents that use the dataset as a data source to use the new data model selectively instead of all at once. Update references in small batches to confirm that the data model returns the same results as the dataset before proceeding with the remaining references. For more information, see [Update selected references after a migration](/docs/migrate-a-dataset-to-a-data-model#update-selected-references-after-a-migration). ## Embeds ### Inbound event to refresh workbook data in embeds Use the `workbook:refresh` inbound JavaScript event to refresh the data in one element or all elements in a workbook. For more details, see [Inbound event reference](/docs/inbound-event-reference). ## Reports ### Move report elements to a new page You can now move report elements to a new page while preserving the position of the elements. See [Move elements to a new page](/docs/customize-element-size-position-and-layering#move-elements-to-a-new-page). ## Workbook elements ### Incremental data fetching for plugins When a plugin loads data from a workbook element, Sigma sends the data in batches of 25,000 rows. As of version 1.3.2 of the `@sigmacomputing/plugin` package, plugins can be configured so that each batch contains only the new rows, instead of re-sending every row already loaded, reducing load time for plugins that use data from large elements. Existing plugins continue to work without changes. To opt in, replace `usePaginatedElementData` with `useIncrementalElementData`. If you use the plugin development API without React Hooks, use `subscribeToIncrementalElementData`. For more information, see the [plugin development API on GitHub](https://github.com/sigmacomputing/plugin/blob/main/packages/plugin-sdk/README.md#useincrementalelementdata). ### Updated region data for maps Region maps now use updated boundary data. Regions whose names or codes changed no longer plot on the map and appear in the missing data modal. This includes Connecticut counties, whose borders were redrawn. US territories are now supported as US states, including Puerto Rico. For lists of supported country and US county names, as well as supported US zip codes, see [Maps - Region](/docs/maps#map---region). ## Bug fixes and improvements * The Sigma MCP connector can now query elements from data models. * The icons used to represent data models and data model table elements have been updated. Previously, the same icon was used to represent a data model and the elements within it. Now, data model elements are represented by the icon. ## 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. ## What's new in Sigma ## AI ### Agent skill for the Sigma CLI The `sigma-cli` skill provides instructions and reference materials that an AI assistant can use to call the Sigma REST API from the command line with the Sigma CLI. For more information, see [Install skills for AI assistants](/docs/install-skills-for-ai-assistants#sigma-cli). ### Assistant in build mode: complex dashboards (Beta) In workbooks, Sigma Assistant in build mode can now generate complex dashboards that span multiple pages sourced from related warehouse tables or an existing data model. Use plan mode to preview the layout of pages, elements, and data sources, then review the plan and make structure adjustments before Sigma builds anything. ## Admin ### Allow embed users to interact with each other (Beta) If you use Sigma Tenants and embed users are separated from each other in different organizations instead of through teams and workspaces, you might want to allow embed users to interact with each other. An admin can turn on a setting and allow the following interactions for embed users in an organization: * Comment on workbooks, including @-mentioning other users. * Share documents and folders with other users and teams. * Create and manage shared views. * View scheduled exports created by other users if they have edit access to the document. * View public teams that they don’t belong to. For more details, see [Manage embed user settings](/docs/manage-embed-user-settings). ## Data modeling ### Migrate warehouse views in datasets to data models When you migrate a dataset to a data model, warehouse views for the dataset are now included in the migration. Sigma creates a warehouse view for the corresponding table in the data model and preserves the original view name so that references to the view continue to work. For more details, see [How warehouse views are migrated](https://help.sigmacomputing.com/docs/migrate-a-dataset-to-a-data-model#how-warehouse-views-are-migrated). ## Templates ### Snowflake Object Usage template Track usage of tables, views, columns, and more for Snowflake connections in Sigma with the Snowflake Object Usage template. Answer questions like: * How many people actually use this table? * Which users have been able to see a certain column? * Which Sigma workbooks use this column? * What tables are used by this Sigma workbook? Setup instructions are available in Sigma QuickStarts: [Snowflake Object Usage Template setup](< https://quickstarts.sigmacomputing.com/guide/snowflake_object_usage_template_setup/index.html>). For more information on templates, see [Get started with templates](/docs/get-started-with-templates). ## Workbook elements ### Drawers (Beta) Use drawers to create a side panel that slides in to overlay the workbook page temporarily, allowing you to display new content and information at specific points in a workflow without disrupting other content. For more information, see [Use drawers to manage complex workflows](/docs/use-drawers-to-manage-complex-workflows). ### Stack layout for containers (Beta) You can use the **Stack** layout type to create containers that change their layouts responsively as you add new elements. Similar to the [CSS Flexible Box Layout Model](https://en.wikipedia.org/wiki/Flexbox), stacks arrange all elements automatically based on a specified layout direction, distribution, and alignment, rather than requiring you to manually place each element in a grid. For more information, see [Use stacks to make responsive layouts](/docs/use-stacks-to-make-responsive-layouts). ## Workbook features ### Trigger workbook action sequences with webhooks (Beta) Configure an automated action sequence triggered by a webhook. You can also pass variables from the webhook for the action sequence to reference. To run a webhook-triggered action sequence, call the [Send to a webhook](/reference/webhooks) (`POST /v2/webhooks/:workbookId/:sequenceId`) endpoint. For more information, see [Create a webhook-triggered action sequence](/docs/configure-action-sequences-to-run-automatically#create-a-webhook-triggered-action-sequence). ## Bug fixes and improvements * CSV uploads with high column counts (roughly 150 or more) now save correctly as data sources. * In workbooks, Sigma Assistant in build mode no longer crashes intermittently when asking the user a variety of question types. * Previously, the element crumb menu overlapped with elements on-hover, causing it to obscure options. Now, it adaptively moves to a position where it doesn't obscure workbook contents. * When using a warehouse agent with Sigma Assistant, more information is available in the conversation about what actions the agent is taking. With the additional detail, you can review the steps the agent took to calculate an answer, helping validate actions taken by the agent or identify errors in logic that you can correct with follow-up messages. * When you create a child table element that transposes columns to rows from a parent element with column-level security rules configured, the child table no longer displays hidden column names to users who should not have access or displays "No access" for column values to users who should have access to the column. * You no longer need to click **Cancel** twice in order to successfully cancel a materialization in progress. ## What's new in Sigma > Sigma release notes for Jul 31, 2026: Sigma plugin for ChatGPT, Amazon Bedrock GA, Sigma Tenants GA, migrate a dataset to data model API, the BusinessDays function, and more. ## AI ### Sigma plugin for ChatGPT You can now install the Sigma MCP server for ChatGPT in one click using the Sigma plugin. For more information, see [Use the Sigma MCP server](/docs/use-sigma-mcp-server). ### Support for Amazon Bedrock AI provider (GA) Amazon Bedrock is now a supported AI provider, letting you use Anthropic foundation models with Sigma AI-powered features. For setup instructions, see [Add Amazon Bedrock as an AI provider](/docs/manage-external-ai-integrations#add-amazon-bedrock-as-an-ai-provider). ### Assistant in build mode: multiple choice prompts (Beta) In workbooks, Sigma Assistant in build mode can now respond with multiple choice prompts that present predefined response options users can select. These prompts help clarify intent, guide users through a workflow, and capture input in a structured format. ### Assistant in build mode: proposed feedback (Beta) In workbooks, Sigma Assistant in build mode now offers to send your feedback to Sigma when it detects dissatisfaction with a response. You can review and edit the feedback before submitting, or you can dismiss the proposal and resume your session. ## API ### New API endpoint for migrating a dataset to a data model (Beta) The following endpoint is now available to migrate a dataset to a data model: * [Migrate a dataset to a data model](/reference/migrate-dataset-to-data-model) (POST /v2/datasets/:datasetId/migrate) Use this endpoint to migrate datasets to data models programmatically, or pass `dryRun: true` to assess the impact of a migration. For more details on how datasets are migrated to data models in Sigma, see [Migrate a dataset to a data model](/docs/migrate-a-dataset-to-a-data-model). ### New API endpoint for restoring a workbook version The following endpoint is now available to restore a workbook to a previous version: * [Restore a workbook version](/reference/restore-workbook-version) (POST /v2/workbooks/:workbookId/restoreVersion) You can use this endpoint to restore previous versions of workbooks programmatically. For more details on version history for workbooks, see [Workbook versions and version history](/docs/workbook-versions-and-version-history). ## Admin ### Sigma Tenants (GA) Sigma Tenants let you set up a multitenant architecture with multiple Sigma organizations to centralize governance while supporting self-contained and isolated tenants. You can create tenants in the same region or different regions offered by the same cloud provider. Deploy folders, data models, reports, and workbooks to tenant organizations and provide curated experiences to users on different tenants. [Example use cases](/docs/deployment-use-cases-and-examples) for Sigma Tenants include: * Comply with data residency requirements by placing tenants in different regions. * Fully isolate data for different customers as a managed service provider. * Centralize governance for multiple business units, but isolate the business units from each other. Different deployment architectures are supported. Deploy content from the parent organization to tenants or from one tenant to other tenants. See [Deploy content to tenant organizations](/docs/deploy-content-to-tenant-organizations). Sigma Tenants is a premium feature. For more details, see [Sigma Tenants](/docs/multitenancy-at-sigma). ### Audit log events for tenant deployments The Sigma Audit Logs connection now includes a `TENANTS` event category that records events related to deployment management, including the following event types: Deployed file management: * DEPLOYMENT\_ITEMS\_SYNCED Deployment policy configuration: * DEPLOYMENT\_POLICY\_CREATED * DEPLOYMENT\_POLICY\_UPDATED * DEPLOYMENT\_POLICY\_TENANTS\_ADDED * DEPLOYMENT\_POLICY\_TENANTS\_REMOVED * DEPLOYMENT\_POLICY\_DELETED * SOURCE\_SWAP\_POLICY\_CREATED * SOURCE\_SWAP\_POLICY\_UPDATED * SOURCE\_SWAP\_POLICY\_DELETED * TENANT\_DEPLOYMENT\_CAPABILITY\_GRANTED * TENANT\_DEPLOYMENT\_CAPABILITY\_REVOKED * USER\_ATTRIBUTE\_TENANT\_SET * USER\_ATTRIBUTE\_TENANT\_DELETED For more details, see [Audit log events and metadata](/docs/audit-log-events-and-metadata). ### Create tenant audit log storage integrations (Beta) Admins can now create storage integrations to export tenant audit logs to cloud storage. See [Configure tenant audit log storage integrations](/docs/create-and-manage-tenant-organizations#configure-tenant-audit-log-storage-integrations). ## Functions and calculations ### BusinessDays function The **BusinessDays** function calculates the number of weekdays between two dates. The count includes the start and end dates, and excludes Saturdays and Sundays. For more information, see [BusinessDays](/docs/businessdays). ## Workbook elements ### Text element supports "mailto:" link scheme When configuring a link on text in a text element, you can now configure the link with a `mailto:` scheme to send an email when the link is selected. For more information, see [Text elements](/docs/text-elements). ## Workbook features ### Create tables from an array with unnest (GA) You can create a table from an array of values using the **Unnest** feature. After selecting a data source and identifying a column with array data, **Unnest** creates a new table element with one row for each item in the array. For more information, see [Create a table from an array](/docs/create-a-table-from-an-array). ## Bug fixes and improvements * Previously, after tagging a document in a folder added to a deployment policy, the document did not deploy as expected. Now, the document deploys as expected. * In workbooks, Sigma Assistant in build mode now reliably preserves Top-N SQL results when building charts, so charts show only the requested top results. * Previously, the API credentials dropdown did not allow you to search credentials. Now, search is available after opening the dropdown. * When adding source swap policies to a deployment policy, the full list of source swap policies now appears. * You can now remove bold from totals and subtotals using conditional formatting options. ## What's new in Sigma ## AI ### Anthropic as an AI provider (Beta) 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 LLM model and must also configure a second AI provider with an embeddings model available. For more details, see [Add Anthropic as an AI provider](/docs/manage-external-ai-integrations#add-anthropic-as-an-ai-provider). ### Improved AI columns support for Databricks (Beta) When creating AI columns on a Databricks connection, you can now: * Configure the **Response format** of the column output. * View usage information on AI columns in the [Usage dashboard](/docs/usage-overview). See [Create AI columns (Beta)](/docs/create-ai-columns). ## AI apps ### Call GraphQL endpoints in Sigma API connectors You can configure an API connector in Sigma with a GraphQL request body, allowing you to perform GraphQL queries or mutations in a **Call API** action in a Sigma workbook. For more information, see [Configure a request body for a GraphQL endpoint](/docs/configure-api-credentials-and-connectors-in-sigma#configure-a-request-body-for-a-graphql-endpoint). ## API ### Access Sigma from the command line using the Sigma CLI You can access the Sigma REST API programmatically from your terminal using the Sigma command-line interface (CLI) tool. The Sigma CLI (`sigma`) simplifies interaction with the Sigma REST API by providing quality-of-life features to developers, such as authentication management, typed commands, and profile-based configuration. For more information, see [Sigma CLI](/docs/sigma-cli). ### Additional write destination information in connection API responses The [Get connection details](/reference/get-connection) (`GET /v2/connections/{connectionId}`) and [List connections](/reference/list-connections) (`GET /v2/connections`) endpoints now return the write destination for connections that use OAuth. ### Create a connection endpoint now supports Starburst and Azure SQL DB The [Create a connection](/reference/create-connection) (`POST /v2/connections`) endpoint now supports two additional connection types: **Starburst** and **Azure SQL DB**. ### New API endpoint to convert workbooks to reports The following endpoint is now available to convert workbooks to reports: * [Convert a workbook to a report](/reference/convert-workbook-to-report) (`POST /v2/workbooks/{workbookId}/convertToReport`). ### New OAuth options for Create a connection and Update a connection endpoints The [Create a connection](/reference/create-connection) (`POST /v2/connections`) and [Update a connection](/reference/update-connection) (`PUT /v2/connections/{connectionId}`) endpoints now support configuring connection-level OAuth using the `isIndependentOAuth` option. You can now provide OAuth credentials specific to each connection, including the client ID, client secret, scopes, and authorization server. ### New option for Export data from a report endpoint The [Export data from a report](/reference/export-report) (POST /v2/reports/:reportId/export) now allows exporting specific pages of data by providing a `pageId`. ### New options for Create a connection and Update a connection endpoints The [Create a connection](/reference/create-connection) (`POST /v2/connections`) and [Update a connection](/reference/update-connection) (`PUT /v2/connections/{connectionId}`) endpoints now include additional options: * Connection queue size * Writeback destination descriptions (Snowflake and Databricks) * Dynamic tables (Snowflake only) * Python warehouse and packages (Snowflake only) ### New report endpoints available The following report endpoints are now available: * [Get version history for a report](/reference/get-report-version-history) (`GET /v2/reports/{reportId}/version-history`) * [Duplicate a tagged report](/reference/copy-tagged-report) (`POST /v2/reports/{reportId}/tag/{versionTag}/copy`) * [Swap report data sources](/reference/source-swap-report) (`POST /v2/reports/{reportId}/swapSources`) * [List SQL queries in a report](/reference/list-report-queries) (`GET /v2/reports/{reportId}/queries`) * [List report controls](/reference/list-report-controls) (`GET /v2/reports/{reportId}/controls`) * [List lineage for a report](/reference/list-report-lineage-tree) (`GET /v2/reports/{reportId}/lineage`) * [List columns for all elements in a report](/reference/list-report-columns) (`GET /v2/reports/{reportId}/columns`) Element endpoints * [List elements in a report](/reference/list-report-elements) (`GET /v2/reports/{reportId}/elements`) * [List lineage for a report element](/reference/list-report-element-lineage) (`GET /v2/reports/{reportId}/lineage/elements/{elementId}`) * [Get the SQL query for a report element](/reference/get-report-element-query) (`GET /v2/reports/{reportId}/elements/{elementId}/query`) * [List columns for a report element](/reference/list-report-element-columns) (`GET /v2/reports/{reportId}/elements/{elementId}/columns`) Grant endpoints * [Grant permissions on a report](/reference/create-report-grant) (`POST /v2/reports/{reportId}/grants`) * [Delete a report grant](/reference/delete-report-grant) (`DELETE /v2/reports/{reportId}/grants/{grantId}`) Page endpoints * [List report pages](/reference/list-report-pages) (`GET /v2/reports/{reportId}/pages`) * [List elements in a report page](/reference/list-report-page-elements) (`GET /v2/reports/{reportId}/pages/{pageId}/elements`) Tag endpoints * [List tags for a report](/reference/list-report-tags) (`GET /v2/reports/{reportId}/tags`) * [Tag a report](/reference/tag-report) (`POST /v2/reports/tag`) * [Remove a tag from a report](/reference/delete-tagged-report) (`DELETE /v2/reports/{reportId}/tags/{tagId}`) ### Snowflake semantic views included in the response for List lineage endpoints The [List lineage for a workbook](/reference/list-lineage-tree) (GET /v2/workbooks/\{workbookId}/lineage) and [List lineage for a data model](/reference/list-data-model-lineage-tree) (GET /v2/dataModels/\{dataModelId}/lineage) endpoints now include Snowflake semantic views that are used as a data source in the response. Semantic views are listed with a type of `semantic-view` and include `semanticViewId` and `semanticViewTable` fields. ## Admin ### Allow embed users to export to Slack or Microsoft destinations (Beta) You can now allow embed users to export to Slack, Microsoft Teams, or Microsoft SharePoint using the integrations set up in your Sigma organization. An admin can turn on this option for each destination, and embed users can only perform exports that their permissions allow. For more details, see [Manage embed user settings](/docs/manage-embed-user-settings). ## Infrastructure ### Format numbers and dates with :lng URL parameter You can now format numbers and dates in the Sigma UI according to the locale associated with the current language. To apply a language to a workbook, use the `:lng` query string parameter in the URL with the syntax `:lng=`. See [Manage workbook localization](/docs/manage-workbook-localization) for more details. ## Performance ### Universal result cache on connections authenticated with OAuth You can use the universal result cache on connections authenticated with OAuth by configuring queries to run with service account credentials. For more information, see [Manage universal result cache](/docs/manage-universal-result-cache) and [Run a workbook with service account credentials](/docs/run-a-workbook-with-service-account-credentials). ## Reports ### Convert workbooks to reports (GA) The ability to convert workbooks to reports is now generally available. See [Convert workbooks to reports](/docs/convert-workbooks-to-reports). ## Search and discovery ### New homepage contents (Beta) Sigma Home now includes a **Popular** section and a **Your work** section: * In the **Popular** section, you can view top activity for your organization, for a selected team of which you are a member, or your own top activity. * In the **Your work** section, you can view a homepage customized for you, recent, and favorite documents. When you select an option, the home page continues to display that option first when you open Sigma in the future. For more details, see [Get around in Sigma](/docs/get-around-in-sigma). ## User profile ### Delete a current connection session You can now delete an active connection session. Deleting a connection session signs you out from the connection. See [Delete a current connection session](/docs/refresh-connection-sign-in-sessions#delete-a-current-connection-session). ## Workbook elements ### Treemaps (Beta) Build a treemap to display values as nested boxes sized in proportion to other values within the same category. Treemaps allow you to easily compare values across product categories, regions, fiscal periods, and more. For more information, see [Build a treemap](/docs/build-a-treemap). ## Workbook features ### Cancel a materialization in progress You can now request to cancel the materialization of a workbook or data model element that is currently in progress or pending. For more information, see [Cancel a materialization in progress](/docs/schedule-materialization-for-a-data-model-or-workbook#cancel-a-materialization-in-progress). ### Configure data loading (GA) Configure data loading to help accelerate the performance of some workbook elements. Data loading manages when a data element performs data prefetch queries using Alpha Query, which can optimize performance and reduce the number of queries sent to your data platform. For more details on optimizing document performance, see [Best practices for improved document performance](/docs/best-practices-for-improved-performance). For information about configuring data loading, see [Configure data loading](/docs/configure-data-loading). ### Create an API connector from a cURL request You can configure an API connector based on details from a client URL (cURL) request by using the **Import from cURL** option when creating a new API connector. For more information, see [Create an API connector based on a cURL request](/docs/configure-api-credentials-and-connectors-in-sigma#create-an-api-connector-based-on-a-curl-request). ### Parse the response of a **Call API** action into a table (Beta) You can use a custom action variable in an API connector with the **Insert row(s)** action to parse an API response array into multiple rows in an input table. For more information, see [Configure API credentials and connectors in Sigma](/docs/configure-api-credentials-and-connectors-in-sigma#create-custom-action-variables-for-an-api-connector). ## Bug fixes and improvements * A Sigma agent was unable to use a Snowflake Cortex Agent with spaces in the name. * An error no longer appears when trying to grant access to a stored procedure in the connection browser. * Previously, the **Profile** screen contained a section labelled **MCP** that contained details like your **Sigma MCP URL**. This content has moved to the **Integrations** screen. * The AI usage dashboard no longer intermittently fails to load with an error indicating "Document was archived: Warehouse Scope "SAMPLE\_CONNECTION\_PRODUCTION" no longer exists". ## What's new in Sigma ## AI ### Add data model tables as data sources for agents (Beta) You can now add relevant data model tables as data sources for Sigma agents. For instructions, see [Build Sigma agents](/docs/build-agents). ### Assistant in build mode: formula join keys (Beta) In workbooks, Sigma Assistant in build mode can join tables on formulas and expressions, not just raw columns. Joins can match on computed dates, normalized text, or any formula-derived value. ### Assistant in build mode: balance sheet creation (Beta) In workbooks, Sigma Assistant in build mode now offers guided balance sheet creation that adapts to your data structure and supports both snapshot and comparative layouts. This capability supplements the existing built-in workflows for profit and loss statements and sales forecasting to support financial use cases with more consistent structure and faster setup. ## Admin ### AI usage dashboard The AI usage dashboard provides details about token consumption, conversations, user engagement, and models used when interacting with Sigma AI features like Sigma Assistant and Sigma agents. You can also ask natural language questions of the AI usage analyst agent and add the dashboard to your workspace to set up custom alerts for token thresholds. For more details, see [AI usage dashboard](/docs/ai-usage). ### Ask natural language questions about usage data The Users and Document Activity usage dashboards now provide the option to ask an AI agent natural language questions about the data in the dashboard. To interact with the agents, you must have an AI provider configured for your Sigma organization. No tokens are consumed unless you interact with the agent. ### Deploy folders to tenants (Beta) If you use Sigma Tenants, you can deploy folders and all workbooks, reports, and data models in the folder, to tenant organizations. Explorations, shortcuts, and other unsupported files in a folder are not deployed. For details, see [Deploy content to tenant organizations](/docs/deploy-content-to-tenant-organizations). ### Deploy reports to tenant organizations (Beta) You can now deploy reports to tenant organizations. For more details, see [Deploy content to tenant organizations](/docs/deploy-content-to-tenant-organizations). ### Redeploy documents to tenants (Beta) When working with deployment policies to deploy documents to tenant organizations, you can manually redeploy documents to tenants. In a deployment policy, locate the tenant on the **Deploy to** tab, then select **Redeploy to tenant**. For more details, see [Deploy content to tenant organizations](/docs/deploy-content-to-tenant-organizations). ### Visualize dependencies in a deployment policy When deploying documents to tenant organizations, dependencies such as data models used by a workbook as a data source, or a workbook opened from an action in another workbook, are also deployed. You can now review dependent documents deployed to tenant organizations in the deployment policy. ## Templates ### AI spend templates to visualize cost of AI tools Use the AI spend templates to visualize costs associated with AI tool usage. Sigma provides 3 templates: * [Claude spend template](/docs/claude-spend-template) to visualize usage of Claude Enterprise AI tools from Anthropic. * [OpenAI spend template](/docs/openai-spend-template) to visualize usage of AI tools like ChatGPT, Codex, and others. * [Snowflake AI spend template](/docs/snowflake-ai-spend-template) to visualize usage of Snowflake Cortex AI functions. If Sigma is connected to a data platform that contains the relevant cost data, you can use the relevant template to visualize spend. ### App templates (Beta) Start building an app in Sigma with app templates. The following templates are available to use and adopt as a starting place for your own app or an example for how to build your own app. Each app template includes sample data, input tables, and agents. The following app templates are available: * Project Management * Revenue Forecasting * Demand Planning * Pipeline Forecasting * Budget Variance Analysis * Territory Management * Shift Management * Marketing Analytics * Headcount Planning * Ticket Management For more details, see [Get started with templates](/docs/get-started-with-templates). ## Workbook elements ### Icon support for buttons and the navigation element (GA) You can customize layouts and guide users by setting an icon for button elements, as well as for options in the navigation element. Sigma provides a searchable library of ready-to-use icons to use. For more information, see [Button elements](/docs/button-elements#customize-button-properties) and [Use the navigation element to guide user exploration](/docs/use-the-navigation-element-to-guide-user-exploration#set-icons-for-navigation-options). ## Workbook features ### Custom email branding and SMTP server configuration has moved Custom email branding and SMTP server configuration options are now located in the **Email customization** tab in **Administration** > **Scheduled exports & actions**. These options were previously located in the **Settings** tab. ### Hide sender information in export emails You can now use the **Hide sender information** setting to hide the email body line that shows which user scheduled or sent the export. This only affects the email body, not the “From” field in the email. See [Customize email branding](/docs/custom-email-branding). ## Bug fixes and improvements * Previously, the tooltips on certain UI elements did not respect the **Invert tooltips** workbook theme setting. Now, they correctly follow the theme setting. * Previously, Sigma overwrote all `id` values in a code representation used with the [Create a data model from a code representation](/reference/create-data-model-spec) endpoint. Now, `id` values are preserved as written. * When creating a linked input table in a workbook, Sigma Assistant in build mode now prompts you to select a valid write-back schema. This update prevents the creation of linked input tables on connections that aren't write-back enabled. * When deploying documents to tenant organizations, if custom page visibility is applied to a workbook tab and a team with the same name exists in the tenant organization, the document is deployed and the page visibility is maintained. If a document contains custom page visibility and the teams specified do not exist in a tenant organization, the document fails to deploy. ## What's new in Sigma > Sigma release notes for Jul 10, 2026: Customize first agent message, insert row(s) action, and more. ## AI ### Customize first agent message (Beta) Customize the first message sent by a Sigma agent. You can set a fixed message or a specific prompt for a generated message. For example, modify an agent to send a specific text greeting like "Welcome to Sigma!" as a fixed message, instead of the agent using the AI provider to generate a message. For more details, see [Customize the first agent message](/docs/build-agents#customize-the-first-agent-message). ## AI apps ### Insert row(s) action (Beta) Configure an **Insert row(s)** action to add one or more rows in a target input table. You can insert new data that you define, or insert rows from an existing source in the workbook, such as a table, input table, or action variable. For more information, see [Create actions that modify input table data](/docs/create-actions-that-modify-input-table-data). ## API ### Elements sourced from CSV files included in the response for List lineage endpoints The [List lineage for a workbook](/reference/list-lineage-tree) (`GET /v2/workbooks/{workbookId}/lineage`) and [List lineage for a data model](/reference/list-data-model-lineage-tree) (`GET /v2/dataModels/{dataModelId}/lineage`) endpoints now include uploaded CSV files that are used as a data source in the response. CSV files are listed with a type of `csv-upload` and include a `csvId` field. ### New API endpoint to revoke user OAuth tokens The following endpoint is now available to revoke user OAuth tokens in Sigma: * [Revoke a user's OAuth tokens](/reference/revoke-member-tokens) (`POST /v2/members/:memberId/revoke`) Use this endpoint to revoke a user’s OAuth refresh tokens used for OIDC single sign-on and warehouse connections, so Sigma can no longer issue new access tokens on the user’s behalf. When you use this endpoint to revoke a user's tokens, existing OAuth sessions cannot be refreshed but an existing user session is not interrupted and issued tokens expire with their usual TTL. ### New options for export endpoints The following endpoints include a new option to add users or teams as Cc or Bcc recipients: * [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}`) * [Export a report](/reference/send-report) (`POST /v2/reports/{reportId}/send`) * [Add report schedule](/reference/create-report-schedule) (`POST /v2/reports/{reportId}/schedules`) * [Update a report schedule](/reference/update-report-schedule) (`PATCH /v2/reports/{reportId}/schedules/{scheduleId}`) ### New options for the list connection paths endpoint The [List connection paths](/reference/list-connection-paths) (`GET /v2/connections/paths`) endpoint includes a new option to filter by `connectionId`. ## Admin ### Localization settings renamed in Administration portal The following have been renamed in the \**Account* tab of the Administration portal: * The **Locale** section is now called **Localization** * The **Account locale** setting is now called **Account language** The functionality of these settings remains the same. ## Data modeling ### Work with Databricks Unity Catalog metric views in Sigma (Beta) You can now browse and query Databricks metric views in workbooks and data models. Metric views allow you to model metrics, dimensions, and joins in a declarative, version-controlled, and queryable format. Work with the metrics and dimensions defined in the metric view: * Browse the metric views in your Databricks connection in the data catalog. * Build a table in a data model using the metric view as a source. * Add tables, pivot tables, and charts to a workbook that use the metric view as a source. * Query the view with custom SQL. For more details, see [Query Databricks metric views in Sigma (Beta)](/docs/query-databricks-metric-views-in-sigma). ## Performance ### Universal result cache (Beta) You can cache recent queries in an external storage integration to reduce warehouse compute costs and improve performance. For more information, see [Manage universal result cache](/docs/manage-universal-result-cache) ## Reports ### Convert workbooks to reports (Beta) You can convert an existing Sigma workbook into a new report. This allows you to take advantage of report features like pixel-level formatting and more reliable exports without manually rebuilding your workbook. See [Convert workbooks to reports (Beta)](/docs/convert-workbooks-to-reports) for more information. ## Resources ### New documentation site design The Sigma documentation has a new design with the following new functionality: * A redesigned homepage * A dedicated section for function reference * A robust API explorer with a dedicated view for code representation endpoints. * View any documentation page as raw Markdown, or start a chat with Claude or ChatGPT with the Markdown version of a documentation page. The documentation MCP server now only has 1 tool available, called `searchDocs` that searches the docs and returns relevant docs sections and source URLs. ## Workbook elements ### Add icons to the button element (Beta) You can customize the button element by adding an icon next to the label text or replacing the label text entirely with a standalone icon. For more information, see [Button elements](/docs/button-elements#customize-button-properties). ## Workbook features ### Find in table (GA) The **Find in table** feature is now generally available. **Find in table** allows you to locate specific values in a table or input table. See [Find a specific value in a table or input table](/docs/find-a-value-in-a-table). ### Manage locales panel renamed The **Manage locales** panel has been renamed to **Manage translations**. The functionality of the panel and the settings within remains the same. ## Bug fixes and improvements * After migrating to a new documentation site, the documentation MCP server was unavailable with error messages referencing issues with an "FAI chat service". * An inactive tag on a version displayed the timestamp for when the tag was last set on any version of the workbook, instead of when the tag was set on that specific version. * When copying and pasting multiple elements, the layout position of the elements when copied is preserved when pasting. * When using Sigma Assistant with a Snowflake Cortex Agent, the agent failed to use the default warehouse set for the user. ## What's new in Sigma > Sigma release notes for Jun 26, 2026: monitor MCP queries, Sigma Assistant in the workbook: plan and build modes, and more. ## AI ### Monitor MCP queries You can now use the `"kind":"mcp"` tag to monitor queries sent by the Sigma MCP server. This can be helpful to monitor costs or usage associated with the MCP server. See [Monitor MCP queries](/docs/use-sigma-mcp-server#monitor-mcp-queries) for more information. ### Sigma Assistant in the workbook: plan and build modes (Beta) Sigma Assistant can now help you design and build workbooks using natural language prompts. When editing a workbook, Assistant can explore any data source you have permission to access, enabling you to ask questions, provide instructions, give feedback, and iterate as needed to build a complete dashboard or AI app. You can use Assistant in plan and build modes to do the following: * Build dashboards with charts, tables, KPIs, and filters to visualize and explore your data. * Set up structured data entry with forms, input tables, and actions. * Accelerate the development of AI-powered apps from idea to working product. For more information, see [Use Sigma Assistant to build dashboards and apps](/docs/use-ai-to-build-dashboards-and-apps). > **Info** > > When editing a workbook, Assistant is only available to customers who meet certain conditions. For more information, contact your Account Executive. ### Upcoming changes to documentation MCP server (Beta) Starting Monday, July 6, the documentation-specific MCP server will only have one tool available: `searchDocs`. The `searchDocs` tool searches the Sigma documentation and returns relevant sections of content and source URLs. **Before the change:** The Sigma documentation MCP server is available at `https://help.sigmacomputing.com/mcp` and provides multiple tools, including `search` and `fetch` for searching and retrieving documentation pages. **After the change:** The Sigma documentation MCP server has only one tool called `searchDocs` that searches the docs and returns relevant docs sections and source URLs. The existing MCP server URL continues to work. The MCP server will also be available at `https://help.sigmacomputing.com/_mcp/server` ## Admin ### Manage tenant attributes from the parent organization (Beta) If you use Sigma Tenants, you can manage attributes for tenant organizations from the parent organization. Create and assign attributes in tenant organizations from the **Tenants** section of the Administration portal. For more details, see [Create and manage tenant organizations](/docs/create-and-manage-tenant-organizations). #### Sigma now supports the Azure Australia region Sigma is now deployed in Azure Australia (australiaeast). This region, located in New South Wales, gives customers in Australia lower latency and enhanced performance when connecting to Sigma. A disaster recovery region is also available (australiasoutheast). ## Workbook elements ### Ad hoc calculated column support Adding ad hoc calculated columns in pivot tables is now supported. This allow you to perform one-off calculations in a pivot table column, without modifying the underlying dataset or restructuring your pivot table. For more information, see [Create ad hoc calculations](/docs/create-ad-hoc-calculations). ### Create tables from an array with unnest (Beta) You can create a table from an array of values using the **Unnest** feature. After selecting a data source and identifying a column with array data, **Unnest** creates a new table element with one row for each item in the array. For more information, see [Create a table from an array](/docs/create-a-table-from-an-array). ### Responsive segmented controls When the values for a segmented control are too long to fully display when viewing or editing a document, the control appears as a drop-down menu instead of truncating the text in the control. | Appearance | Display | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Before the change | ![A segmented control labeled New England State with its values truncated to fit the element width, showing abbreviated labels such as Co… and Mas….](/_fern-img/9a2d54a7947ec797d1da487afcff5e9bf57be7365d071c3f2de4c315f104ed47.webp) | | After the change | ![A segmented control labeled New England State collapsed into a drop-down menu, open to show the values Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont.](/_fern-img/126375076bb99e88b8d2bae7440a44a4a9221509a58db9ac63f0455ce840a1c0.webp) | For more details, see [Create and configure a segmented control](/docs/segmented-control). ## Bug fixes and improvements * Documents containing custom SQL elements failed to deploy when the source swap policy associated with the deployment policy defined specific paths in the connection to swap to or from. * Improved the loading time for KPI charts when opening a workbook for the first time. * When using warehouse agents with Sigma Assistant, the name and email address of the user is shared with the agent. ## What's new in Sigma > Sigma release notes for Jun 18, 2026: AI column support for Databricks connections, new option for Sync a connection by path endpoint, and more. ## AI ### AI column support for Databricks connections (Beta) You can now create and use AI columns on Databricks connections. AI columns allow you to construct dynamic prompts that reference specific table columns, which can be helpful for tasks like enriching, summarizing, and classifying data. See [Create AI Columns (Beta)](https://help.sigmacomputing.com/docs/create-ai-columns). ## API ### New option for Sync a connection by path endpoint The [Sync a connection by path](/reference/sync-connection-path) endpoint (`POST /v2/connections/{connectionId}/sync`) now allows syncing all objects in a connection by providing an empty path (`[]`). ### New option included in API endpoint response The following endpoints now include a `parentSourceUrlId` in the response when returning details about documents deployed to a tenant organization. The `parentSourceUrlId` can be used to identify the document in the parent organization that was deployed. * [List files](/reference/list-files) (`GET v2/files`) * [List member files](/reference/list-accessible-inodes) (`GET /v2/members/{memberId}/files`) ## Admin ### Deployment policies deploy documents referenced in "Open Sigma document" actions If a document deployed to a tenant organization has an "Open Sigma document" action configured, the target document of that action is also deployed to the tenant organization and the action is updated to open the deployed document. For more details, see [What gets deployed to a tenant](https://help.sigmacomputing.com/docs/deploy-content-to-tenant-organizations#what-gets-deployed-to-a-tenant). ## Bug fixes and improvements * After making edits in a securely embedded workbook or a Sigma Public app and leaving the draft without publishing, edits were no longer visible in the draft. * After releasing warehouse agents for Sigma Assistant, asking questions of data source tables with Sigma Assistant was no longer available. * Editing a scheduled email or Slack export no longer displays an error that prevented the scheduled export from being edited. * Swapping sources with the `v2/workbooks/swapSources` endpoint with the `copyInputTableData` option set to `True` did not copy input table data successfully. * Text updates that might affect embed customers: * "My workspaces" is now called "Your workspaces". * The "My last activity" column in the **Recent** view is now called "Your last activity". * When saving a custom view, the option to "Set as my default view" is now called "Set as your default view". * When modifying a saved view, the option to "Remove as my default view" is now called "Remove as your default view". * When editing or customizing elements in a container, tabbed container, or repeated container, you can select the parent container from the context menu. Right-click an element, then choose **Select parent element**. * When modifying export schedules, only the owner of the schedule or an admin can make changes to the schedule. ## What's new in Sigma > Sigma release notes for Jun 12, 2026: Build and interact with Sigma agents, configure MCP tools to use with Sigma agents, and more. ## AI ### Build and interact with Sigma agents (Beta) Build agentic solutions natively in Sigma with [Sigma agents](https://help.sigmacomputing.com/docs/sigma-agents). Agents provide AI capabilities to a dashboard or application based on a predefined context of the data elements in a workbook. Instructions and data sources provide context to the agent, while actions, warehouse agents, warehouse search services, and MCP tools provide tools for an agent to take action or enrich insights. After you build an agent, you can schedule it to run automatically, or add a **Chat** element for users to interact with the agent using natural language in a conversational interface. See [Build Sigma agents](https://help.sigmacomputing.com/docs/build-agents). You can build agents to achieve specific business tasks, like analyzing pipeline funnel for sales operations, explaining financial variances across actual and plan data, forecasting different sales promotions, or summarizing the status of an incident in a debugging app. For detailed examples, see [Example use cases for Sigma agents](https://help.sigmacomputing.com/docs/example-agent-implementations). ### Configure MCP tools to use with Sigma agents (Beta) Use MCP servers for third-party services with Sigma agents by adding them to Sigma as MCP tools. For example, to provide context about documents in Microsoft SharePoint to Sigma agents, or allow agents to perform tasks in Jira, configure the relevant MCP servers in Sigma. For instructions, see [Add MCP tools to Sigma](https://help.sigmacomputing.com/docs/configure-mcp-tools). ### Use warehouse agents with Assistant and agents (Beta) If you have Snowflake Cortex Agents or Databricks Genie Spaces, you can ask questions of those agents from Sigma Assistant, or set up a Sigma agent to use one or more warehouse agents as tools. Ask questions of warehouse agents from Sigma Assistant, or set up a Sigma agent to call one or more warehouse agents as tools. Admins can turn off warehouse agents with Sigma Assistant to use only Sigma analyze mode. For more details about setup requirements, see [Use warehouse agents with Sigma](https://help.sigmacomputing.com/docs/use-warehouse-agents-sigma). ## API ### New API endpoint for updating deployment policies The following endpoint is now available to update a deployment policy in Sigma: * [Update a deployment policy](/reference/update-deployment) (`PATCH v2/deploymentPolicies/{deploymentPolicyId}`) ## Admin ### AI usage dashboard Review and monitor token consumption and more for AI-powered features in your Sigma organization. After it is configured for your organization, you can review the following for Assistant and agents: * Data source, tool calls, token usage, and model used to answer questions. * User feedback provided on agent and Assistant responses. * Conversation details For configuration instructions, see [Configure the AI usage dashboard](https://help.sigmacomputing.com/docs/configure-a-usage-dashboard-for-assistant). For details about the dashboard, see [AI usage dashboard](https://help.sigmacomputing.com/docs/ai-usage). ### License type column in the Administration > Users table In the **Administration** > **Users** page, the table now includes a dedicated *License type* column that indicates the license tier associated with each user's account type. The new column enables admins to easily review license tier allocation directly from the **Users** page. ### Support for OpenAI GPT 5.4 If your OpenAI or Azure OpenAI account supports GPT 5.4, Sigma now uses that model instead of GPT 5.1. For more information, see [Add OpenAI as an AI provider](https://help.sigmacomputing.com/docs/manage-external-ai-integrations#add-openai-as-an-ai-provider). ## Workbook elements ### Progress bars and progress rings (Beta) Build a progress bar or progress ring to display a value as a percentage or proportion of a target value. Progress bars and rings allow you to evaluate your current status in completing a goal, visualize your team's usage of a budget, and more. For more information, see [Build a progress bar](https://help.sigmacomputing.com/docs/build-a-progress-bar) and [Build a progress ring](https://help.sigmacomputing.com/docs/build-a-progress-ring). ## Workbook features ### Select Snowflake role for a connection (GA) If you have access to a Snowflake connection authenticated with OAuth, you can select which Snowflake role to use when performing tasks in Sigma. In addition to selecting a role from the data catalog, you can now also choose a role from your user profile page. For more details, see [Choose your Snowflake role for an OAuth connection](https://help.sigmacomputing.com/docs/choose-snowflake-role). ### Swap MCP tools, warehouse agents, and API connectors When tagging a workbook version, you can swap the API connectors used by **Call API** actions and the MCP tools and warehouse agents used by Sigma agents in the workbook. For more details, see [Tag a workbook, data model, or report version](https://help.sigmacomputing.com/docs/tag-a-document-version). ### Use dynamic text in email exports You can now use dynamic text when formatting the **Subject** and **Message** fields in ad hoc and scheduled email exports. See [Export to email](https://help.sigmacomputing.com/docs/export-to-email) for more information. ## Bug fixes and improvements * License tier usage counts in the **Administration** > **Users** page are now consistent with the **Usage dashboard**. * The value column position in exports now always matches how it appears in the workbook. Previously, pivot table exports with 2 or more values always placed the value column last, regardless of its position in the workbook. * You can now configure the text color of options in the navigation element. For more information, see [Use the navigation element to guide user exploration](https://help.sigmacomputing.com/docs/use-the-navigation-element-to-guide-user-exploration#style-a-navigation-element). ## What's new in Sigma > Sigma release notes for Jun 5, 2026: Create AI columns, disable/enable action sequences, and more. ## AI ### Create AI columns (Beta) You can now create AI columns to enrich your data using natural language prompts. AI columns allow you to construct dynamic prompts that reference specific table columns, and can be helpful for tasks like enriching, summarizing, and classifying data. See [Create AI columns (Beta)](https://help.sigmacomputing.com/docs/create-ai-columns) for more information. ## AI apps ### Disable/enable action sequences Disable a sequence to prevent it from running, then enable it to run again. The disabled state persists across workbook refreshes and user sessions until you manually re-enable the sequence. For more information, see [Disable and enable sequences](https://help.sigmacomputing.com/docs/create-and-manage-action-sequences#disable-or-enable-sequences). ### Pause/resume action sequences (Deprecated) The pause/resume option for action sequences has been deprecated and replaced by disable/enable controls. Because the pause state was session-based and not saved, no migration is needed. New and existing sequences automatically reflect the updated controls. See [Disable/enable action sequences](#disable-enable-action-sequences). ## Admin ### Assistant usage dashboard (Deprecated) The Assistant (Ask Sigma) usage dashboard is now deprecated and will be unavailable after September 15, 2026. Instead, configure the AI usage dashboard. See [Configure the AI usage dashboard](https://help.sigmacomputing.com/docs/configure-a-usage-dashboard-for-assistant). ### Configure mutual transport layer security (mTLS) for API connectors in Sigma You can add client and server certificates to Sigma, allowing you to configure mutual transport layer security (mTLS) for API connectors. For more information, see [Configure mutual transport layer security (mTLS) for API connectors in Sigma](https://help.sigmacomputing.com/docs/configure-mutual-transport-layer-security-for-api-connectors-in-sigma). ### Manually specify an OAuth provider when configuring organization-level OAuth You can now manually specify an OAuth provider when configuring OAuth as the single-sign-on (SSO) method for authenticating to Sigma. This enables the use of custom domain names. ## Workbook features ### Custom page sidebar (GA) You can enable custom page sidebars to appear on one or more workbook pages. Page sidebars allow you to repeat contents like filters or navigation options across multiple pages in a single configuration. For more information, see [Add custom page panels to a workbook](https://help.sigmacomputing.com/docs/add-custom-page-panels-to-a-workbook). ### Hierarchy columns (GA) Hierarchy columns are now generally available. See [Work with hierarchies](https://help.sigmacomputing.com/docs/hierarchies) and the [RaggedHierarchy](https://help.sigmacomputing.com/docs/raggedhierarchy) function reference for more information. ### Using #raw in SQL statements (Deprecated) The `#raw` directive in custom SQL is deprecated. On December 1, 2026, Sigma will no longer support the `#raw` directive. Update any custom SQL that uses `#raw` to use the `#identifier` directive before that date to avoid query errors. For more information, see [Replace the #raw directive in custom SQL](https://help.sigmacomputing.com/docs/replace-the-raw-directive-in-custom-sql). ### Cc/Bcc allowlist when run queries as recipient is enabled For security reasons, if **Run queries as recipient** is enabled, either as an [organization requirement](https://help.sigmacomputing.com/docs/restrict-export-recipients#require-run-as-recipient-for-all-email-exports) or for specific exports, admins must add recipients to an allowlist in export settings before they can be listed as Cc/Bcc recipients. Organizations with affected scheduled exports will be notified separately. See [Manage export frequency and authentication settings](https://help.sigmacomputing.com/docs/restrict-export-recipients) for more information. ## Bug fixes and improvements * Collapsed and expanded row/column groupings now export as they appear in the workbook. Previously, all row/column exported fully expanded. * Tagging a workbook version that contained custom SQL failed with an error "Cannot read properties of null (reading 'connectionId')". ## What's new in Sigma > Sigma release notes for May 29, 2026: Support for Amazon Bedrock AI provider, connect to ClickHouse, and more. ## AI ### Support for Amazon Bedrock AI provider (Beta) Amazon Bedrock is now a supported AI provider, letting you use Anthropic foundation models with Sigma AI-powered features. For setup instructions, see [Add Amazon Bedrock as an AI provider](https://help.sigmacomputing.com/docs/manage-external-ai-integrations#add-amazon-bedrock-as-an-ai-provider). ## Admin ### Connect to ClickHouse (Beta) Sigma now supports connections to ClickHouse. For more information, see [Connect to ClickHouse (Beta)](https://help.sigmacomputing.com/docs/connect-to-clickhouse). ### View materialization schedule owners in workbooks and data models You can now see who owns a materialization for an element in a materialization schedule by opening the **Materialization schedules** modal. By default, the owner is the user who added the element to the schedule, and the materialization job runs using that user's credentials for the connection. If another user updates the **Grouping** configuration, pauses, or unpauses the materialization in the schedule, ownership of the materialization transfers to that user. For more information, see [Materialization ownership](https://help.sigmacomputing.com/docs/materialization#materialization-ownership). ## Resources ### New training courses on input tables and app best practices Two new virtual training courses are now available to all Sigma users. * **Intro to Input Tables**: A hands-on lab designed for business and technical users who want to confidently explore data and create content in Sigma. [Register for the event](https://community.sigmacomputing.com/t/intro-to-input-tables/6921) to gain core skills in using input tables, forms, modals, and actions to build an interactive app. * **AI Apps Best Practices**: A webinar designed for analysts and business users with a Build license who are ready to move beyond dashboards. [Register for the event](https://community.sigmacomputing.com/t/ai-apps-best-practices/6918) to learn a framework to design applications that scale and adapt. Browse and register for all courses on the [Sigma events calendar](https://community.sigmacomputing.com/c/events/20). ## Bug fixes and improvements * When a deployed workbook was version tagged, the [Get deployed workbook in a tenant organization](/reference/get-tenant-workbook) API endpoint did not successfully return the `workbookId`. ## What's new in Sigma > Sigma release notes for May 22, 2026: Sigma Public, new API endpoint for setting organization time zone, and more. ## AI Apps ### Sigma Public [Sigma Public](https://public.sigmacomputing.com/sign-up) is now available as a free-to-use platform where you can create, share, and explore apps built in Sigma. Use sample data or upload your own datasets to build workflows in an embedded Sigma experience. You can also search apps created by other users to get inspiration for your next app in Sigma. For information about creating and managing a Sigma Public account and building public apps, see the [Sigma Public documentation](https://help.sigmacomputing.com/docs/sigma-public). ## API ### New API endpoint for setting organization time zone The following endpoint is now available to set the time zone of an organization in Sigma: * [Update organization settings](/reference/update-organization-settings) (`PATCH /v2/organizations/settings`) If you use Sigma Tenants, you can use this endpoint to set the time zone for tenant organizations. ## Data modeling ### dbt Core integration (Beta) Add metadata from the output of a dbt Core run to Sigma to visualize freshness data, monitor data quality, and display table and column descriptions configured in dbt directly in Sigma. To integrate dbt Core with your organization, use the [Add dbt metadata for a connection](/reference/post-connection-dbt-artifacts) (`POST /v2/connections/{connectionId}/dbtArtifacts`) endpoint to upload the artifacts of your dbt run to Sigma. For more details, see [Configure dbt Core integration](https://help.sigmacomputing.com/docs/manage-dbt-integration#configure-dbt-core-integration-beta). ## Workbook elements ### Hierarchy column actions and control improvements (Beta) Hierarchy column support has now been expanded: * You can use hierarchies with actions to create logic and interactivity. See [Use hierarchies with actions](https://help.sigmacomputing.com/docs/hierarchies#use-hierarchies-with-actions). * When searching for values in a hierarchy control, you can now select up to 1,000 values from the search results. * You can now see all levels of a hierarchy in your control without selecting them individually with the **Expand all levels** option. See [Work with hierarchies (Beta)](https://help.sigmacomputing.com/docs/hierarchies) and [Hierarchy](https://help.sigmacomputing.com/docs/intro-to-control-elements#hierarchy-beta) controls. ## Workbook features ### Translate Sigma UI text in workbooks You can now translate the Sigma user interface (UI) text into other languages while editing, viewing, or customizing workbooks. To apply a locale to a workbook, use the `:lng` query string parameter in the URL with the syntax `:lng=`. See [Manage workbook localization](https://help.sigmacomputing.com/docs/manage-workbook-localization) for more details. ## What's new in Sigma > Sigma release notes for May 15, 2026: Custom SQL elements included in the response for List sources endpoints, and more. ## API ### Custom SQL elements included in the response for List sources endpoints The [List data model sources](/reference/list-data-model-sources) (`GET /v2/data-models/{dataModelId}/sources`), [List workbook sources](/reference/get-workbook-sources) (`GET /v2/workbooks/{workbookId}/sources`), and [List report sources](/reference/list-report-sources) (`GET /v2/reports/{reportId}/sources`) endpoints now include custom SQL elements in the response. Custom SQL elements are listed with a type of `custom-sql` and include a `customSqlId` field. ## Admin ### Audit logs for tenant organizations in other regions (Beta) Admins in the parent organization can now access audit logs for tenant organizations hosted in other cloud regions. Browse a separate connection for each region in which you have tenant organizations with audit logging enabled. For more details, see [Review audit logs from tenant organizations](https://help.sigmacomputing.com/docs/create-and-manage-tenant-organizations#review-audit-logs-from-tenant-organizations). ### Enable multiple identity providers for your organization (GA) The ability to enable multiple identity providers (IdPs) for your organization is now generally available. See [Using multiple identity providers for your Sigma organization](https://help.sigmacomputing.com/docs/using-multiple-identity-providers-for-your-sigma-organization) for more information and enablement steps. ## Templates ### Hiding some Sigma templates To ensure that the available Sigma templates shared to every organization are relevant and high quality, some Sigma-provided templates are now hidden from the list. The following templates owned by Sigma Templates remain available: * Dynamic Profit and Loss Statement * Fivetran Usage Template * Google Analytics 4 * Loan Analysis * Snowflake Cost Monitoring * Snowflake Cost Per Query * Snowflake Performance Monitoring * Snowflake Security Monitoring * Tasty Bytes Fleet Performance Any workbooks created from the templates are unaffected. ## Workbook elements ### Add data labels to geography maps You can now configure custom data labels for geography maps. In the **Properties** tab, select **Label**, and then add the column you want to use as a data label. ## Bug fixes and improvements * "Documents" and "My documents" references are now standardized as "Your documents". * The editor panel now displays an **Invalid image URL** warning if the **Image URL** entered for a workbook page or container background image is invalid. _Showing the 20 most recent of 160 entries. Append `/llms.txt` to the changelog URL for the complete index._