Apply settings with a Cloud configuration profile
Capture settings, review a canary site, then approve the remaining targets.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- An EMCP Cloud account on a paid plan (Freelancer, Agency or Enterprise) and owner access.
- Connected practice sites with Gateway access enabled and current EMCP versions.
- EMCP 3.19 or later on source and targets.
Let’s do this, step by step.
Step 01
Capture source settings
Open configuration profiles in the account, select a source and Capture current settings. Name the immutable profile.
Open configuration profiles in your account. Choose the source site and capture its settings with a clear name. This saves a fixed profile without changing other sites yet.
Step 02
Preview differences
Select one to ten targets and Preview differences. Review switches and supported settings; secrets, licences and Management access are excluded. Missing keys stay unchanged.
Choose a small target group and preview the differences. Review what each site would receive. Passwords, licences and Management access are not copied. A setting missing from the profile stays as it is on the destination.
Step 03
Prepare and apply a canary
Prepare deployment with before-images, approve one canary and apply, or Approve and queue canary. Review expires after fifteen minutes.
Prepare the deployment and choose one test site as the canary. Approve and apply there first, or use the queued canary option for background work. The review expires after fifteen minutes; prepare a fresh review if it is no longer valid.
Step 04
Verify before expansion
Inspect saved Tools/Modules settings and reconnect for a test. Approve remaining sites separately; background queue pauses at Awaiting approval.
Check the canary’s settings in WordPress and test its AI connection. Only then approve the remaining sites. A queued deployment pauses for approval; passing the canary does not approve every other site.
Step 05
Inspect results and rollback
Read per-site results. Check status after a lost response before retrying. Rollback restores recorded values with conflict checks; cancelling does not undo applied work.
Read each site’s result. If a response was lost, check status before trying again. Rollback uses the recorded earlier settings and checks for later changes. Investigate conflicts. Cancelling stops remaining work, but does not undo sites already changed.
You’re done when…
The canary is verified, remaining targets have explicit outcomes and rollback availability is understood.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.