Salesforce Multi-Environment and Org Topology

Overview

Map each environment to a purpose, fidelity level, data policy, authorization boundary, lifecycle, and promotion contract.

Prerequisites

• Business release model, Salesforce DX project, package strategy, org inventory, and environment owners
• Dev Hub, scratch-org, sandbox, staging, and production capabilities actually available to the customer
• Data seeding, masking, refresh, drift, namespace, dependency, promotion, rollback, and support requirements

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

Scratch orgs are disposable source-driven environments configured from project definitions; sandboxes provide different production fidelity and lifecycle characteristics. Available types, features, refreshes, data, and limits depend on the customer org.