Definition
Deployment Settings is a Setup page where administrators configure which Salesforce orgs are authorized to send or receive change sets. It manages the deployment connections between production and sandbox environments, controlling the flow of metadata changes across the development lifecycle.
Real-World Example
The admin at TechNova opens Deployment Settings to authorize a deployment connection from the UAT sandbox to the production org. She checks the "Allow Inbound Changes" box for the UAT sandbox, enabling the release manager to upload validated change sets from UAT directly to production for the quarterly release.
Why Deployment Settings Matters
Deployment Settings is the Setup page where administrators authorize deployment connections between Salesforce environments. Specifically, it controls which sandboxes and production orgs can send or receive change sets by toggling the Allow Inbound Changes checkbox for each connected environment. Without this authorization, change sets cannot flow between environments, providing a security gate that prevents unauthorized modifications from reaching production.
As organizations mature their release management processes with multiple sandbox tiers (Developer, QA, UAT, Staging), Deployment Settings defines the authorized promotion path that changes must follow. A well-configured deployment pipeline might only allow Developer sandboxes to send change sets to QA, QA to UAT, and UAT to Production - never allowing developers to push directly to production. This controlled flow enforces separation of duties and ensures every change passes through proper testing and approval stages. Organizations that leave deployment connections open in all directions risk bypassing critical review steps.
How Organizations Use Deployment Settings
- TechNova — TechNova's admin configures Deployment Settings to only allow inbound changes to production from their UAT sandbox. Developer and QA sandboxes can send change sets to each other and to UAT, but cannot push directly to production, ensuring every change passes through user acceptance testing before release.
- Meridian Partners — During a security audit, Meridian's compliance team reviews Deployment Settings and discovers that three decommissioned sandboxes still have inbound deployment connections to production. The admin removes these connections, closing potential pathways for unauthorized changes.
- Cascade Financial — Cascade establishes a documented deployment pipeline: Dev sandbox sends to QA, QA sends to UAT, UAT sends to Production. The admin configures Deployment Settings to enforce this one-way flow, and the configuration becomes part of their SOX compliance documentation for change management controls.