Skip to content

docs: explain Notion page access is per-integration, not per-token#3385

Open
decimal-pr-bot[bot] wants to merge 1 commit into
nextfrom
decimal/docs-explain-notion-page-access-is-per-integration-not-per-t-b039
Open

docs: explain Notion page access is per-integration, not per-token#3385
decimal-pr-bot[bot] wants to merge 1 commit into
nextfrom
decimal/docs-explain-notion-page-access-is-per-integration-not-per-t-b039

Conversation

@decimal-pr-bot
Copy link
Copy Markdown
Contributor

@decimal-pr-bot decimal-pr-bot Bot commented May 8, 2026

Summary of Changes

  • Updated docs/content/toolkits/faq/notion.md "How does Notion's access model work?" section to explain that page/database access is tracked per integration (client_id), not per token or auth config
  • Added explanation that multiple auth configs sharing the same Notion integration will have cumulative shared page access
  • Added guidance to create separate Notion integrations for isolated page access

Reasoning

  • Users confused when multiple auth configs sharing the same Notion integration see shared page access across connections
  • Users need to understand that Notion's access model is per-integration (per client_id), which differs from typical OAuth scope-based providers
  • Users need clear guidance on how to achieve page-level isolation between connections (separate Notion integrations)

@decimal-pr-bot decimal-pr-bot Bot requested a review from Sushmithamallesh as a code owner May 8, 2026 19:23
@vercel
Copy link
Copy Markdown

vercel Bot commented May 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 8, 2026 7:25pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants