Mindset docsBuildersTest and shipMove it to Production
Move it to Production
Applies the same agent files to Production once Sandbox passes, with Production's own connections, credentials and API key.
Nothing copies between environments. Your coding agent applies the same files from your repo to Production that it applied to Sandbox, so both run what you reviewed.
Ask your coding agent#
Apply agents/invoice-exceptions to Production. List the connections and credentials Production still needs before you start, stage the version, and read it back into a separate live file for Production.What happens#
Apply to Production
Your coding agent applies the files with
envSlugset to Production's slug. Only an org admin's signed-in connection can name another environment.Connect Production's systems
Connections belong to one environment. Production gets its own, pointed at your production systems, and a person enters each credential on its capture page.
Test in Production
Tested status is kept per environment, so the go-live gate applies again. Run the test parameters in Production, and approve each write with care: these reach your real systems.
Activate
A person activates the version on Versions & Availability, in Production.
What you decide#
- When Production gets a change: after its Sandbox tests pass.
- Who activates in Production.
Done when#
- Production runs the version built from the same files as Sandbox.
- Its read-back is committed, and the drift test checks it too.