SalesForce (External Client Apps) on Multiple Organizations
April 15, 2026
This guide will walk you through the required steps to support using a Salesforce External Client App (ECA) across multiple organizations. When an ECA is created in Salesforce, it can only connect to users within the organization that created it. To allow the ECA to be used across multiple organizations, you must complete the required setup steps before it can connect to users outside the original organization.
- The first thing you need to do is create an app within Salesforce. If you have already done this proceed to step 2, otherwise check out our how to guide.
- In the SalesForce Dev Hub > Settings > Setup > Dev Hub, enable both 'Enable Unlocked Packages and Second-Generation Managed Packages' and 'Enable Dev Hub'
- Install SalesForce CLI
- Generate a SalesForce project
sf project generate --name unified-sf - Navigate into project
cd unified-sf - Login to your Source organization, this is the organization where you have created the External client app
sf org login web --alias SourceOrg - Login to your target organization, the organization you want to install the app on
sf org login web --alias TargetOrg - Retrieve the app metadata
sf project retrieve start --metadata ExternalClientApplication:Unified --target-org SourceOrg sf project retrieve start --metadata ExtlClntAppOauthSettings --target-org SourceOrg - Deploy the app onto your target organization
sf project deploy start --metadata ExternalClientApplication:Unified --target-org TargetOrg sf project deploy start --metadata ExtlClntAppOauthSettings:Unified_oauth --target-org TargetOr - A connection can now be created in the Target org