-
How to split the work.
Five decisions. The fourth is the one that actually saves you.
Count the seats your plan includes.
Give each person only the websites they work on.
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.
Give access only where the work is. There is no view-only role: anyone you add can edit and publish. A client following progress or a founder checking copy only needs to look, so leave them off unless they will change things, and someone who does need access should get it only on the websites they actually work on, because seats are counted per website.
Keep Admins few. Two roles: Admins manage the team and the website — inviting and removing people, transferring the website, deleting it — and Members edit and publish pages. Most people need Member. Make Admin the one or two people who would be trusted to delete the site.