approvals
The routine runs on its own. You decide where it asks first.
Set a rule per kind of change: run on its own, ask first, or never. Anything that asks waits in one place, with the difference.
Update policies are in beta, rolling out per account.
- Plugin update inside your windowran on its own
- Theme update inside your windowran on its own
- WordPress core update, your rule: ask firstdone
- Delete a plugin, always askswaiting for you
- Rules for this sitePer site
- Plugins and themesTuesday window, restore point firstruns on its own
- WordPress coreMajor releasesasks first
- Deleting anythingasks first
- A plugin you pinnever
Pick the days and hours updates may run.
One default, an override on any site. Pins and exclusions through API or MCP.
Automatic runs need a recent backup, and a failed check rolls back.
Deleting or restoring asks for a confirmation tied to that exact request.
Done, waiting and held, in the site's activity log.
Core has no automatic rollback. A failed check ends in a mail to you.
past tense
Mails you stop getting
Inside the window, so it ran on its own. Checked, logged.
Core asks first. You decide, in the list.
A check failed, so it rolled back and held. The log says why.