Who can see a client's or a project's knowledge?

People whose role can read contacts and who can see that client or project. An API key needs the contacts:read scope as well.

Is anything indexed by search engines?

No. Shared knowledge is private to the workspace. It is never added to a sitemap, llms.txt or any public page.

Can an assistant change shared knowledge through MCP?

No. Through MCP an assistant can list it and search it, quoting source and date. Adding, making public, giving to an agent and taking away are a person's acts on the screen.

Are older versions kept?

Each version's date, author, passage count and fingerprint are kept. The text of older versions is not, so an answer can name the version it read but an old version cannot be restored from here.

Shared knowledge for agents, clients and projects

Keep a source once for the workspace, a client or a project, choose which agents may read it, and see which source and version an answer came from.

Steps

AI agents → Shared knowledge lists every source that belongs to the workspace, a client or a project rather than to one agent. Add pasted text, a web page or, at workspace level, your website.
Each source is Public or Internal. A public source can be given to an agent, and the agent may quote it to a visitor. An internal source is for your team's search only and no agent reads it. A client's or a project's source starts internal.
Give a public source to an agent from the source list or from the agent's Knowledge tab. Taking it away works from the agent's next answer: nothing is copied into the agent.
A source is stored once, however many agents read it. Its version goes up only when its text changes; fetching an unchanged page again is the same version. If a refresh fails, agents keep reading the last version and the screen says so.
Search the knowledge as your team, or as one agent to see exactly what that agent would be shown. Each result names its source, version and when it was last updated. The search calls no AI model.
When an agent answers, the test console and the conversation trace name the source each answer rests on, its version and update date, and how many passages were the agent's own and how many shared.

Questions

Who can see a client's or a project's knowledge?: People whose role can read contacts and who can see that client or project. An API key needs the contacts:read scope as well.
Is anything indexed by search engines?: No. Shared knowledge is private to the workspace. It is never added to a sitemap, llms.txt or any public page.
Can an assistant change shared knowledge through MCP?: No. Through MCP an assistant can list it and search it, quoting source and date. Adding, making public, giving to an agent and taking away are a person's acts on the screen.
Are older versions kept?: Each version's date, author, passage count and fingerprint are kept. The text of older versions is not, so an answer can name the version it read but an old version cannot be restored from here.

Updated 2026-10-25 · llms-full.txt