-
How to split the work.
Five decisions. The fourth is the one that actually saves you.
Count the seats your plan includes.
Sort people into editors and viewers.
Buy extra seats only if needed.
Agree one editor at a time.
Check version history after handovers.
-
Working without live co-editing, in detail
Nominate a holder. One person has the site at any given time and says so in whatever chat the team already uses. Short sessions beat long ones: an hour with the file, then hand it on. The handover message costs ten seconds and is the entire mechanism.
Split by page, not by section. Two designers working on different pages of one site is a far safer arrangement than two designers agreeing to stay in different halves of the same page. Page boundaries are visible; imaginary lines inside a canvas are not.
Assume nothing is merged. How the editor settles two people saving the same page is not documented, so do not build a process that depends on a particular answer. Version history is part of the product, so there is somewhere to look after a collision, but what a restore covers and how far back it reaches are not documented either. Check both in the app before you treat version history as an undo button for a whole afternoon.
Default people to viewer. A client following progress, a founder checking copy, a developer reading the layout — none of them need to be able to change anything. An editor seat is for someone whose job is to move things.
Two details this page will not guess at: exactly what each role can and cannot do, and whether a viewer consumes one of the editor seats your plan includes. Roles and seats are separate rows on the pricing table and it does not say how they interact. The app is the authoritative source for both, so read them there before you buy a seat you may not need.