Multi-org governance ensures consistency across separate Salesforce instances.
Governance components:
1. Centralised standards.
- Architectural patterns, naming conventions, security requirements — applied to ALL orgs.
- Documented; trained on; enforced.
2. Center of Excellence spanning all orgs.
- Unified team.
- Per-org liaisons.
- Cross-org architects.
3. Architecture Review Board across orgs.
- Reviews changes affecting multiple orgs or violating standards.
- Members from each major org.
4. Standardised tooling.
- Same DevOps platform (DevOps Center, Gearset, Copado) across orgs.
- Same source control structure.
- Same CI/CD patterns.
5. Shared metadata.
- Common objects (e.g., Customer, Product) consistent across orgs.
- Shared LWC component library.
- Shared Apex utility classes (deployed via Unlocked Packages).
6. Identity federation.
- Single SSO IdP.
- Same user federated across orgs.
- Permissions managed centrally.
7. Integration backbone.
- Mulesoft / iPaaS as standard.
- Cross-org integration patterns documented.
8. Reporting consolidation.
- Cross-org analytics via warehouse.
- Org-specific operational reports.
9. Vendor management.
- Single Salesforce contract covering all orgs (enterprise agreement).
- Bulk negotiation power.
10. Talent strategy.
- Architects shared across orgs.
- Per-org admins / devs.
- Cross-training to avoid silos.
Common pitfalls:
- Each org goes its own way — divergent standards.
- Inconsistent tooling — every org has different deployment.
- Cross-org issues no one owns — no governance over integration.
- Standards exist but unenforced — no consequence for divergence.
Architecture artefacts:
- Multi-org architecture diagram — orgs + integrations + identity.
- Standards documentation — what's required.
- Per-org deviations log — sometimes orgs need exceptions; document them.
Senior architect insight: multi-org governance is much harder than single-org governance. Each org has its own team, history, culture. Imposing standards is hard.
Approach: collaborate, don't dictate. Bring teams together; co-create standards; gain buy-in. Top-down mandates rarely work.
The senior framing: multi-org consistency is an ongoing effort, not a one-time setup. Quarterly governance reviews; annual deep dives. Without rigor, drift compounds.
