The five steps
- Someone asks for a change. It comes for a change: in wp-admin through the assistant, from Claude or ChatGPT over MCP, or by approving an update in the dashboard.
- A restore point is saved. Before anything is written, the posts, fields, settings or files the change touches are saved.
- You see the difference. Old and new side by side. For content, in plain words and in the content itself; for an update, the code difference.
- Someone decides. A person with the approval role approves, declines or asks for another version. Declining discards the draft; the site is untouched.
- It is logged, with undo attached. Who asked, who approved, what changed, when. Undo restores the restore point in one click from the log entry.
Who can approve
Approval rights are set per WordPress role and per site. Typical setups: an agency approves everything for a client site; a client may approve text changes on their own site but not price changes or updates; a shop owner approves everything on their single site.
What a restore point contains
Exactly what the change touches, not a full backup. For twelve product prices, the twelve previous prices. For a plugin update, the plugin's previous files. Restore points are kept long enough to undo a change you only notice later; the retention period is stated in the privacy policy.
Undoing a change
Open the log entry and choose undo. The restore point is written back and the site is checked again. If other changes landed on the same content after it, the log shows them so you can decide what to keep.
What does not wait for approval
Reading. Questions about a site, checks and the security scan never change anything, so they never wait. Everything that writes to a site does.