When Notion AI says it cannot access a page, first identify the account, page and AI feature involved. Do not grant the whole workspace editing access, invite an imagined “AI service” member, or disconnect other apps to make the error disappear.
Reading a source and editing it are different operations. A permission change should follow the task and the owner’s intent, not an assumption that more access always fixes AI.
1. Separate a reading problem from an editing problem
Open the page yourself with the same account and workspace. If the page is unavailable, ask its owner to check whether you should have access. If you can read it but cannot edit, a request to rewrite the page has a different requirement from a request to explain it in chat.
Personal Notion Agent follows your view and edit permissions. It does not require a separate invitation to every private page. See the personal Agent guide. Being private to other members does not by itself prevent your own Agent from using content you may access.
Where you only need an explanation, ask for a chat response without modifying the source. Do not request editing rights merely to read a document.
2. Identify the page in the current AI request
Open a fresh personal Agent chat from the intended page, or use an @ reference to select it. Ask a small question whose answer you can check directly. For example: “Summarize the approval steps in this page, cite the source and identify any missing details. Reply here without editing the page.”
A link or @ reference supplies context; it does not override access permissions. Do not copy restricted content into a more widely shared page as an access workaround.
For Enterprise Search, inspect the source selector and model. The selected configuration may exclude workspace material even when your page access is correct. See source selection in Enterprise Search. Distinguish “the source was not searched” from “my account cannot open it.”
3. Have the owner review only the necessary access
If permission is genuinely missing, the owner can inspect Share on the relevant source page or database. Notion’s sharing guide distinguishes viewing, commenting and editing, including inherited access and database page-level rules.
Use the narrowest authorized access for the actual task. Do not set “Can edit” for every workspace member or publish the page. Review existing group and teamspace access as well: a narrow direct grant does not cancel a broader grant elsewhere.
A filtered or supposedly private database view should not be treated as a separate AI-service permission panel. Identify the underlying source and affected records instead of looking for an undocumented “View Permissions → Add AI” switch.
4. Check whether you are using a shared Custom Agent
A Custom Agent differs from your personal Agent: it has its own assigned resources. Its owner should inspect Tools and Access and the agent’s sharing separately. Someone allowed to use an agent can receive information they cannot directly open if the agent has access. This makes an indiscriminate workspace-wide grant especially risky. See Custom Agent permissions.
For troubleshooting, record the agent’s name and the required page, then ask its owner to review that specific resource and operation. Do not broaden the agent’s permissions merely because your personal Agent can read the page.
5. Check feature availability and escalate the remaining error
Current Notion AI availability centers on Business and Enterprise plans, with limited complimentary responses on Free and Plus. Usage allowances can also pause features. Read the actual notice and the AI FAQ before attributing an error to an expired add-on or buying a different plan.
If the page is readable, correctly selected and supported by your AI feature but the error continues, collect a redacted page link, account/workspace context, time, exact request and message. Note whether another permitted page works. Give that evidence to the workspace owner or Notion support.
Leave unrelated integrations and sharing settings intact while investigating. If an unfamiliar connection raises a security concern, ask the responsible owner to investigate its purpose and authorization; disconnecting it blindly can disrupt other workflows without explaining this error.
Official documentation checked October 14, 2026.