Flows
Flows are lightweight boards for repeatable runs like deploys and QA passes. You define the stages once as a template, then start a flow from it whenever you have a batch of tasks to shepherd through those stages. Tasks on a flow are completely unaffected by it: their status, assignees, and everything else stay exactly as they are on the main board. A flow is a tracking overlay, not a second workflow.
Templates
A template is an ordered set of stages with a start and an end, for example Queued → Merged → Deployed for a staging deploy. New templates start with two stages, Queued and Finished, ready to be renamed. Manage them from Flows → Templates.
- System templates can be used by anyone in the workspace to start a flow. Creating and editing them requires the system flows permission.
- Personal templates are visible only to you. Anyone can create them, and they're handy for private checklists like a personal QA pass.
Each stage has a name and a colour, and you can drag to reorder them. The first stage is where newly added tasks land; the last is your "done" column. Adding a stage slots it in before the end, so your finish line stays put. A stage that still holds cards on any flow can't be removed from its template.
Deleting a template also deletes every flow started from it, so treat that button with respect.
Starting a flow
From the Flows page, hit Start Flow, pick a template, and give the run a name (one is suggested for you, like "Staging Deploy, 13th Jul 2026"). Then choose who can see it:
- Private flows are yours alone. Nobody else sees the flow or its board.
- Shared flows are visible to the whole team, and collaboratively editable: anyone who can see a shared flow can add tasks, move cards, and mark it complete.
Your active flows appear in the sidebar under Flows, and the Flows page lists everything in progress with its template, task count, visibility, and who started it.
Working the board
A flow's board works like the main task board: full task cards (labels, departments, client and project, retainer, due dates, checklists, git status, assignees), drag and drop between stages, a board/list toggle, and grouping by assignee, department, client, or project. The right-click context menu works here too, so you can change a task's real status, assignees, or labels without leaving the flow.
Adding tasks: the Add Tasks button opens a searchable, filterable picker where you can select several tasks at once. They land in the first stage. A task can be on many flows at the same time; drafts can't be added to any.
You can also add or remove tasks from a flow anywhere you see them:
- Right-click any task card or row and use Add to flow or Remove from flow. A checkmark shows which of your active flows the task is already on.
- On the task page, the ... menu has the same options, and an In flows panel shows every active flow the task is on along with its stage in each, linking straight to the board.
Completing a flow
Reaching the last stage doesn't finish anything by itself; when the run is done, hit Mark complete. Completed flows drop out of the sidebar and become read-only, so a signed-off deploy can't be quietly rearranged later. Reopen brings one back if you need to.
A few housekeeping rules:
- Edit flow (in the ... menu) renames a flow; only the person who started it can change its visibility.
- Only the person who started a flow can delete it.
- Flows never change tasks. Removing a task from a flow, completing the flow, or deleting it leaves the task exactly as it was.
Flows or automations?
Automations act on tasks for you: they change statuses, assign people, and add labels when events happen. Flows deliberately do none of that. Reach for a flow when you want to see where a batch of work sits in a process you run by hand, like "which of these ten tasks have actually been merged?", and reach for an automation when you want the system to do the moving.