Reviewing edits
Updated 2026-08-13
Once a wiki is open to people you have not worked with, you want to see what they changed before readers do. That is the review queue. Working with other people covers roles and why any of it exists.
What lands in the queue
With review on, a save by somebody without auto-accept becomes a proposal instead of going live.
A queue that caught article text and let layout changes through would be guarding the cheap thing.
The person saving is told which will happen before they press the button, so nothing disappears silently on them.
Working the queue
- Open Manage › Moderation.
- Open a proposal and read what changed. The queue shows the change, not the page.
- Accept it, or send it back with a reason.
Say why. “Sent back” with no reason reads as “go away”, and one sentence is the whole difference between somebody trying again and not.
Keeping it from becoming a bottleneck
A queue nobody empties is worse than no queue. Contributors watch their work sit there and stop contributing. Two levers prevent it.
Accept generously
The queue is not a quality bar. Every save is a version and any of them can be put back, so accepting an imperfect edit commits you to nothing.
For who edited what outside the queue, recent changes is the other half of patrolling, and the one that matters with review off.






