Skip to navigation

What's new in Sigma

AI

Voice input in Sigma Assistant and agents

You can now dictate prompts in Sigma Assistant on the home page, Assistant in workbooks, and chats with Sigma agents.

In the prompt bar, select Dictate, speak your request, and then select Stop dictating to review and edit the transcribed text before you send it. Voice input uses your browser’s speech recognition, so it requires a supported browser and microphone access. Sigma never receives your audio, only the prompt text you send.

For more information, see Voice input and audio processing and Chat with Sigma Assistant on the home page.

Assistant in build mode: PDF attachments

In workbooks, Sigma Assistant now supports PDF attachments in plan and build modes. Use attached PDFs, like brand guidelines, business requirements, or metric definitions, as reference material to guide builds.

For more information, see Attach a file in Use Sigma Assistant to build dashboards and apps.

API

New API endpoints for setting a badge on a document

The following endpoints are now available to add, update, or remove a badge on a workbook, report, or data model in Sigma:

Use Sigma color palettes in the code representation of a workbook

You can now use the named categorical, sequential, and diverging chart color schemes in the code representation of a workbook, such as superbloom, blues, and redblues. For more information, see Manage workbooks as code.

Use custom functions in the code representation of a workbook

You can now use custom functions defined in your organization when writing formulas in the code representation of a workbook. For more information, see Manage workbooks as code.

Use stored procedure action variables in the code representation of a workbook

You can now use the results of a stored procedure action as a variable in an action sequence when representing a workbook as code. For more information, see Manage workbooks as code.

Admin

Enable or disable file attachments in chats

Admins can now control whether users can attach images and PDFs to Sigma Assistant chats in plan and build modes.

For more information, see Manage file attachments in chats.

New model used for Gemini and Google BigQuery

If you use Google BigQuery or Gemini as your AI provider, Sigma now uses Gemini Flash 3.8 as the model.

For more details, see Supported AI models.

Allow embed users to interact with other users (GA)

User interactivity for secure embeds is now generally available. By default, embed users can’t see or interact with other users in your organization. To enable these interactions, an admin can turn on Allow embed users to interact with other users in the embed settings.

The setting doesn’t grant new permissions. Depending on their permissions and access, embed users can:

  • Comment on workbooks and @-mention 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 they don’t belong to.

All secure embed users can use existing shared views when user interactivity is on.

For setup instructions, see Manage embed user settings.

Workbook features

Burst an export to cloud storage (Beta)

You can split a cloud storage export into multiple files by using a control as the split-by value.

See Burst an export to cloud storage (Beta).

Bug fixes and improvements

  • Agents in workbooks set to run as a service account now run as the service account instead of the calling user.
  • Code blocks in Assistant responses now display with a single background and scroll horizontally. Long lines like SQL queries are no longer clipped or overlapping.
  • Redeploying a document to a tenant organization no longer fails when Sigma can’t create an input table, such as when the tenant connection doesn’t have write access configured. After you configure write access for the connection, the next deployment creates a replacement input table and uses it for later deployments.
  • Workbook warehouse override no longer fails when there is no warehouse specified on the connection.