Experience Cloud external users. Pay for the logins, not the list.

Experience Cloud external licensing turns on one ratio: monthly active rate. Below roughly 30 percent, login pools beat member pricing by 25 to 75 percent. Most portals sit below it.

How does Salesforce actually license external users?

Experience Cloud licenses external users two ways: per member per month, or per login with a monthly login pool. The right choice is arithmetic on your usage pattern, and Salesforce's default proposal is whichever yields more revenue on your profile.

The license types are published on the Experience Cloud pricing page, and the usage rules live in the Salesforce master subscription agreement and order form documentation. The order form, not the pitch deck, defines what an external user may touch.

Member versus login: the break even math

Login based pricing wins when average monthly logins per registered user fall below roughly 30 percent. Customer portals and dealer networks almost always sit below that line; daily use partner communities sit above it.

Which license type maps to which population?

• Customer Community: high volume, low complexity access; cases, knowledge, simple records.
• Customer Community Plus: adds roles, sharing, and reports; the step most often oversold.
• Partner Community: adds opportunity and lead access; channel sales only.
• External Apps: custom object heavy patterns at lower entry cost in some profiles, priced per Salesforce platform pricing.

What does external user licensing really cost at scale?

List prices mislead at portal scale because the unit economics invert: a 50,000 member portal at member pricing costs multiples of the same portal on a login pool sized to real traffic. Model both before any conversation with the account team.

The object permission trap

License type is gated by object access, documented in Salesforce's external license type documentation, so one requirement, like partners updating opportunities, can force the whole community up a tier. Audit which roles genuinely need the gating object before accepting an edition wide upgrade; in most estates it is under 10 percent of the population.

Where the common advice on Experience Cloud licensing is wrong

The standard advice is to size external licensing on registered community membership. We disagree. In roughly 20 of the 25 to 35 estates Fredrik Filipsson reviewed in 2024 to 2025, registered membership overstated licensable need by 3x or more, because most registered users log in rarely or never. The buyer side move is to pull twelve months of login telemetry, license the active pattern on a login pool, and split the small high access population onto the higher type. Salesforce sizes proposals on membership because membership only grows. Pay for behavior, not for the database row.

Salesforce licenses the community you registered. You should pay for the community that shows up.

How should a CIO negotiate the external user line?

The external line negotiates separately from internal seats, with its own discount curve and its own levers: basis choice, tier splitting, pool sizing, and growth protection. Bundling it into the org wide renewal hides all four.

1. Choose the basis first: member or login per community, from telemetry, before pricing talk.
2. Split tiers: license the 5 to 10 percent who need Plus or Partner; keep the rest on the base type.
3. Size login pools to P75 traffic: overage rates are negotiable; oversized pools are sunk cost.
4. Cap growth pricing: lock unit rates on incremental volume so portal success does not become a penalty.
5. Reprice at renewal: external usage shifts; the basis that fit two years ago may not fit now.

What evidence wins the conversation?

Login distribution by month, active rate by community, and object access by role. With those three datasets the negotiation is arithmetic; without them it is the account team's forecast against your hope.

What to do next

1. Inventory every Experience Cloud community, its license type, and its registered population.
2. Pull twelve months of login telemetry per community.
3. Compute member versus login break even for each population.
4. Map object permissions by role to find tier inflation.
5. Move internal license type external users onto proper external types.
6. Reprice the external line as a separate negotiation track.
7. Set a telemetry review six months before every renewal.

The Salesforce license optimization service covers the internal seat side, and the Salesforce knowledge hub holds the full negotiation library. The Renewal Program runs the twelve month sequence around your next Salesforce date.

Frequently asked questions

What is the difference between member based and login based Experience Cloud licensing?

Member based licensing charges per registered external user per month regardless of activity. Login based licensing charges for a monthly pool of logins. Below roughly 30 percent monthly active rate, logins are cheaper, often by 25 to 75 percent.

Which Experience Cloud license types exist for external users?

Customer Community for high volume basic access, Customer Community Plus for roles and reports, Partner Community for opportunity and lead access, and External Apps for custom object heavy patterns. Each step up roughly doubles unit cost.

Can external users be licensed on internal Salesforce licenses?

They can, but it is almost always wrong commercially. Partner users on full Sales Cloud seats cost 3x to 5x the appropriate Partner Community rate in the estates we reviewed. Move them to external types at the next renewal.

How should login pools be sized?

Size pools to around the 75th percentile of monthly login traffic and negotiate the overage rate, rather than buying peak capacity year round. Oversized pools are unrecoverable spend; negotiated overage is insurance.

When does Partner Community licensing become necessary?

Only when external users need opportunity, lead, or campaign access for channel selling. If partners only manage cases and shared records, Customer Community Plus covers them at roughly half the cost.