Selecting the Right Cross-Org Authentication Options

This diagram shows how authentication works between the subscriber org and the publisher org.

Salesforce Connect cross-org adapter architecture diagram

If you’re new to named credentials, see Get Started with Named Credentials for background on external credentials and principals.

Authentication Modes 

The biggest architectural decision that you make is whether all users share one credential or each user authenticates individually. This choice affects compliance posture, OAuth token management, and what data users can see.

ModeWhat it doesUse it when
Named PrincipalAll users share one service account credentialYou have service accounts, background integrations, or orgs where all users need the same access
Per UserEach user authenticates individually via OAuthYou have user-context-sensitive data, compliance requirements, or in regulated industries

Tiebreaker: If users in the subscriber org should only see records they’re also authorized to see in the publisher org, use Per User. If all users can see all publisher records equally, use Named Principal.

OAuth Flow Options 

After you select the authentication mode, select the OAuth flow that fits your requirements.

FlowHow it worksBest for
Client Credentials (Recommended)The subscriber org authenticates with a consumer key + secret, no user login is required. Runs as a designated service user.Background integrations, named principal authentication, or automated pipelines
Browser FlowEach principal authenticates to the publisher org interactively via a browser window.Per-user authentication or compliance scenarios that require individual user context

This guide covers how to configure both OAuth flows in the subscriber org. Most teams start with client credentials OAuth because it’s simpler, has no extra browser authentication step, and works well for named principal scenarios.