Shared knowledge

Shared knowledge gives everyone the same source of truth. Write your refund policy once at organization level, and every person and agent can find it, with no need to repeat it to each agent.

It differs from agent memory, which is private to one agent and built from its own conversations. Shared knowledge is deliberate: someone authored it, and it’s visible to everyone in that scope.

Where it lives

Knowledge exists at three levels:

Organization — Knowledge in the dashboard sidebar. This also works in a personal account.
Team — the Knowledge tab on a team.
Project — the Knowledge tab on a project.

Each one has two parts, Docs and Profile, plus a Review section if you can approve changes.

Docs

Docs hold your reference material. You can create documents and folders, or upload files and whole folders.

Every change is recorded as a revision, with who made it. You can compare revisions and restore an earlier one.

Profile

A profile describes the organization, team, or project itself. It has an about section, a short description, and a list of links.

Propose a change

You don’t need write access to contribute. If you can’t edit directly, the same actions become Propose, and your change waits for review instead of applying immediately. Nothing changes until it’s approved.

Anyone in your workspace can propose a change. People with write access can review:

Open Review in the relevant Knowledge section. A badge shows how many are open.
Compare the proposed change with the current content.
Approve or reject it.

An approved change is applied in the proposer’s name. Proposers can follow their own proposals, and withdraw one that’s still open.

How agents use knowledge

Agents read and contribute through their tools, within the scopes they belong to:

Search — resource_search looks across the agent’s documents by meaning.
Read — resource_read_doc and resource_get_profile fetch specific content.
Write — resource_write_doc writes a document if the agent has access.
Propose — resource_propose_change opens a proposal when it doesn’t, and resource_list_change_requests follows it up.

Agents only see knowledge from scopes they’re a member of, so add an agent to a team or project to give it that knowledge. To work with it in your own code, see the Shared knowledge API.