A locked Notion page is not automatically hidden from AI. Notion documents page locking as protection against edits, not as a separate permission that prevents reading. If AI cannot use a page, first distinguish a reading request from an attempt to insert or rewrite content.
Do not remove collaborators, publish the page, grant everyone editing rights or unlock it for the whole team merely to troubleshoot a summary request.
1. Separate page lock, permissions and the AI feature
The official collaboration guide says that Lock page makes content read-only until an authorized editor explicitly unlocks it. A database lock instead protects views and properties while allowing data editing. Neither description establishes an AI-specific ban on reading.
Your personal Notion Agent follows your viewing and editing permissions. Asking it to explain a paragraph in chat is different from asking it to replace that paragraph on the page. A disabled editing action does not establish that the text is unavailable as a source.
For a Custom Agent, check the agent’s own access instead. These agents have independently granted resource permissions. Someone allowed to use one can potentially retrieve information the agent can access even without direct access to the original page. Do not broaden a shared agent’s resources as an informal workaround.
2. Test reading while leaving the page locked
- Open the original page using the affected person’s own account and intended workspace. Confirm that the relevant paragraph is actually visible, not just the page title or a link.
- Open personal Agent chat from that page and explicitly select the page with @. Ask a narrow question and request an answer in chat without changing the page.
- Check the selected sources. If a manually chosen model cannot use workspace content, return to Auto as described in the Agent guide.
- Compare the answer and any cited source with the original text. An answer based on general web knowledge is not proof that the page was read.
Keep the test non-sensitive where possible. A read-only instruction describes your intended task; it is not a substitute for correctly configured permissions. If the request still fails, record the exact message rather than assuming that the lock is the cause.
For a linked database, check the actual source and affected record. Linked data sources retain the original database’s access rules. Do not unlock an unrelated database template or duplicate the data into a more widely shared location.
3. Unlock only when you intend to edit
If your task really is to change the page, confirm both your editing permission and the owner’s approval to modify a finalized document. The page’s Share menu shows access levels; Can view or Can comment does not authorize rewriting content. See Notion’s permission guide.
For a user with full or edit access, current instructions allow selecting Locked in the breadcrumb and then Unlock for me. Prefer that limited scope when only you need to edit. Unlock for everyone affects other editors too and should be intentional.
Make the approved change, inspect the actual result and select Re-lock afterward when you used the personal unlock. Do not assume an AI editing request always waits for a universal final approval dialog. Ask for draft wording in chat first when you need to review it before making any page changes.
If the unlock option is unavailable, stop and ask the responsible editor. Changing sharing permissions or workspace roles is a separate authorization decision, not part of this repair.
4. Check availability and escalate the specific failure
Current Notion AI guidance describes Business and Enterprise availability, limited complimentary responses on Free and Plus, and usage allowances. Ask the owner to inspect the actual plan, usage message and relevant controls under Settings → Notion AI. Do not assume there is a separate AI seat checkbox for every member or purchase access before identifying the restriction.
If the same small reading request works on another permitted page but fails on this one, report the page-specific difference to support. Include the exact operation, error, client version, time and whether you are using personal Agent, inline editing or a Custom Agent. Keep private source text out of public reports.
Do not remove a guest or disable legitimate sharing without evidence and authorization. The useful result is either a verified read-only answer from the intended source or an approved edit with the protection restored—not simply making the lock icon disappear.
Official documentation checked October 14, 2026. The guides describe permissions and locking; they do not guarantee that every AI action works with every locked page or content type.