Editing as a team

When two or more team members edit the same item at the same time, each one works on their own piece without stepping on the other's. The piece someone is editing is locked for the others, with the editor's face on its border; when that person saves, the new text shows up on everyone's screen, without reloading.

This adds to the faces at the top of the screen and the notices in Who is here and team editing.

#What locks in each editor

#How it works

1. You click a block (or an event section, or open the edit of a post or episode). It is yours while you are in it.
2. For the other people editing the same item, that piece gets a border with your face and "{name} is editing", and does not accept typing.
3. You type. In campaigns and e-mails, the block saves by itself about 1 second after you stop.
4. What you saved shows up in the same block, on the screen of whoever is in the item, within a few seconds. If someone has unsaved changes in another block, they stay there: only the block that changed arrives.
5. When you leave the block, it is free for anyone.

Two people in different blocks save at the same time with no conflict and no lost text.

#The Save button in campaigns and e-mails

The text of the blocks saves by itself. The Save button handles the rest: the name, the subject, the audience and adding, removing or reordering blocks. While it saves, "Saving…" shows.

#E-mail in use

A library e-mail used by automations or sends changes the next sends right away. So, on the first change of each editing session, This e-mail is in use shows ("This e-mail is used by N automations; what you change takes effect right away."). After Keep editing, it saves block by block, like the others, without asking again until you leave the editor.

#Published event

In the event, each section locks separately, and two people in different sections don't get in each other's way. In a published event, what you change still waits for Save changes, because it reaches whoever already registered. When someone else saves, the sections where you have nothing pending update by themselves.

#Post, article and episode

Here the lock covers the whole item: the first person who opens the edit edits; the others see "{name} is editing" and get the new content when that person saves. If someone saves over a version you already had open, the Someone else saved before you window opens (see Who is here and team editing).

#When the lock is released

• When you leave the block, the section or the edit.
• When you close the tab or lose the connection: within 30 seconds without a signal.
• When you go 30 seconds without touching the page: your face fades and the block is released. Whoever was idle sees "You were inactive for a while, so we released this block. Click it to continue." The text already typed is saved before the lock passes on.

#Take over editing

The owner and the admin can take a block someone else is editing:

1. Click the locked block.
2. Confirm in Take over editing? ("{name} is editing this block. Their text is saved first, then editing passes to you.") with Take over editing.
3. While the other person's text is saved, "Saving the text of whoever was editing…" shows. Then the block is yours.

Whoever lost the block sees "{name} took over this block" right away, and what they had typed is saved. Moderator and finance don't have this option: they wait for the block to be released.

#If a save fails

If a block's text cannot be saved (the connection dropped, for example), it is not lost: it is kept on this device as a draft, with the notice "We couldn't save; your text is kept here". Restore my text puts it back in the block; Discard deletes it.

The draft is yours only, for this community and this browser: someone else who signs in on the same computer doesn't see it. It is deleted when you sign out and goes away by itself after 7 days.

#Who appears

• Only whoever can edit the item enters the edit and sees the locks. Whoever only reads the page doesn't see who is editing.
• Whoever turned off Available to chat in the chat stays invisible outside the editor, but shows up with face and name to whoever edits the same item, so nobody works blind.
• A block in the chat between two people hides the name: the block says only "Being edited by another team member".
• With the community chat turned off, no face shows: the lock still applies, and the locked block says "Being edited by another team member".

#Example

Ana, Bruno and Carla review the newsletter. Ana clicks the opening block: Bruno and Carla see her face on the border and can't type there. Bruno edits the events block and Carla the footer; the three blocks save by themselves, and each one sees the others' text appear within seconds. Ana leaves for a meeting with the block open; 30 seconds later, her text is saved and the block is free. Carla changes the subject and clicks Save.

#Frequently asked questions

Do I need to turn anything on? No. It applies to the whole team (owner, admin, moderator and finance) and, on a post, also to its author; on an episode, to the show's presenters.

Can two people write in the same paragraph at the same time? Not yet: a block has one person at a time.

What about the AI assistant? A change through MCP on an item with any piece locked is refused as a whole, with the name of whoever is editing, and nothing is saved. See Common problems.

#For developers

A save that hits a lock answers 423; campaigns and e-mails gained a single-block save; the event answers 409 only for the sections that changed; posts, articles and episodes now check the version. See Responses and errors and Realtime.

#Related

• Who is here and team editing
• Roles and permissions
• E-mail campaigns
• Events