Documents
Write specs and notes in team documents, wiki collections, and entity-attached pages.
Documents
Pulse separates documents (editable content) from issues and projects. Use documents for specs, decision logs, runbooks, and team knowledge that should outlive a single task.
Document types
| Surface | Where | Typical use |
|---|---|---|
| Team documents | /teams/{team}/documents | Project doc lists owned by a team |
| Wiki collections | Team wiki tree (/teams/{team}/collections/…) | Folder-based team knowledge |
| Standalone editor | /content/{id} | Open a document directly |
| Entity-attached docs | Issue, project, initiative detail → Documents | Specs tied to delivery objects |
Terminology in settings: Documents for team doc lists; Wiki for collection trees; Knowledge for agent RAG sources (see Pulse Agent).
Create a document
From a team Documents page or an entity's document section:
- Click New document (or add from a wiki folder).
- Enter a title and start writing in the rich-text editor.
- Save — Pulse versions content as you edit.
Attach existing documents to projects, issues, or initiatives from the entity sidebar when linking is supported.
Wiki collections
Teams can organize collections — nested folders of documents shared with the team:
- Browse from the team wiki entry point
- Manage membership and shares per collection
- Pin important pages to Favorites
Shared with me
Documents another member shared appear under Shared with me in your personal sidebar (/shared-with-me).
Templates
Workspace managers configure document templates under Settings → Documents → Templates to seed new pages with standard structure.
Permissions
Creating documents requires create permission on content for the team or entity. Sharing and wiki administration may require manager roles — check team settings if actions are disabled.
Next
- Projects — attach specs to deliverables
- Pulse Agent — knowledge sources for the agent
- Templates — issue and project templates (separate from document templates)
Last updated on