The Board
The work from idea to done on one board, with cards that say what is still missing.
On the board you follow the work in Flow from idea to done. An epic is the big goal, a feature a recognisable part of it and an item the work itself. They sit in the columns new, grooming, refined, committed, in progress, review and done. The board keeps the agreements for you: an item only moves on when it is ready, and only to done after an approval by someone who did not work on it.
In short
Drag or use the keyboard
Drag a card to the next column or move it with space, the arrows and Enter, and undo a move in one click.
Refusals that explain
When an item cannot move on yet, the card says what is missing, with a button that takes you straight there.
Epics, features and items
Epics and features follow their items by themselves, and a colleague's feedback can become an item.
Linked to versions
Put an item's code in a version's message, and a release brings the list of delivered items along.
Descriptions that read well
Headings, lists, bold, code and links are formatted properly, with a preview beside the field.
AI apps work along
An AI app views, creates, moves and links items with the rights of the person behind the access. Approving stays work for people.
What you can do
Put the work on the board
Start with an epic, hang features under it and write per item what should happen and when it is done: the acceptance criteria. A new board says in one sentence what it is for, with one button to begin.
Move cards, and see why something may not move yet
The column under the card lights up when the move is allowed. When it is not, for example because the acceptance criteria are missing or a blocker is open, the card says exactly what is missing, always fully in view. An item only moves to done after the approval of a second person.
Link items to versions and releases
Copy an item's code (#…, at the top of the inspector) into a version's message and Flow links the item to it. When you save a version you choose which items it delivers, and a release to the next environment brings the delivered items along.
Let an AI app work along
With MCP access an AI app such as Claude Code views the items on the board, creates new ones, updates them and moves them, always with your rights. Only a person can approve an item, in Flow.
The guides
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.
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.
DTAP: from development to production
Flow separates building from running. Only Development changes; Test, Acceptance and Production receive only committed versions, in a fixed order, with a trail of who promoted what and when. You add a test environment, move one version down the whole street, look at production's protection and the release history, and roll back the Flow version of an environment.
Releases: what was promoted when
Releases → History is your organisation's log: every time a version moves on to the next environment, it is there, with a note, who did it, when and what changed. You publish a version with a note and table data, and read back what was recorded. Putting a version into Production step by step is in ‘Put a version into Production’.
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.
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.
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.