Project docs
Each project's brief, working notes and handoffs, plus the company brief — the context people and any AI agent read before work, with version history and restore.
What are project docs?
Every project has three kinds of doc, each with as many files as you need, so a newcomer — person or AI agent — knows what the project is for and where work stands without asking again.
| Kind | What goes in it |
|---|---|
| Brief | Why the project exists, what it needs, its business goals and tech structure |
| Working notes | Progress, where things stand, rules and lessons learned — updated by people or agents when they see fit, never required |
| Handoffs | Hand work over to a team or the whole project — the people it is for are notified and acknowledge it |
| Company brief | Company level: rules, how the company uses BoardMark, or what it does — shown read-only in every project |
Where do I open and write docs?
Press the gear on the board: admins get Project settings with a Docs tab; members and viewers get Project docs. Press New document or New handoff, or drop .md / .txt files, and write in the same editor as issues; an optional “What changed” note shows in History.
- Every project member edits the brief, working notes and handoffs; viewers read
- Only .md and .txt, up to 1 MB per doc, counted toward the company's storage
- If someone saved first, what you typed stays and you choose: show what differs, take theirs, or save yours as a new version
- Copy context for AI gives one markdown text with the company brief, brief, working notes and open handoffs, to paste into any AI
Can I see history and restore a doc?
Yes. Every save is a new version recording who made it (marked AI agent when an agent did). In Version history, view a version, diff it with the current one, or Restore it — restoring saves a new version and never removes history. Deleted docs can be restored from their history too (turn on Show deleted docs).
How do handoffs work?
A handoff passes work to a team or the whole project: tick the teams it is for (none ticked means everyone in the project), add related issues and save. People in those teams are notified, see a “For you” tag and a dot on the gear, and press Acknowledge — the writer is told. Status goes Open → Acknowledged → Closed (and can be reopened).
What is the company brief, and who edits it?
A company-level doc in the admin console's Company brief tab: rules, how the company uses BoardMark, or what the company does. Every project shows it read-only in its Docs, and AI agents read it before they start work. Only company admins edit it; members read it.
How do AI agents use these docs?
Over MCP (Claude, ChatGPT, Gemini, Copilot, Cursor and other clients), an agent sees which docs to read first from get_project, or reads everything at once with get_docs_context, and edits docs with the docs tools — every edit is a new version marked with its agent token.