The useful question is what each person can do with your company’s knowledge. Can they walk into a meeting prepared? Can their AI use relevant team context? And can they do both without exposing private information to colleagues? This comparison focuses on those buyer questions.
This page sets one documented approach beside ours. Every statement about Notion below is a verbatim quote from a Notion page, linked to the exact source. Vendor documentation changes; read the sources.
What Notion documents about permissions, in Notion’s words. *
Notion AI responses generated for a user
Notion’s AI security and privacy page states: “Yes, Notion AI honors existing permissions. The LLMs and AI Models used to generate AI responses for a user cannot see or use any information to which that user does not already have access.” (Notion AI security & privacy practices).
On retrieval scope, Notion’s FAQ states that what Notion AI draws on “includes pages in your Notion workspace that you have access to; your Notion AI Connectors, which connect to apps like Slack or Google Drive; and information from the web.” (What is Notion AI? FAQs). Notion’s Enterprise Search page adds: “All queries respect user permissions for each connected app (permissions sync periodically; see individual AI Connector documentation for specific details)” and “Results filtered based on user's access rights in both Notion and connected apps”. (Enterprise Search security & privacy).
Custom Agents
Notion’s Custom Agents security page opens: “Custom Agents operate with their own independent permissions separate from individual user permissions. This means anyone who can use an agent might access information through it that they couldn't access directly.” (Notion Custom Agents security features).
The two statements above sit on two different Notion pages and describe two different surfaces: AI responses generated for a user, and Custom Agents. Each is quoted here in full so the scope of each is visible, and both are linked so you can read them in place.
The controls Notion documents
Notion frames the mitigation on the same page: “Custom Agent security features help you control this access to keep your data safe.” The documented controls include an access floor, a revocation rule, and an escalation rule.
The access floor: “Each connected resource must have at least one Agent editor that has access to that resource”. The revocation rule: “If all editors lose access to a resource, the agent stops running.” Notion names the failure mode this addresses: “This prevents "orphaned" agents from continuing to access sensitive data after everyone who set them up has left the team or lost access.”
The escalation rule: “For each Custom Agent, only the person who connected an integration can add more Slack channels or increase access (for example, from `Read Only` to `Read & Reply`).” And: “Users with "Can Edit" access can remove third-party connections, but cannot expand what the connection can see.” (All four quotes: Notion Custom Agents security features).
How Notion describes delivery
Notion draws its own line between the two products: “Custom Agents are team-wide AI teammates that run automatically on schedules or triggers. Notion Agent is a personal AI assistant that works on-demand when you ask.” On how an unattended agent is set up, the same page says: “One person sets up a workflow: what data to pull, how to format it, where to post it. Set a trigger or schedule, and the agent handles it from there—24/7, whether you're online or not.” (Meet your 24/7 AI team | Notion).
Team knowledge that arrives before you ask.
WonderForce connects updates across your team’s email, meetings and documents, then prepares each person for the work ahead. A customer success colleague gets the context for a renewal. A teammate gets the updates that matter to their own work. Private information stays with the people allowed to see it.
For example, a shared account update can help everyone preparing for a customer call, while a private acquisition discussion stays private. Connecting your AI through MCP gives you the company knowledge you’re missing without opening your private information to teammates.
The difference to evaluate is practical: does the product bring useful context before a meeting, tailor it to each person, and respect private information across briefs, answers and connected agents? Compare those outcomes using your own workflows.
Learn more about proactive company knowledge and permission-aware AI retrieval.
What to compare for your team.
Every Notion cell below is a verbatim quote from a Notion page listed in the previous section
| Question | Notion, as documented | WonderForce |
|---|---|---|
| Private information | A page, and for a Custom Agent, each connected resource: “Each connected resource must have at least one Agent editor that has access to that resource”. | Private information stays with the people allowed to see it. |
| When the check is applied | For AI responses, against the asking user: the models “cannot see or use any information to which that user does not already have access.” For connected apps, “permissions sync periodically”. | Personalized briefs and answers that respect each person’s access. |
| Connected agents | For Custom Agents, the agent’s own: they “operate with their own independent permissions separate from individual user permissions”, and “anyone who can use an agent might access information through it that they couldn't access directly.” | Your AI gets relevant company context without giving colleagues access to your private information. |
What to check for yourself, with any vendor.
These questions are not about any one product. Ask them of every AI assistant you are considering, and read the vendor’s own documentation for the answers rather than a comparison page.
- Try the same question as two teammates.Use shared account updates and one private document. Check that each person gets useful context without restricted details.
- Try a brief that arrives before a meeting.Evaluate whether the preparation saves work and suggests useful questions.
- Connect an AI agent.Check whether colleagues can access private information through a shared assistant.
- Change a source permission.Ask how quickly that change affects answers, scheduled work and remembered information.
Questions people ask about Notion AI and permissions.
Does Notion AI respect user permissions?
Notion documents that Notion AI honors existing permissions for AI responses generated for a user. Notion’s AI security and privacy page states: “Yes, Notion AI honors existing permissions. The LLMs and AI Models used to generate AI responses for a user cannot see or use any information to which that user does not already have access.”
Can a Notion Custom Agent reach information a person cannot open directly?
Notion documents that a Custom Agent runs on its own permissions rather than on the permissions of the person using it. Notion’s Custom Agents security page states: “Custom Agents operate with their own independent permissions separate from individual user permissions. This means anyone who can use an agent might access information through it that they couldn't access directly.” The same page documents the controls Notion provides for that access.
What controls does Notion document for Custom Agents?
Notion documents an access floor and a revocation rule: every connected resource needs an agent editor with access to it, and the agent stops running if all its editors lose access. In Notion’s words: “Each connected resource must have at least one Agent editor that has access to that resource”, and “If all editors lose access to a resource, the agent stops running.” Notion frames these as: “Custom Agent security features help you control this access to keep your data safe.”
How does WonderForce protect private information?
WonderForce gives each person relevant company knowledge while keeping private information with the people allowed to see it. The same expectation applies to proactive briefs, answers and AI agents connected through MCP.
Is a Notion Custom Agent proactive?
Notion documents that Custom Agents run on schedules or triggers, while the personal Notion Agent works on demand. Notion’s product page states: “Custom Agents are team-wide AI teammates that run automatically on schedules or triggers. Notion Agent is a personal AI assistant that works on-demand when you ask.”
What should I check before rolling out any AI assistant company-wide?
Test whether a shared agent can reveal one colleague’s private information to another. Ask how scheduled answers, shared spaces and changes to source access affect that result.
Less catching up.
More getting ahead.
Better meeting prep. Better answers.
The context you need, before you have to ask.
* Every quotation on this page is verbatim from Notion’s own public documentation, retrieved 23 August 2026. Sources: Notion AI security & privacy practices · What is Notion AI? FAQs · Enterprise Search security & privacy · Notion Custom Agents security features · Meet your 24/7 AI team. Vendor documentation changes; the links are there so anything here can be re-checked at the source.