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

• 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

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.

Edit and suggest changes

Open a document from its thread or the Space Library. Owners and editors can choose Editing or Suggesting from the document mode menu. Viewers see Read only.

• In Editing, changes save directly to the document.
• In Suggesting, insert or remove text to propose changes without immediately replacing the accepted document text. Suggestions save as you work; there is no separate submit step. Wait for Saving… to finish before leaving, or switch back to Editing when you are done.

To review proposed changes, open Comments, select the Suggestions tab, and choose Preview on a suggestion. Choose Accept to apply a change or Reject to dismiss it. When a group offers Accept all, use it only after reviewing the whole group. Accepting and rejecting changes require editor or owner access.

If a suggestion can no longer be applied because its target text changed, ask AI to regenerate it against the current document.

View and restore versions

1. Open the document and choose Version history.
2. Find an earlier version and choose Preview. Use Show current to return without changing the document. Where a version has a source conversation, Thread opens it.
3. To bring an earlier version back, choose Restore, review the confirmation, and confirm Restore. Restoring requires editor or owner access.

The selected version becomes current. The version it replaced remains available in history, so you can restore it later if needed.

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

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

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

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 list lists documents you can access.
• type-cli documents push --file ./doc.md --title "Title" --space engineering creates or updates a document in the target Space.
• type-cli documents sync --file ./doc.md --title "Title" --space engineering creates a document once, then keeps later local edits mapped to the same document.
• type-cli documents pull wart_123 --file ./doc.md downloads a Type document as Markdown.

See Type CLI for the full command reference.

Share documents

Open the document and choose Share to see its owner, your role, and who has access.

Role	What it allows
Viewer	Read the document and copy its link. Sharing settings are read-only.
Editor	Edit, suggest changes, accept or reject suggestions, restore versions, manage sharing, and publish.
Owner	Everything an editor can do, plus archive the document and manage its placement in Spaces.

To share with specific people or a private Space:

1. In Share, set General access to Only those invited if you want a restricted audience.
2. Select the person or private Space, choose Viewer or Editor, and select Share.
3. Review the access list. Use a recipient’s role menu to change their role or remove their direct access.

For workspace-wide access, use General access to let everyone in the workspace view, or view and edit. Removing one person’s direct grant does not remove access they still have through the workspace or a shared Space.

Public-link publishing is separate from signed-in sharing and is available when workspace policy allows it. Use narrow sharing for internal work; publish a public link only when someone outside the workspace needs to view the document.

Related

• Apps
• Automations overview
• Tool Calls, Files, and Previews