Documents
Keep collaborative narrative, supporting documents, links, and files with a Project.
Overview
Every Project has one primary collaborative document for its main narrative. Use it for background, acceptance context, implementation notes, and review framing. Keep status, priority, lead, Teams, dates, Initiative membership, dependencies, and health in their structured controls so they remain filterable and auditable.
Supporting Documents live in the Project's Resources row. Each has its own title, icon color, collaborative editor, and stable nested URL, while access continues to follow the parent Project.
Edit the primary document
Open a Project and select Overview. Click in the main document when your Project access allows editing. Changes save collaboratively, and another active editor can appear with a live cursor.
Type / to insert headings, lists, checklists, code blocks, tables, dividers, callouts, collapsible sections, or a table of contents. Use @ to reference supported people and accessible workspace objects. Restricted references resolve to display-safe text for each reader.
Create a supporting Document
- Open the Project's Overview.
- In Resources, choose New document.
- Give the Document a title and write its content on the page that opens.
Supporting Documents are useful for design notes, meeting records, test plans, and other long-form context that should not crowd the primary Project document.
Manage supporting Documents
Use a Document's menu to rename it, change its icon color, duplicate it on the current Project, move it to another Project, or remove it. Moving requires Resource-management permission on both Projects. Documents cannot move between object families and do not have independent sharing.
Accessible Documents can appear in workspace search and Favorites. Renaming a Document does not change its stable URL.
Add links and files
The same Resources menu can add an http:// or https:// link or upload a private attachment up to 100 MiB. Integrity authorizes every download against current Project access; a copied application URL is not a public file-sharing link.
Repository spec.md, plan.md, tasks.md, and build-notes.md are
synchronized lifecycle evidence. They are separate from the primary document
and supporting Documents.
Version history and comments (coming soon)
Browsing and restoring Document versions, per-passage author labels, inline comment threads, independent Document subscriptions, and document templates are not available yet. Discuss a supporting Document in the parent Project's Activity and include its link.