> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.sigmacomputing.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.sigmacomputing.com/_mcp/server.

# What's new in Sigma

> Sigma release notes for Mar 13, 2026: CSV upload using customer-owned cloud storage, validate content in a data model, and more.

## AI apps

### CSV upload using customer-owned cloud storage (GA)

CSV upload using a customer-owned cloud storage data flow is now generally available. This option offers an alternative to the default data flow through Sigma's infrastructure.

When customer-owned cloud storage is enabled, raw and processed CSV files are staged in a customer-owned bucket (instead of a Sigma-owned bucket) before loading to the data platform. Your company controls the bucket region, access, TTL, etc., helping your organization meet security and compliance requirements.

For more information, see [Configure CSV upload and storage options](https://help.sigmacomputing.com/docs/configure-csv-upload-and-storage-options) and [Configure storage integration using customer-owned bucket](https://help.sigmacomputing.com/docs/configure-storage-integration-using-customer-owned-bucket).

## Data modeling

### Validate content in a data model (GA)

When you make changes to a data model, those changes affect users of workbooks that use the data model as a source. You can now validate content to prevent breaking changes to those workbooks. Instead of manually replacing and updating deleted or changed columns, elements, metrics, and relationships in affected documents, you can validate content in the data model and prevent these errors.

For details, see [Validate content in a data model](https://help.sigmacomputing.com/docs/validate-content-data-model) and [Sync a draft with the latest published version](https://help.sigmacomputing.com/docs/edit-draft-and-publish-a-workbook#sync-a-draft-with-the-latest-published-version).

## Embeds

### New option for `workbook:mode:update` inbound JavaScript event

The `workbook:mode:update` inbound JavaScript event now supports edit as a mode.

For more details, see [Inbound event reference](https://help.sigmacomputing.com/docs/inbound-event-reference).

## Reports

### Create pixel-perfect reports (GA)

Creating reports in Sigma to generate predictable and pixel-perfect exports is now generally available. In addition to existing [formatting](https://help.sigmacomputing.com/docs/edit-report-page-setup-headers-and-footers), [pagination](https://help.sigmacomputing.com/docs/edit-report-page-order-visibility-and-numbers), [export](https://help.sigmacomputing.com/docs/share-and-export-reports), and [embedding](https://help.sigmacomputing.com/docs/create-an-embed-api-with-json-web-tokens) abilities, the following functionality is now available:

* Creating [report templates](https://help.sigmacomputing.com/docs/create-and-edit-workbook-templates) and sharing them with users both [within](https://help.sigmacomputing.com/docs/share-workbook-templates) and [outside](https://help.sigmacomputing.com/docs/share-and-accept-cross-org-workbook-templates) your organization.
* [Adding version tags](https://help.sigmacomputing.com/docs/add-version-tags-to-workbooks-and-data-models) to reports, including [input table version tagging](https://help.sigmacomputing.com/docs/use-input-tables-with-version-tagging) support.

For more information about reports, see [Reports overview](https://help.sigmacomputing.com/docs/reports-overview) and [Tutorial: Build and export a sales report](https://help.sigmacomputing.com/docs/tutorial-build-and-export-a-sales-report).

### New report API endpoints

The following endpoints are now available:

* [Create a report](/reference/create-report) (`POST /v2/reports`)
* [List reports](/reference/list-reports) (`GET /v2/reports`)
* [Get a report](/reference/get-report) (`GET /v2/reports/{reportId}`)
* [List report sources](/reference/list-report-sources) (`GET /v2/reports/{reportId}/sources`)
* [Duplicate a report](/reference/copy-report) (`POST /v2/reports/{reportId}/copy`)

Export endpoints

* [Export data from a report](/reference/export-report) (`POST /v2/reports/{reportId}/export`)
* [Export a report](/reference/send-report) (`POST /v2/reports/{reportId}/send`)

Export schedules endpoints

* [List scheduled report exports](/reference/list-report-schedules) (`GET /v2/reports/{reportId}/schedules`)
* [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}`)
* [Delete a scheduled export for a report](/reference/delete-report-schedule) (`DELETE /v2/reports/{reportId}/schedules/{scheduleId}`)

## Bug fixes

* When you create a metric that uses a column with column-level security configured, the metric no longer displays as an error to unauthorized users and is instead only visible to users with access to the column.