# How to manage many Salesforce orgs without losing track of any.

> Managing many Salesforce orgs with SyncOnAI 360 means connecting each production org with its sandboxes, watching health across the portfolio in the Command Center, tracking changes per org, comparing orgs, setting conventions per org, and shipping every change through the same governed proposal path.

Source: https://synconai360.com/use-cases/multi-org

## Key facts

- **6h**: Refresh of every connected org
- **1**: Portfolio view of every org
- **Per org**: Conventions and freeze windows
- **1**: Governed path for every change

## Why multi-org Salesforce estates drift apart

Each org gets its own team, its own habits and its own gaps. Nobody can see them all at once, and each one is managed from memory.

- **No portfolio view.** Each org is checked only when someone logs in.
- **Drift.** Shared configuration diverges between orgs.
- **Different rules.** Each org follows different conventions, if any.
- **Uneven governance.** Some orgs get careful releases; some get Setup.

## How do you see every Salesforce org at once?

The Command Center shows the org portfolio with health scores side by side, an action queue and an activity feed of syncs, deploys and audits across every org, refreshed about every thirty seconds.

- Health side by side
- Action queue
- Activity across orgs

## How do you compare Salesforce orgs?

Compare metadata between two orgs, or between snapshots of the same org, to see which components differ. Use it to check a sandbox against production or two business units' orgs against each other.

- Org to org
- Snapshot to snapshot
- Exactly which components differ

## How do you keep each org's conventions?

Org rules set naming conventions, forbidden patterns and the preferred automation type per org, and the AI builds inside them. Each production org's deploy policy and freeze windows apply when a proposal is promoted to it.

- Rules per org
- AI builds inside them
- Per-org policy on promotion

## How do you track change in every org?

Each org's Changes lens shows what changed and when, and whether it came through SyncOnAI 360. The audit reads each org's Setup Audit Trail and flags side-door production changes.

- Changes per org
- Route of each change
- Side-door changes flagged

## How do you govern change across all of them?

Every change in every org is a proposal with named checks and validation; production needs approval and leaves a receipt with rollback. Read-only health reports can go to each org's owners as links.

- One path for every org
- Receipts everywhere
- Reports per owner

## How do changes move between orgs?

Build and test a change in a sandbox, then promote the proposal to production, where the production org's policy, freeze windows and approval rule apply. The proposal is validated against each target org before it deploys there.

Each deploy leaves its own receipt, so the history shows where a change went and when.

- Sandbox to production by promotion
- Target org's policy applies
- Receipts per org

## How to bring many orgs under control

1. **Connect.** Add each production org with its sandboxes.
2. **Watch.** Read portfolio health in the Command Center.
3. **Compare.** Find drift between orgs.
4. **Set rules.** Conventions and policy per org.
5. **Govern.** One proposal path everywhere.

## Many orgs, by memory versus in one view

| Without | With SyncOnAI 360 |
|---|---|
| Logging into each org to check | Portfolio health in one view |
| Drift found by accident | Org comparisons |
| Conventions per person | Rules per org |
| Uneven release discipline | One governed path |

## Multi-org setup checklist

- [ ] Connect each production org with its sandboxes.
- [ ] Set org rules for each org's conventions.
- [ ] Set each production org's freeze windows and approvers.
- [ ] Scope any AI client tokens to the orgs they need.
- [ ] Review portfolio health in the Command Center weekly.
- [ ] Compare orgs that should match, and investigate drift.
- [ ] Ship every change through the same proposal path.

## Who runs many orgs

- **Enterprises.** Govern every business unit's org the same way.
- **Managed services providers.** Watch every client org from one console.
- **Consultancies.** Run a portfolio of client orgs with per-client rules.
- **Architects.** Keep shared design consistent across orgs.

## Frequently asked questions

### How many orgs can we connect?

Plans are priced by production org, each with its sandboxes. See pricing for limits.

### Do sandboxes count?

No. Sandboxes linked to a counted production org are included.

### Can we compare two production orgs?

Yes. Metadata can be compared between any two connected orgs.

### Can each org have its own rules?

Yes. Org rules and deploy policy apply per org.

### Can we see all orgs' health together?

Yes, in the Command Center.

### Does it sync orgs automatically?

Every six hours, on demand and after deploys.

### Can different teams own different orgs?

Within a workspace, members see its connected orgs. Use separate workspaces where orgs must be kept apart.

### Is this on every plan?

Yes. Every plan includes every feature.

### Can AI tools see every org?

MCP tokens are scoped to the orgs you choose, so Claude or Cursor sees only those.

### Do orgs refresh at different times?

Each refreshes every six hours and on demand, and after deploys made through SyncOnAI 360.

### Can reports cover several orgs?

Yes. Reports and the Command Center span every connected org, and each widget states how much data it covers.

### Can one change be checked against two orgs?

A proposal is validated against each org it is deployed to, when it is deployed there.

### Can one person approve changes in every org?

An admin can approve production changes in any org in the workspace, as long as they did not author the change.