Permission-aware enterprise search: Glean + Notion — the property that makes cross-tool search respect security boundaries

3 sources

Glean 5 (permission-aware connectors that respect source-system ACLs) and Notion Enterprise Search GA (10+ source connectors with permission propagation) both ship permission-aware search in the same week. Permission-aware search is the property that makes cross-tool enterprise search respect access control — without it, a unified search across Slack + Google Drive + Notion would expose documents that users don't have permission to see. The two are not equivalent: Glean bets on connector-level permission propagation; Notion bets on Notion-as-source plus 10+ external connectors.

Why now

Both shipped in the same week — enterprise search is now permission-aware by default, and creators building enterprise tools can rely on the property.

Why it is worth publishing

Demo potential: side-by-side of the same cross-tool search query that surfaces a permission-restricted document, measuring whether the document is exposed or hidden.

Evidence basis

Two independent vendor primary sources + The Decoder weekly roundup

“Glean 5 and Notion Enterprise Search both shipped this week — and together they make cross-tool enterprise search permission-aware by default: connector-level ACL respect, source-aware propagation.”

Angle

Frame the two as 'permission-aware enterprise search' surfaces — Glean on connector-level ACL respect, Notion on Notion-as-source + 10+ connectors — and pick based on the source-system topology.

Format

Long-form explainer

Demo idea

Record a 10-minute explainer: 3 min intro on 'permission-aware search' framing, 3 min on Glean (connector-level ACL respect + Glean Agents), 3 min on Notion Enterprise Search (10+ connectors + AI for every database), 1 min on the cross-tool comparison.

Platform notes

Specific connector list and per-tier availability beyond the captured summary are not extracted; confirm specific surface details against the underlying vendor docs before stating them on the record.

Usable claims

Glean shipped 5 — enterprise search with permission-aware connectors (respects source-system ACLs), Glean Agents for workplace automation, Glean Assistant for natural-language data interaction.
Notion shipped Enterprise Search GA (search across Notion + Slack + Google Drive + GitHub + Jira + Linear + Asana + Salesforce + Zendesk + Box) and AI-for-every-database.

Evidence pipeline

From the news

Breakdown

Glean bets on connector-level ACL respect; Notion bets on Notion-as-source + 10+ connectors. This explainer uses the source-system topology as the lens for picking a search surface, rather than treating 'permission-aware enterprise search' as a single category.

Sources

Risks

Use The Decoder and IT之家 as media-type corroboration, but read the underlying vendor docs for any specific accuracy claim or connector list before stating it on the record. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.
Vendor docs confirm feature existence but specific pricing beyond the captured summary is not in this pass. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.

Demo ideas

Side-by-side cross-tool search: same query across Glean + Notion Enterprise Search, measure permission propagation and result freshness.
Permission edge case: search for a permission-restricted document, measure whether it is exposed or hidden.
Workflow story: 'migrate cross-tool enterprise search from one surface to another', measure porting work and surface delta.