Permissions

What you can do is decided by your account's permissions on this site. They typically separate the ability to create, to edit, to publish and to delete — and separating publish from edit is the important one.

It means a contributor can prepare a change and someone accountable decides when it goes live. If everyone who can edit can also publish, review is a matter of etiquette rather than something the system supports.

Ownership

Records have an owner. On a small site this is mostly informational; on a larger one it can restrict who may change what. Either way it answers "who should I ask about this page?", which is worth more than it sounds.

Two people, one page

The revision model protects you from losing work, but it does not merge concurrent edits. If two people edit the same page at once, the second save wins and the first person's version becomes a historical revision.

Nothing is destroyed — the earlier revision is still there — but the work has to be re-applied by hand. The practical fix is coordination: say what you are picking up before you start on a shared page.

Review that works

Reviewing in the admin beats reviewing a link, because the reviewer can see what changed rather than just the result. Compare the proposed revision against the active one and you get an exact diff instead of an impression.

Habits worth having

  • Publish deliberately. "Save" and "make this public" are separate decisions; treat them that way.
  • Say why in the revision, where the system allows a note. Future you will not remember.
  • When you unpublish or delete, check the menus and any pages linking to it in the same sitting.
  • Agree who owns which sections. Documentation without an owner goes stale faster than anything else on a site.