Docs / Knowledge / Knowledge documents
Knowledge documents
A knowledge document holds written information, such as a returns policy or a product guide, that Chat, workflow actions and apps use as context.
Written context
Write the information once, and everything that uses it follows the same text. A job that answers customers can follow the Returns policy, and when the policy changes, you update the document once.
A document can hold instructions, a support policy, product information, or other reference text. Chat reads the saved information when you tag the document with @ in a message. A model job, such as an LLM call or an Agent, uses the documents attached to it.
Several jobs can use the same document. Its ID stays the same across branches and saved versions, so workflow references continue to name that document after its content changes.

Versions and branches
A branch lets you work on a change while jobs keep using main. When the change is ready, you merge it into main.
- Saved version
- A snapshot of the content. Saving a changed title and saving changed content are separate operations. Earlier saved content remains available for comparison.
- Main branch
- The saved content used by workflow execution, including tests. A job reads the latest saved main version, so another branch keeps proposed changes separate.
- Merge
- Copies the source branch’s latest content into a new target version. It replaces the target content rather than combining conflicting text.
A human-created document starts with its creator as Owner. Access applies to the whole document across its branches and versions. View reads, Edit changes content, and Owner also manages access.
Documents in an action
A job loads the latest saved main version when it runs. Deleting the document or removing the job account’s access prevents that context from loading. Sharing a workflow does not by itself grant access to every document it references.