Workspace Docs
Docs are collaborative pages for decisions, briefs, specs, and runbooks. They live inside spaces, support rich blocks, and can be linked from the rest of your workspace.
Overview
Use posts for progress updates and docs for information that should stay current. A doc can describe how a system works, why a decision was made, or what a project needs before the next milestone.
Project briefs
Keep goals, scope, stakeholders, and open questions next to the work.
Decision logs
Record the decision, context, owner, and follow-up tasks in one durable place.
Runbooks
Document repeatable procedures with links to posts, media, canvases, and tasks.
Review notes
Collect structured feedback before turning it into tracked tasks.
Spaces
Spaces group related pages. Keep space names broad enough to last, such as “Product,” “Engineering,” or a client name. Create narrower pages inside the space instead of making a new space for every meeting or decision.
Page visibility follows the workspace and project access model. If a page contains sensitive material, keep it in a private project or a private/shared docs space and review access before sharing links.
Write A Page
- 1.
Create a space
Use a space for a product area, team, client, or long-running project.
- 2.
Add pages
Give each page a clear title, optional icon, and visibility that matches the audience.
- 3.
Write with blocks
Use headings, lists, tables, quotes, code, dividers, and links from the editor menu.
- 4.
Invite feedback
Comment on the page or use external share links when stakeholders need read-only access.
- 5.
Publish the source of truth
Link the page from a project, task, canvas, or post so people can find it again.
Collaboration
Docs support collaborative editing, inline page activity, comments, and version history. If a page is being edited live, avoid automation that replaces the entire body at the same time. Use the Docs API for scripted updates and handle conflict responses before retrying.