Permissions
What you may do is set by permissions, given to users or to groups of users: Read, Write, Publish and Admin, set for a whole module and, where needed, for one record, which can otherwise inherit from its parent (a page's Permissions tab). Keeping Write and Publish apart is the important part. A contributor can then prepare a change, and someone accountable decides when it goes live: without publish access, "Save and activate" is not offered. See Permissions and Groups.
Two people, one record
When two people open the same record, the setting "Edit locks" decides what happens. By default the admin shows who else is editing and lets both save; a site can instead hide the edit button, or refuse a second editor altogether while the first has the record open.
When both can save, their changes are not merged: the site shows whichever version is made active last, and the other person's changes have to be combined by hand. The practical fix is to say what you are picking up before you start on a shared page.
Approval workflows
An approval workflow makes changes pass through steps, such as Draft, Review and Approved, before a version goes live, with named groups approving each move. Workflows apply to pages, blog posts, global components, FAQ pages and questions, and product and category descriptions. While one applies, "Save and activate" is not offered: a change goes live by passing the workflow's steps. Setting one up is an administrator's task; see Content workflows.
Review that works
Reviewing in the admin beats reviewing a link, because the reviewer sees what changed, not just the result: compare the proposed version with the active one in the versions list.
Habits worth having
- Publish deliberately. Saving and making something public are separate decisions.
- When you unpublish or delete something, check the menus and the pages that link to it in the same sitting.
- Agree who looks after which section. Content without an owner goes stale faster than anything else on a site.