Managing connected orgs
Connect a production org and its sandboxes, switch between them, reconnect, and disconnect.
A SchemaForce workspace can track your production org and the sandboxes you connect alongside it. Each connected org keeps its own dictionary, snapshot, and change history, and you move between them with an org switcher.
Connecting orgs
Every tier includes one production org plus its sandboxes:
- Free — 1 production org + a sandbox
- Pro — 1 production org + its sandboxes
- Business — 1 production org + its sandboxes, plus cross-org compare
Managing multiple production orgs (an agency, or a company with several business units) is a custom plan — talk to us. See Plans & billing for the full breakdown, and Connect your Salesforce org for how connecting works.
Adding another production org?
Every plan includes one production org; sandboxes don't count against it. Connecting a second production org is a custom plan — Connect another org points you to get in touch.
What you can do
The org switcher sets which connected org you're viewing. Pages render that org's dictionary, changes, and impact analysis.
Add a sandbox to test against. Each connected org gets its own baseline snapshot and history.
A one-click re-authorization against the org's own My Domain — no form to fill in. Use it if a connection needs to re-auth.
Stop tracking an org, with a choice about whether to keep or erase its stored data.
Switching the active org
The org switcher controls which connected org you're looking at. Whatever you select becomes the active org, and the dictionary, change timeline, and impact views all render for that org until you switch again.
Reconnecting
Reconnecting is a one-click re-authorization against the org's own My Domain — there's no host to re-enter. Use it whenever a connection needs to re-authenticate, for example after a token is revoked in Salesforce. Reconnecting an already-connected org doesn't add a new connection, and its history is preserved.
Disconnecting
Disconnecting offers two modes. Both revoke SchemaForce's access token at Salesforce — the difference is what happens to the data SchemaForce already stored for that org.
Choose carefully — Erase everything can't be undone
Keep history marks the org as disconnected but keeps its dictionary and change history, so you can reconnect later and pick up where you left off.
Erase everything permanently deletes all of that org's data — its dictionary, snapshot, and change history. This can't be reversed.
Both modes revoke SchemaForce's access token at Salesforce.