PR Custody

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

@decimal-pr-bot[bot]checks n/achecks…decimal/docs-explain-notion-page-access-is-per-integration-not-per-t-b039 → next1 files · +5 −1review: @Sushmithamalleshupdated 1mo ago

GitHub

▸Description · 1 noise

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)

▸ 1 bot/status comment hidden

@vercel[bot]1mo ago

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

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

loading diff…