Project Documents (Wiki): Overview
Every project in AB Projects has a built-in wiki — called Documents in the app — for the knowledge that lives alongside the work: specs, runbooks, decisions, onboarding notes, and anything your team needs to keep written down. It sits in the same place as your tasks, so documentation and execution stay together.
Where it lives
- Open a project and go to its Documents area (the project wiki). Each project has its own separate Documents space.
- Pages are organized as a tree — a page can sit under a parent path, so you can build sections and sub-pages (for example
onboarding/dev-setup). - The left navigation shows the page tree with a search/filter box so you can jump to a page by title quickly.
What a document is
- Pages are written in Markdown and rendered for reading, so formatting, headings, lists, code blocks, and links all work.
- Each page has a title, an optional summary and tags, the last editor and modified time, and a version number.
- Long pages are fully supported — large content is stored efficiently behind the scenes.
Built for teams, like the rest of AB Projects
- Membership-scoped. Who can see a project's Documents follows the connected Teams channel, the same way task visibility works (see Who Can See What?). Individual pages can also restrict who may edit them.
- Accountable. Every edit is versioned and carries an edit note explaining what changed — you can view history and restore an earlier version (see Creating and Editing Documents).
- Connected to Teams. Document activity posts to the linked Teams channel and replies sync back as comments (see Document Comments & Teams Sync).
- Linked to work. Documents can be linked to tasks and vice-versa, and AI assistants can read, search, and update them via MCP (see Linking Documents to Tasks & Finding Pages).
When to use Documents vs. tasks
- Use tasks for work that has an owner, a status, and a deadline.
- Use Documents for durable knowledge that should outlive any single task — how things work, why a decision was made, reference material — and link the two together where it helps.
Documents turn a project from just a task list into a place where the team's knowledge and its work live side by side.