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.
Mode
What it does
Use it when
Named Principal
All users share one service account credential
You have service accounts, background integrations, or orgs where all users need the same access
Per User
Each user authenticates individually via OAuth
You 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.
Flow
How it works
Best 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 Flow
Each 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.