Governance

💬 In plain words: Single Org = One house for the whole company. Everyone shares one customer view, one set of processes, one set of data limits, and one big shared codebase. Multi-Org = Separate houses per region or business unit. This provides total freedom and isolation. However, the unified customer view splits, and you end up paying for everything (integration, DevOps , licenses) multiple times. ⚡ 1-Minute Summary Default to a single org strategy. Split only for a hard, named business driver (never just to escape your own slow internal processes). Salesforce Shield adds encrypted storage, activity history, and long-term field history. Encrypt only what is legally required. When inheriting a legacy org: look first, stabilize second, then change. Give yourself 30 days of pure observation before ripping out code. 📌 Example: Forcing Functions for Multi-Org A German subsidiary legally requires strict EU data isolation; a newly acquire...

In Salesforce, Record Types allow organizations to offer different business processes, picklist values, and page layouts to different users. While updating a Record Type's label seems like a simple UI change, altering Record Type names (or Developer Names) can ripple through your entire org architecture.