Appearance
Environment governance best practices
Good environment governance reduces configuration conflicts, release failures, and production incidents.
WARNING
This article includes governance recommendations abstracted from Salesforce Help release practices. Internal enterprise approval processes and responsibility assignments require manual review.
Business value
Environment governance helps you manage multiple environments reliably.
It clarifies environment purpose, release order, permission scope, and rollback methods, and suits customization projects with team collaboration.
Environment planning
| Environment | Purpose |
|---|---|
| Development Sandbox | Configuration development and unit testing |
| Testing Sandbox | Functional testing and integration testing |
| Acceptance Sandbox | User acceptance and business confirmation |
| Production environment | Formal business operations |
Naming recommendations
| Scenario | Example |
|---|---|
| Development | DEV |
| Testing | QA |
| Acceptance | UAT |
| Training | TRAIN |
| Release rehearsal | STAGE |
Release governance
Before release, complete the following checks:
- The component list is confirmed.
- Dependent components are confirmed.
- The inbound change set has passed validation.
- The release window is confirmed.
- The business owner has confirmed.
- A rollback plan is ready.
Permission governance
Set sandbox permissions by purpose.
You can grant configurators higher permissions in a Development Sandbox. An Acceptance Sandbox should simulate production permissions as closely as possible. A Full Sandbox contains more real data and should strictly control access.
Data governance
Control the data scope when copying production data.
If a sandbox contains account, contact, contract, or order data, evaluate whether you need to mask the data, restrict export, or narrow access scope.