Sigma’s PowerPoint export is a governed snapshot—not a live report

Sigma has put PowerPoint export into public beta, turning a maintained Sigma report into a formatted .pptx file from the product’s export menu. The important deployment detail is not the one-click workflow; it is where governance stops. Sigma says each export queries the current state of the cloud warehouse, applies the report’s permissions and row-level security, and captures the data visible at that moment.

Generation is governed; circulation is not

That makes the generated deck a governed snapshot. It is not a live connection that keeps rechecking Sigma permissions after download. Sigma’s launch post says a changed source requires another export to put updated numbers into a new deck. For teams running weekly pipeline reviews, monthly closes or quarterly business reviews, that is a useful boundary: authorization determines what enters the file, while ordinary document controls determine where the file goes afterward.

The practical acceptance test is therefore two-part. First, export the same report as two users with different allowed rows and verify that the two decks differ as intended. Second, revoke one user’s report access and confirm that the previously downloaded .pptx is handled by the organization’s document-retention and sharing controls. The second check is an operational recommendation, not a Sigma product claim: a detached file cannot inherit a future policy change unless the surrounding document system enforces it.

The beta has report-side limits

Sigma’s export documentation says the exporter requires an account type with the Share documents permission and report ownership or Can edit access. It also caps each exported table at 10,000 rows and says a report must be published before its first export. The same page labels PowerPoint export a public beta whose interface and behavior can change quickly.

Those constraints argue against treating .pptx as a bulk-data escape hatch. They also make publication state part of the rollout checklist: test draft-versus-published behavior, the 10,000-row rendering ceiling, and the exact identity used to generate scheduled or manual decks before replacing an existing reporting pipeline.

Sigma says the beta is available to customers through their representative, with more export formats and finer layout control planned. For now, the cleanest operating model is simple: keep the Sigma report as the maintained source, regenerate the deck when data changes, and treat every downloaded file as a time-stamped distribution artifact—not as a live governed surface.