Documents
Create durable workspace documents for team knowledge, Agent context, reports, playbooks, and MCP-accessible reference material.
Last reviewed July 13, 2026
Open Documents from the sidebar. Documents preserve context beyond one chat or report and are scoped to the active team workspace.
What Documents are for
- Analysis conclusions and decision context.
- Strategy notes, playbooks, and operating procedures.
- Client- or workspace-specific definitions.
- Reference material the Agent can use in later sessions.
- Durable output created through the app or MCP.
Use Timeline for dated decisions, experiments, and annotations. Use Memory for compact context the Agent has saved for future conversations.
Create a document
- Open Documents.
- Select New Document.
- Give it a specific title and state its intended audience.
- Add the evidence, assumptions, decision, and review date where relevant.
- Save and confirm it appears in Documents search.
Write for reuse
A useful document answers:
- What is this and who should use it?
- Which workspace, data, and time period does it cover?
- What definitions and assumptions were used?
- What decision or procedure should the reader follow?
- When should it be reviewed or retired?
Do not store API keys, access tokens, or other secrets in a document.
Use Documents with the Agent
Reference a document by name and tell the Agent how to use it:
Use our Q3 paid-media strategy as context. Compare the current allocation with its target ranges, cite the metrics you used, and do not change budgets.
Check that the Agent opened the intended document, especially when titles are similar.
Use Documents through MCP
MCP clients can expose permission-scoped tools to list, search, read, create, update, or delete documents. The connected account and OAuth/API-key access mode determine which operations appear.
Review write and delete calls before approving them, and keep tool approval enabled when an external assistant can modify workspace knowledge.