live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
newsEnterprise AI

Sigma brings governed data analysis and workbook building into ChatGPT

The new plugin uses Sigma’s MCP server and existing account permissions, giving ChatGPT and Codex a path from natural-language questions to saved workbooks without turning the assistant into an unrestricted analytics admin.

By The News Desk· Sep 12, 2026the quick take — two AI hosts go live when you do

Sigma has released a plugin that lets ChatGPT and Codex users search, explore and query governed data in a Sigma organization, then turn the result into a saved workbook. The feature appeared in Sigma’s September 11 changelog and is distributed through the ChatGPT plugin marketplace (Sigma changelog; plugin documentation).

The useful distinction is that this is not merely a chat answer layered over warehouse data. Sigma says the assistant can locate a source, compose a query and return results in chat, but it can also create a workbook or edit an existing one. A user can ask for monthly sales by region, a top-customer chart or a year-over-year KPI; the plugin creates the artifact in Sigma and returns a link for review and continued editing (plugin documentation).

The governance boundary travels with the user

The plugin connects to the same tools exposed by Sigma’s MCP server and authenticates with OAuth. It inherits the user’s Sigma permissions: access to connections, data models and workbooks depends on the user’s account type and document-level grants. Creating or editing workbooks requires the corresponding Sigma permissions, while querying a specific document requires at least view access and querying a connection requires use access (plugin documentation).

That design matters for enterprise adoption. The assistant is not granted a parallel, universal data identity; it operates inside the access envelope already assigned to the person. Organizations using IP allowlists must also permit the AI assistant’s outbound addresses with API scope, according to Sigma’s setup requirements (plugin documentation).

It is a builder, not an administrator

Sigma documents several deliberate limits. The plugin cannot create data models, create workbooks directly in shared folders, share a workbook, delete one, restore a prior version, configure exports or edit tagged versions. New workbooks land in the user’s Your documents folder. Those constraints keep the assistant focused on analysis and draft artifact creation rather than administrative lifecycle operations (plugin documentation).

For teams that want query access without workbook creation, Sigma offers a read-only ChatGPT connection through its MCP server instead of the full plugin. The plugin itself is published as open source under Apache License 2.0 and bundles Sigma-maintained skills alongside the MCP tools (plugin documentation).

The release is another step in analytics interfaces moving outside the BI application while preserving the BI system as the governed execution and artifact layer. Here, the chat client becomes the front door, but Sigma still controls what the user can see and where the resulting analysis lives.

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.