Comments and teamwork on a flow: pin, discuss, resolve

To discuss a flow with a colleague, pin a comment to the block you mean: press C in the editor (or Pin to a block in the Comments panel), click the block, and write. Type @ to mention someone; they get a notice and an email that opens the flow on that thread. Reply in the thread, press Resolve when it is settled, and the pin disappears from the canvas while the conversation stays in the Comments panel. If you are both in the flow at the same time, you see each other's cursors and edits as they happen.

This article is for teams where more than one person looks after an AI employee: one person builds, another reviews the AI instructions, a manager approves the timetable. It covers how comments work, a made-up review from a hotel group, live editing, version history, and the habits that keep a busy flow readable.

Comments on the canvas

• Pinned to a block. A small chip on the block's top corner shows the first author's picture and the number of messages. It moves with the block when anyone rearranges the flow.
• Pinned to a spot. Click empty canvas in pin mode for a comment about an area of the flow, such as a group of steps.
• A thread. Click a pin to open its thread beside it: the messages, a reply box with @mentions, Resolve or Open again, and delete for your own.
• The Comments panel lists every thread, Open and Resolved, each saying where it is: on a named block, on the canvas, or on a block that was later removed.

Anyone who can see the flow can comment, including people with view-only access. A reply tells the thread's author. A reply to a resolved thread opens it again.

A worked example (made up)

A hotel group in Lisbon has an employee that watches the hotels around each of its three properties and scores how guests rate them, so the revenue team can see when a neighbour slips. Joana built it; Miguel, the revenue manager, reviews it before it goes live.

Miguel opens the flow and pins three comments. On the Nearby places block: 1 km is too wide in Alfama, the streets are tiny. Can we try 500 m there? On the xMap LLM block: @Joana the instructions call a 4.2 weak. For our segment that is average. Can we move the line? On the Email block: Add Rita, she runs the Belem property.

Joana gets a notice for the mention. She changes the score instruction and replies with what she wrote; Miguel resolves it. She adds Rita to the email and resolves that herself. The distance question needs the general manager, so she mentions him in that thread and leaves it open. The Comments panel now shows one open thread, which is exactly the one thing still to decide.

Editing at the same time

When two people have the same flow open, each sees the other's cursor with their first name, and a ring in their colour on the blocks they selected. A block being dragged moves on the other screen as it moves. Typing in a block's settings appears live too, and the box shows who is typing in it and holds for a moment so you do not overwrite each other. A block someone is editing carries a tag above it, such as Joana is editing.

If both of you change the flow, each save is merged block by block. Only when you both changed the same block are you told, and your version is kept with the other's change named so you can check it.

History: what changed and who changed it

Open History in the editor to see earlier versions of the flow. Each has What changed, which draws the flow small with added blocks in green, removed ones in red and changed ones in amber, beside a plain list: Added a block, My city: Cities: London to Paris, Renamed. You can compare a version with now, which shows what restoring it would undo, or with the version before it. Restore puts that version back and keeps the current one in the list.

Who can do what

You can also share a flow with one person or a sharing group, with view or edit rights. Custom roles can remove the Deploy permission from some members.

Habits that keep a shared flow readable

• Pin to the block, not the canvas, whenever the comment is about one step. It stays attached when the flow is rearranged.
• One question per thread. A thread that mixes the timetable, the AI wording and an address is impossible to resolve.
• Mention the person who must act. A comment with no mention is easy to miss; a mention arrives in the bell and by email.
• Resolve when done. Open threads are the to-do list. Leaving settled ones open hides the real questions.
• Check What changed before restoring. A restore can undo a colleague's fix you did not know about.

Where the AI employee comes in

Comments are for the people around an employee; the employee's own reports stay in its Team inbox thread. A useful pattern is to answer a question in a comment and then tell the employee in its thread: pin should we include hostels? on the search block, agree in the thread, then write include hostels from now on to the employee in the inbox, which makes the change and shows what it changed with Undo.