When an answer must follow an approved policy or project brief, combine Notion AI’s search-scope controls with explicit instructions and evidence checking. Selecting a source helps focus a query; it is not the same as removing access to every other document.
There is no documented workspace-wide “AI Answer Sources” allowlist matching older instructions to disable “Search entire workspace.” Use the controls below for the feature you are actually using, and apply permissions separately when confidentiality matters.
1. Select the source for this search
Open Enterprise Search in Home. In All sources, select your workspace, then hover over its name to choose the relevant page or teamspace. Exclude unwanted external sources and switch off Web search. An @ reference or Add context helps identify the intended material but is not an access-control rule. See Notion’s search-scope instructions.
Before asking the question, check the source name and open the document yourself. Similar titles, archived drafts and different client workspaces are easy to confuse. Use a source whose status and owner you can verify. You do not need to move existing pages into a new database just to run this check.
2. Ask for a bounded answer, not a plausible guess
Use a prompt that makes the evidence requirement explicit. For example, after selecting the approved travel policy:
Example prompt: “Using the selected travel policy, explain which expenses need approval before booking. Cite the section supporting each rule. If the policy does not answer a point, say ‘Not stated in the selected policy.’ Do not fill gaps from general practice. Reply here without editing any pages.”
The wording is a quality instruction, not a technical security barrier. A fluent response can still introduce an unsupported assumption. In a decision involving money, customer commitments or sensitive information, check the original text before acting.
For repeatable work, keep a short checklist naming the approved source and review date. A collection of links to approved documents is often enough; copying the documents can create competing versions. If an owner intentionally reorganizes content, review its sharing and links as a separate change.
3. Test citations and missing information
- Known-answer test: ask for one fact clearly stated in the approved document. Open the citation and compare the answer with the actual passage.
- Unknown-answer test: ask about a plausible detail that the approved document does not contain. The useful result is a clearly identified gap, not an invented policy.
- Wrong-source check: inspect every cited document. An outdated or unrelated reference means the answer needs correction even if its conclusion seems reasonable.
- Repeat after changes: record the selected source, question, expected result and review date so another person can repeat the same check.
These tests assess the answer, not the completeness of the system’s security controls. If a response uses unwanted evidence, start a fresh, explicitly scoped query and verify the selected controls. If the problem repeats, retain a redacted example for the workspace owner or Notion support; do not rely on an arbitrary cache waiting period or delete source data.
4. Enforce confidentiality with actual permissions
Use Notion sharing permissions to decide which people and groups should see a page. Review inherited teamspace access as well as direct invitations. A view filter, source reference or “use only this document” instruction should not be your confidentiality boundary.
For a workspace-wide web restriction, an owner can disable web search under Settings → Notion AI → AI Web Search. This controls web access, not a fixed approved-page list. See the Notion AI settings documentation.
Custom Agents need a separate review. They have their own resource permissions. Someone allowed to use a shared agent can obtain information they cannot open directly, or cause edits where the agent has write access. Review both Tools and Access and who can use the agent; grant only required resources and capabilities. The Custom Agent permission guide explains this distinction.
Official documentation checked October 14, 2026.