TeamFlow documentation
TeamFlow draws a delivery map from the work you were doing anyway. Nobody moves a card: every position on the board was reported by an edit, a test run, a merge or a deploy. These pages are how to set that up and what each part of it means.
Start here
New to TeamFlow? Get started takes about ten minutes and ends with your first report on the board. If your board has stopped moving, troubleshooting is in the order that finds it fastest.
Get started
Create your organisation, connect your sources, make a project, install the plugin and see your first report.
Projects
One project per session, by repository. What a project is, who owns a repository, and every state work can be in outside one.
Connect a tracker
GitHub, Linear and Jira: how each one connects, who owns which part of a ticket, and how the import fills your board.
The delivery flow
The eleven stages, the four lanes, how rework is drawn and what each arrow on the board means.
Workflows and ad hoc work
Turn an order into a plan with phases and dependencies, add a ticket you missed, and give unticketed work a key.
Other tools
Cursor, Copilot, Windsurf, Cline, Codex CLI, Gemini CLI, JetBrains, Zed, Aider and Claude Desktop.
Your team
Invite people, understand owners and members, move a machine between organisations and revoke one.
What a report carries
The exact list of what leaves your machine, and the longer list of what never can.
Demo mode
What the demo gives you, what is reset this week, and exactly what happens to your account at launch.
Troubleshooting
A ticket stopped moving, nothing is reporting, work is outside any project, or sign-in failed.
FAQ
Short answers to the questions people ask, each linking to the page that has the long one.
Looking for your editor rather than a concept? The client guides have one page per tool, with what the installer writes and the configuration to paste by hand.