Specs that stay attached to the work.
A wiki that links both ways: the doc knows which tasks implement it, and every task knows which doc explains it.
API v2 — migration brief
We are moving the public API to versioned endpoints. This covers the deprecation window, the rate-limit headers we are adding, and who owns each phase.
Old endpoints keep working until March. Every client hitting a deprecated route gets a Sunset header pointing at the replacement.
3 editorsDocs, in three moves.
- 01
Write it where the work is
Docs live in the same workspace, with the same permissions and the same search.
- 02
Embed the real tasks
Drop a task into the doc and it renders live — status, assignee and due date always current.
- 03
Keep it honest
When linked tasks change status, the doc shows it. Stale specs announce themselves.
What you get.
- Two-way links between docs and tasks
- Live task embeds that never go stale
- Real-time collaborative editing with presence
- Version history with named restore points
- Nested pages, templates and a table of contents
- Public share links with expiry
“We stopped arguing about the tool in week two. That has never happened with anything else we have rolled out.”
Marcus KellHead of Delivery, PeaklineFrequently asked
Most teams stop paying for one of them. Taskzin Docs covers specs, meeting notes, runbooks and onboarding. It is deliberately not a general-purpose database.
Yes. Docs inherit workspace permissions and can be restricted further to a project, a team or named individuals.
Put Docs to work this week.
Set up a workspace in under two minutes. Import from ClickUp, Jira, Asana or Trello in one click.
No credit card • Free 14 days • Cancel anytime