What's New

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.

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.

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.

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.

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 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 (GET v2/workbooks/:workbookId)
• Create workbooks (POST v2/workbooks)
• Update a workbook from a code representation (PUT v2/workbooks/:workbookId/contents)

For more information, see Manage workbooks as code (Beta). For examples of various features represented as code, see the 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 (GET /v2/workbookAgents)
• List agents in a workbook (GET /v2/workbooks/:workbookId/agents)
• Run a Sigma agent (POST /v2/workbooks/:workbookId/agents/:agentId)

For usage details, including an end-to-end example, see Call Sigma 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.

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 (GET /v2/organizations/settings/emailBranding)
• Update the email branding settings for an organization (PATCH /v2/organizations/settings/emailBranding)
• Reset the email branding settings for an organization (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 endpoint.
• ownerId option for the POST /v2/workbooks/{workbookId}/schedules 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 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, Manage workbooks as code (Beta), or Manage reports as code (Beta).

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.

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 turned on for your organization and for any AI features that support chat history. For more details, see 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.

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.

For details on what deprecation means, see the section on deprecated features in 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 (GET v2/reports/:reportId)
• Create report (POST v2/reports)
• Update a report from a code representation (PUT v2/reports/:reportId/contents)

For more information, see Manage reports as code (Beta). For examples of various features represented as code, see the 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.

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).

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.