AI Colleagues build what is on the Board
Let an AI Colleague build an item that is ready: you approve the plan, follow it live and a colleague reviews the result.
An item on the board that is ready to build can be built for you by an AI Colleague. With Build this item the AI Architect gets the item as its assignment: the title, the description, the acceptance criteria and the epic and feature around it. It builds only in the development or test environment, with your rights, and never without a person watching: you approve its plan, and a colleague who did not work on it approves the result.
In short
Build this item
The AI Architect becomes the owner and moves the item to In progress in your name. If the item is not ready yet, you see which checks are missing.
The plan first
Before it changes anything, a person approves the plan or writes what should change.
Follow it live
The plan part by part, every step it takes and what it does now, right in the item.
Restore point and versions
Before its first change Flow records a restore point, and every built part becomes a version linked to the item.
Four eyes
An AI Colleague never approves its own work. Someone who did not work on it approves it or sends it back with what should change.
I'll take over
After its current step the AI Colleague stops and you become the owner.
What you can do
Give an item that is ready to an AI Colleague
Open the item on the board and choose Build this item. If something is still missing, such as acceptance criteria, Flow says which check does not pass yet, with a button that takes you straight there.
Approve the plan and follow the building
When the plan is complete, the AI Colleague waits for a person. Read what it will make and in which order, and approve it or write what should change. Under More on the board you switch that approval on or off. Then it builds part by part, and you see live where it is.
Always a way back
Before the first change there is a restore point: the version ‘Before the AI Colleague: …’. Every built part is then a version of its own, linked to the item, that you can compare and restore.
Review the result with four eyes
When building is done the item moves to Review, with a report of what was made, what Flow checked and what is still left for a person. A colleague who did not work on it approves it or sends it back, and the AI Colleague then adjusts it. In Governance whoever may approve gets the task ‘See what the AI Colleague built’ in My work.
Put an AI Colleague to work from an AI app
With MCP access (Read and Build) an AI app such as Claude Code puts an AI Colleague on an item that is ready, with your rights, and follows how far it is and what it waits for. Approving stays a person's job in Flow.
The guides
An AI Colleague builds an item
An item on the board that is ready can be built for you by an AI Colleague. With ‘Build this item’ the AI Architect gets the item as its assignment: title, description, acceptance criteria and what it belongs to. It first proposes a plan, part by part; only when a person approves the plan does it build, with your rights and only in the development environment. You follow every step in the item, every built part becomes a version linked to the item, and when it is done the item moves to Review with a report. Approving is always done by a person who did not work on it. An AI app can also put an AI Colleague to work over MCP and follow it.
The board
On the board you follow the work from idea to done. An epic is the big goal, a feature a recognisable part of it and an item the work itself: items move across the columns New, Grooming, Refined, Committed, In progress, Review and Done, and epics and features follow their items by themselves. You create them, move a card with the mouse and with the keyboard, see what Flow says when an item may not move on yet and fix it on the spot. You read an item calmly in the inspector's tabs, or large as a page. Then you choose which items a new version delivers, and see the same items again on the release in Acceptance. Finally an AI app works on the board over MCP. Finally you write an item well: a user story from a template, expanded in the large editor, with a proposal from the AI help that you accept.
Build with the AI Architect
Tell the AI Architect what you want. It works in small steps: it first reads Flow's guide and your workspace, writes down what it knows, and proposes the plan part by part: what it will make, in which order, and what stays for you. Only when you say ‘Build it’ does it build, part by part, with the same tools an AI app uses over MCP and never with more rights than you. You see every step live; a mistake Flow finds, it fixes itself; access it proposes instead of granting. Before it changes anything Flow records a version, so ‘Revert all’ puts everything back in one go.
Compare and restore versions
Version control keeps track of what changes in your environment. You commit a version, change something, see line by line what is different, and restore one item to an earlier version without touching the rest. Restoring is itself a change you commit: history is never lost.
Compare two versions
In Version control every committed version is in the history. You pick a version, see which items changed in it and compare one item line by line with the version before. That is how you find out afterwards when a rule or setting changed, and who changed it.
Getting started with Governance
Governance brings quotes, projects, people and decisions together, next to your environments in Flow. It is on or off per organisation, and only the owner switches it on in the portal; after that everyone in the organisation opens it from the menu, with their own portal account. You start on My work, with a short list ‘Getting started’: four steps that tick themselves off. The left bar grows with what you use.
Building from Claude Desktop and Claude Code (MCP)
With MCP access you let an AI app build in your development environment: modules, tables, workflows, agents. The app acts as you and can never do more than your role, it cannot delete, and keys and security policies remain in human hands. You create a key with limited rights, see what the app may and may not do, and revoke the access again.
More that is new
The new portal
Calmer: one question per screen, four fixed places in the bar, and your personal Flow always first.
Secrets and key vaults
Passwords, tokens and keys as a named secret nobody reads back, in Flow's own vault or in the one of your own cloud.
Governance
Quotes, projects, people and decisions in one place next to Flow, with gates, four eyes and a decision ledger you can have checked.
The Board
The work from idea to done on one board, with cards that say what is still missing.
Dashboards
Everything your tables and workflows produce, at a glance, built the way you will see it.
The company home
One place where everyone starts the day: in your house style, with what matters to each role.
Security you can see
Who can open what, and why, explained in plain words everywhere in Flow.
RPA screenshots
See what the browser saw, right where you follow the run.