Collaborative authoring
Write shared primary documents for Initiatives, Features, and Issues.
Collaborative authoring gives Initiatives, Features, and Issues one shared primary document. Use it for narrative context, rationale, scope notes, acceptance framing, and working explanations that do not belong in a fixed property field.
Structured planning data stays in the existing controls: status, priority, Teams, lead, members, dates, Initiative membership, Feature relationships, Health, and linked Issues. The document is for authored text, not hidden metadata parsing.
Issue documents hold narrative only. Issue workflow, properties, relations, comments, and Activity remain in their existing structured surfaces.
What you can author
| Object | Primary document use |
|---|---|
| Initiative | Shared description, background, delivery approach, and links to related Feature work. |
| Feature | Detailed feature description, rationale, implementation context, and reviewable notes. |
| Issue | Work-item description and implementation context that do not belong in Issue properties or Activity. |
Each supported object has one primary document. Integrity creates or ensures that document when the object is created or opened. Supporting Documents are separate Resources with their own title and nested route.
How editing works
- Multiple editors can type in the same document with live cursors and presence.
- Viewers and users without edit access see read-only content.
- The editor saves durable Yjs state, Tiptap JSON, plain text, and Markdown projections.
- Search, export, and agent context use the display-safe projections instead of raw live editor state.
- Old Teamspace notes are retired as active product surfaces; new lifecycle authoring happens on the supported lifecycle objects.