Connect your Salesforce org
Authorize SchemaForce to read your Salesforce metadata via OAuth.
Connect your Salesforce org so SchemaForce can read its metadata. You can connect from the Integrations page (Integrations → Salesforce), or during onboarding right after signup.
Read-only metadata access
SchemaForce requests an OAuth scope that lets it read your org's metadata — object, field, and relationship definitions. It never reads your records. See What SchemaForce reads below.
Connect your org
Open the Salesforce integration
Go to Integrations → Salesforce and choose Connect org.
Point SchemaForce at your org
Enter your login host — see the two ways to connect below.
Authorize via OAuth
You're sent to Salesforce to authorize. Approve the request and you're redirected back, connected. Your first sync starts automatically.
Choose how to connect
There are two ways to point SchemaForce at your org.
Enter your My Domain host, found in Salesforce under Setup → My Domain:
acme.my.salesforce.com
Sandboxes look like this:
acme--dev.sandbox.my.salesforce.com
Tokens and reconnecting
SchemaForce stores OAuth tokens encrypted and refreshes them automatically. If a connection expires or is revoked in Salesforce, you'll be prompted to reconnect — your change history is preserved across reconnects.
What SchemaForce reads
SchemaForce reads metadata only. It never reads, stores, or displays your records. It is read-only by default.
During OAuth, SchemaForce requests these scopes:
| Scope | Why it's requested |
|---|---|
api | Read your org's metadata over the API |
refresh_token, offline_access | Keep the connection alive — so SchemaForce can sync without you logging in again |
For how those tokens are stored and what we do and don't keep, see Security & privacy.
The one exception is the Push to Salesforce action:
Push to Salesforce (opt-in)
If you accept an AI-drafted field description, you can explicitly push it back to that field's metadata — one confirmation at a time. It only fills descriptions that are empty in Salesforce and never overwrites an existing one.
Pushing requires the connected Salesforce user to have the Customize Application permission.
How many orgs can I connect?
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 is a custom plan — talk to us. See Plans & billing for the full breakdown, and Managing connected orgs for working across them.
Troubleshooting
The OAuth screen won't approve
Your Salesforce user needs permission to approve connected apps and to read metadata (API Enabled, and for metadata the View Setup and Configuration permission). Ask your Salesforce admin to authorize the connection, or connect as an admin user.
I connected the wrong org
Disconnect from Integrations → Salesforce, then reconnect pointing at the correct org. History from the previous org stays with that org's record.