Documents
Documents are shared, editable files for reports, knowledge bases, briefs, operating procedures, and other written work your team wants to keep current.
AI can create a document inside a thread. You and your coworkers can edit it together, comment, and ask AI to keep revising it. The document becomes part of the Space Library and stays connected to the conversations behind it.
Use documents for
Section titled “Use documents for”- Team reports, account briefs, research summaries, and launch plans.
- Knowledge bases, SOPs, handbooks, and repeatable process notes.
- Working drafts that need comments, revisions, and AI help.
- Reference material AI should read before recurring work.
Work with AI
Section titled “Work with AI”Ask AI to draft, revise, summarize, or restructure a document in a thread. Your team can prompt together, comment on the document, and keep feedback in the same conversation.
Because the document lives in the Library, AI can reference it during later work when access allows it. Use a document when the output should stay useful after the original conversation ends.
Mention people and reference work
Section titled “Mention people and reference work”Type @ in a document to mention a person or to reference another document or a skill. Comments support people mentions only.
- Mentioning a person in a document or comment notifies them, subject to their notification preferences.
- Referencing a document or skill links it in place so readers and AI can jump straight to the source.
Mentions and references respect access: a person is only notified, and a referenced document only opens, when the viewer already has access to it.
Use documents in automations
Section titled “Use documents in automations”Documents pair well with scheduled and event-driven automations. For example, an automation can:
- Refresh a weekly report from connected data sources.
- Update a knowledge base when a relevant app event arrives.
- Read a team process document before responding to a support, sales, or operations workflow.
- Append findings to a shared brief after each recurring sweep.
Put stable team guidance in the document, then keep the automation instructions focused on when it should run and what result it should produce.
Import and create documents
Section titled “Import and create documents”Create documents from a thread or from the Space Library. You can also import existing .docx and .md files as editable documents, including Google Docs exports, Notion Markdown exports, and Notion ZIP exports.
With the Google or Notion integration connected, import directly from Google Docs or Notion without exporting first. See Tool Calls, Files, and Previews for the full import flow.
Use documents from the CLI
Section titled “Use documents from the CLI”Use the Type CLI when a local Markdown file should become a Type document, or when you want to pull an existing Type document down for local edits.
Common commands:
type-cli documents listlists documents you can access.type-cli documents push --file ./doc.md --title "Title" --agent @engineeringcreates or updates a document for the target agent.type-cli documents sync --file ./doc.md --title "Title" --agent @engineeringcreates a document once, then keeps later local edits mapped to the same document.type-cli documents pull wart_123 --file ./doc.mddownloads a Type document as Markdown.
See Type CLI for the full command reference.
Share documents
Section titled “Share documents”A document can be shared with specific people, private Spaces, the workspace, or through a public link when workspace policy allows it.
Use narrow sharing for internal work. Use a public link only when someone outside the workspace needs the document.