Pages & knowledge
Pages are where your team’s knowledge lives. Think of them as rich documents — like the ones you’d write in a modern doc editor — except everyone can edit them together in real time, they nest neatly into a tree, and they’re searchable the moment you hit save (which happens automatically). You’ll also see Pages called Knowledge or Docs in different corners of the product; they’re the same thing.
Where a chat is a conversation that scrolls away and a task tracks a piece of work, a page is the durable, organized memory of your team: the handbook, the project brief, the meeting notes, the spec, the runbook.
What you can do with Pages
Section titled “What you can do with Pages”- Write rich content. Headings, lists, checklists, tables, quotes, code blocks, images, and file embeds — composed with a friendly ”/” menu. See The editor.
- Edit together, live. Multiple people can type in the same page at once. You’ll see their cursors move and their changes appear instantly, with no conflicts and no “Save” button to fight over. See Real-time collaboration.
- Organize into a tree. Pages nest under other pages, so you can build a tidy hierarchy — a handbook with chapters, a project with sub-docs. See Organizing your knowledge.
- Discuss in place. Drop a comment on a passage or @mention a teammate to pull them in.
- Find anything fast. Search looks across every page by both keyword and meaning.
The pieces
Section titled “The pieces”| Term | What it means |
|---|---|
| Page | A single document with a title and rich content. |
| Block | A single piece of content inside a page — a heading, a list, a table, a code block, an image. |
| Page tree | The nested hierarchy of parent and child pages shown in the sidebar. |
| Collaborative editing | Several people editing the same page at the same time, merged automatically. |
A page can live in a project — or on its own
Section titled “A page can live in a project — or on its own”A page can belong to a project (handy for keeping a project’s brief, notes, and plans next to its tasks), or it can be a standalone, workspace-wide page in your general knowledge base. Either way, it behaves the same as a document — the only difference is who it sits with.