GoBuildWP Cloud · Safety policies
One AI safety policy for WordPress sites, applied as far as each owner allows.
An AI safety policy for WordPress sites, written once in GoBuildWP Cloud: which safety profile AI agents work under, whether a person approves risky calls, and which abilities stay off. Each site applies it only after its owner agrees in wp-admin.
Pro, Site owner opts in from wp-admin, Never Developer Full Access
Client sites
app.gobuildwp.com- Safety profile
- Production Safe
- Approvals
- A person approves
- Switched off
- PHP, WP-CLI, file edits
- 12 sites
- 10 in sync · 2 not opted in
Representative policy. Each site applies it only as far as its owner allowed.
Why it exists
Ten sites, ten settings screens, and one of them left wide open
When every site is configured by hand, they drift. The one you forgot is the one an AI agent finds.
A safety policy is the agreement written down once: which safety profile agents work under, whether a person has to approve risky calls, and which abilities are off altogether. Push it and every assigned site that accepts it ends up with the same settings, with a status that tells you which ones did.
The site's owner keeps the last word. A policy does nothing on a site until someone with admin access there agrees to it in wp-admin, and they choose whether Cloud may only tighten their settings or also relax them. This is what lets an agency manage client sites without taking control away from the client.
How it works
Safety policies in 4 steps
The owner opts in
On each site, in wp-admin, an administrator allows Cloud to make safety settings stricter, and separately decides whether it may also loosen them.
Write the policy
Pick a safety profile, an approval mode, the abilities to switch off and the ones that always need confirming.
Assign and push
Tick the sites the policy is for and push. Each site applies it or refuses it, and says why.
Keep them in sync
Each site shows whether it matches the policy, so a site that drifted, or never opted in, stands out.
Safety
What keeps it safe, and where it stops
Built in
- Nothing changes on a site until its owner opts in, and the opt-in is cleared when the site disconnects
- Loosening is a separate permission, and a policy can never go beyond Production Safe
- A policy applies whole or not at all, so a site is never left half-configured
- Abilities the owner switched off themselves are never switched back on by Cloud
- No Cloud call or token can change the opt-in; only an administrator in wp-admin can
What it does not do
- A policy covers the safety profile, approvals and ability switches, not other GoBuildWP settings
- The next push resets the profile and approval mode on an assigned site; take a site off the policy to keep its own
- Sites need GoBuildWP Free 1.18.0 or newer to apply a policy
Free and Pro
What you get without Pro, and with it
| Feature | Cloud Free | With a GoBuildWP Pro licence |
|---|---|---|
| See how many sites let Cloud manage safety settings | Yes | Yes |
| Create, assign and push safety policies | Locked | Yes |
| Opt-in and final say on each site | Free plugin | Free plugin |
Cloud has no price of its own: it comes with every GoBuildWP Pro licence. Pro pricing
FAQ
Questions about Cloud safety policies
The rest of Cloud: updates, backups, team and clients, seo report, and how Cloud connects your sites.
Can GoBuildWP Cloud change a client's WordPress settings without asking?
No. A site applies a Cloud safety policy only after an administrator on that site has allowed it in wp-admin, and only in the direction they allowed: stricter only, or stricter and looser. They can withdraw it at any time.
Can a policy give an AI agent full access to a site?
No. Developer Full Access cannot be set from Cloud, and even a site that allows loosening stops at Production Safe.
What if a site refuses the policy?
Nothing on it changes, and the push reports the reason, for example that the owner has not opted in, or that the policy would loosen a setting when the owner only allowed tightening.
Does every site need GoBuildWP Pro?
No. Sites apply policies with the free plugin, version 1.18.0 or newer. Writing and pushing policies needs a Pro licence on the Cloud account.
Set the rules once. Let each owner agree to them.
Connect your sites, ask each owner to opt in, and push one policy instead of visiting every settings screen.