Salesforce Experience Cloud licensing — member SKUs, login limits, and the audit math.

Customer, Partner, Member — and which one you actually need.

Salesforce Experience Cloud is sold under three primary external-user SKU families: Customer Community, Partner Community, and the lighter Member/Login variants. Each carries a different price, a different functional scope and a different metric. The pricing spread is wide — Partner Community Plus at the top end can be 5-7x the Member SKU at the bottom end — and the SKU chosen at acquisition often persists for years past the point where it stopped fitting the use case.

Customer Community vs Customer Community Plus

Customer Community is the entry-level external-user SKU, scoped to read-mostly access against a small set of standard objects (Cases, Knowledge Articles, basic record viewing). Customer Community Plus adds sharing rules, role hierarchy, Chatter, reports/dashboards and access to additional custom objects. Customer Community is typically appropriate for self-service support portals; Customer Community Plus is appropriate where the external user has a sustained collaborative role. The pricing differential is approximately 4-5x, and the SKU upgrade is the single most common renewal-time finding.

Partner Community and Partner Community Plus

Partner Community SKUs are designed for indirect-channel and reseller workflows — opportunity sharing, lead distribution, partner-driven case management. The Plus variant adds access to additional standard objects and custom-object record types. Partner Community is materially more expensive than Customer Community because the use case implies sustained, complex interaction with sales data. Customers using Partner Community for use cases that map functionally to Customer Community are routinely over-licensed.

Where the metric stops being per-user.

Member-Based vs Login-Based

Salesforce offers Experience Cloud licences on two distinct metrics: Member-Based (a named external user, with a fixed monthly cost per member) and Login-Based (a consumption-based metric where Salesforce sells blocks of monthly logins and a login from any external user against the org consumes a unit). Login-Based is appropriate where the external user community is large but each member logs in infrequently (annual portals, periodic survey portals, login-once-per-quarter customer portals). Member-Based is appropriate for sustained-use communities.

The 12-month rolling login measurement

Login-Based licensing measures monthly logins as a rolling 12-month maximum. Salesforce's standard audit position is that the licensed monthly login count must be at least equal to the highest single-month login count over the preceding 12 months. Customers running portals with seasonal spikes — quarterly enrollment, year-end statements, periodic compliance attestation — accrue licence requirements at the peak month, not the average. The peak shapes the licence, even when the steady state is 70% lower.

Page-view caps under External Apps

External Apps (the embedded Experience Cloud SKU for headless and API-driven external user access) is licensed by page views, with a standard cap per licence. Page views past the cap incur a per-overage charge billed quarterly. The audit risk is API-driven access from a custom front-end that accrues page-view-equivalent counts not visible to the customer's own analytics — Salesforce captures the count in API telemetry and bills against the contract cap.

What each SKU actually permits.

Salesforce's Experience Cloud SKUs each carry a defined object-access scope. The scope is documented in the SKU comparison matrix (refreshed twice a year) and enforced at the platform level: a Customer Community user cannot access Opportunities; a Customer Community Plus user can access them only with sharing rules. The functional boundary is not negotiable through configuration — attempting to grant access beyond the SKU scope returns a platform error, not a billable event.

The standard-object vs custom-object trap

The most common SKU-mismatch finding we see is custom-object access. Customer Community licences include access to a defined number of custom objects per user (typically 10); customers building portal applications with extensive custom data models routinely exceed the limit. Salesforce's audit position treats the exceedance as a SKU-upgrade requirement, not a per-object overage. The defence is to inventory custom-object access before renewal and either consolidate or budget for the SKU flip.

Knowledge access and the support-portal use case

Salesforce Knowledge access on Experience Cloud is licensed in a quirky way: read-only Knowledge access is included in Customer Community at no add-on cost; create/edit Knowledge access requires the Knowledge User permission on a paid full Salesforce licence. Customers building support portals where partner agents or community managers contribute knowledge articles often discover the requirement during deployment, not procurement.

How Salesforce calculates portal exposure.

Salesforce's commercial position on Experience Cloud sizing emphasises predictable growth: customers buy an annual member or login count, with a defined true-up at renewal. The trap is the mid-term true-up — Salesforce's standard contract reserves the right to bill mid-term overage at list price (not the original discount) for usage that exceeds the contracted block. We have seen true-ups arrive at 2-3x the original block price for the same SKU.

Overage protection — and how to negotiate it

A negotiated overage cap is the single most valuable Experience Cloud clause. Standard Salesforce contract language permits mid-term true-up at list; negotiated language caps the true-up rate at the original discount, defers true-up to the next anniversary, and allows the customer to right-size at renewal without back-bill. The cost of the clause is typically a 12-24 month minimum commitment or a small commitment uplift — and is almost always worth the price.

Six levers that move Experience Cloud pricing.

1. SKU right-sizing. The single largest savings lever — auditing actual SKU usage versus what is appropriate.
2. Member-to-Login conversion. For portals with seasonal access patterns, the Login-Based SKU is materially cheaper.
3. External Apps consolidation. Where multiple portals or headless front-ends could be consolidated under External Apps, the page-view metric can replace many Member licences.
4. Overage cap negotiation. The mid-term true-up rate is the most expensive default in the standard contract.
5. Page-view monitoring. Establishing a baseline of actual page-view consumption before the renewal removes Salesforce's information advantage.
6. Multi-org sharing. Where multiple Salesforce orgs share an external user base, consolidating onto a single Experience Cloud licence pool reduces total licence count.

Working these six levers in sequence is the core of a buyer-side Salesforce renewal negotiation — in our experience the SKU right-sizing alone typically funds the rest of the engagement.