How to edit a scenario together with colleagues?

When several integrators work on a large bot, waiting until a colleague saves and leaves is a waste of time. In Scenario Builder you can work on one process in parallel: each person in their own section, with live cursors on the canvas and a polite hand-over of a section on request.

When you need it

Two or more integrators configure different sections of the same bot.
Before changing a scenario, you want to see who is working with it right now.
A colleague holds the section you need, and you want to take it over without losing their changes.

What you need to know

Co-editing is enabled by an administrator in two steps: first "Co-editing presence: cursors and participants", then "Parallel section editing" (Menu -> Settings, section Instance settings, the Feature flags card, category Scenario Builder).
A section is the unit of parallel work: one section is edited by one person at a time, and different sections by different people.
Publishing saves only the sections you changed. Your colleagues' sections stay untouched.
If co-editing is disabled, the usual behavior applies: one user edits the scenario, saving is blocked for everyone else.

Before you start

You are logged in with integrator or administrator rights.
An administrator has enabled co-editing (see above).
The Scenario Builder editor is open with the process you need.

Step-by-step instructions

1. See who is already working with the process

At the top of the editor there is the "Active in this process" panel with colored avatars of your colleagues.
Hover over an avatar to see the colleague's email, the section they are in, and — if they have been inactive for a while — the "idle for N min" mark.
Live cursors of your colleagues are visible on the canvas, and the node a colleague is currently editing is highlighted with a colored ring.

2. Pick a free section

In the section list on the left, busy sections are marked with a lock; the tooltip shows "Editing: (colleague's email)".
Open a free section and start editing — a pencil icon appears next to it with the tooltip "You are editing this section". The section stays yours while you actively work in it; if you leave it or stay inactive for more than 3 minutes, a colleague can take it over on request (see step 3).

3. If you need a busy section

Open it — the section is view-only, with a banner above the canvas: "Section … is being edited by … — view only".
Click "Request editing". You will see "Request sent — waiting for the editor to respond".
The colleague receives an editing request with the "Hand over" and "Block" buttons and an "Auto hand-over in N s" countdown.
Three outcomes are possible:
- the colleague clicks "Hand over" or does not respond within 30 seconds — you see "The section is yours now";
- the colleague has been inactive for more than 3 minutes — the section is handed over to you immediately;
- the colleague clicks "Block" — you see "The editor declined your request"; talk to them directly.

4. Save your changes

Click "Save" or press Ctrl+S (Mac: Cmd+S) — same as in regular editing.
Only the sections you changed are published. If a colleague's section ended up among the changed ones, the system skips it and warns you: "Sections being edited by others were skipped: …".

What happens next

Your sections are saved and your colleagues immediately see the current version; their sections are untouched. When you switch to another section or close the tab, the section is automatically released for others.

How to make sure everything worked

Your section in the list has the pencil icon "You are editing this section".
After saving, a success message appeared without a warning about skipped sections.
A record with your save appeared in the version history.

Other options

If the administrator enabled only cursors and participants (without parallel section editing), the scenario is still edited by one user at a time. The blocking banner then shows an "Ask for access" button — the colleague immediately gets a message that you want to edit, no calls or messengers needed.