Community licensing, now Experience Cloud, prices external users in ways that scale with growth. This guide covers the models, the cost drivers, and the buyer side moves.
Salesforce community licensing, now delivered through Experience Cloud, prices external users in ways that quietly scale with growth. This guide explains the models, the cost drivers, and the buyer side moves that keep external access affordable.
External users are people outside your company. Customers checking an order, partners submitting a deal, citizens filing a form. Salesforce licenses them differently from employees, and the model you pick decides whether external access stays cheap or quietly compounds.
The product name changed from Community Cloud to Experience Cloud. The buyer mechanics did not. The decision is still member based versus login based, audience by audience.
Community licensing covers external users through Experience Cloud sites. It is not the same as a full CRM seat and it is not free. The license type controls which objects the external user can touch and how you are billed.
Salesforce rebranded Community Cloud as Experience Cloud. The external license families carried over. Older contracts may still name community licenses, and those entitlements remain valid.
External licenses split by audience. Customer community types suit self service and support. Partner community types add sales objects like leads and opportunities for resellers and distributors. List prices sit on the Experience Cloud pricing page.
This is the decision that sets the bill. Both models grant the same access. They bill on different events, so the right answer depends entirely on how often each audience logs in.
Member based licenses bill a flat fee for every provisioned external user, whether they log in or not. The cost is predictable and rises with the size of the audience, not its activity. Salesforce sets out how external logins are counted in its login based license documentation.
Login based licenses bill on monthly logins, sold in blocks. They suit occasional users who visit a few times a month. For daily users they cost far more than a member seat. Salesforce documents both models in its Experience Cloud license documentation.
Member based versus login based, by external audience
| Audience | Login pattern | Better model | Why |
|---|---|---|---|
| Support customers | A few times a year | Login based | Low logins beat a flat per user fee |
| Active portal users | Several times a week | Member based | Logins exceed the break even fast |
| Channel partners | Daily, work driven | Member based | Predictable cost for heavy users |
| Seasonal audiences | Spiky, event driven | Mixed | Model peaks before committing |
External cost rarely jumps because of price. It jumps because the audience grows and the licensing model no longer fits. Three drivers do most of the damage.
Member based cost scales linearly with provisioned users. A portal that doubles its audience doubles that line, even if half the new users never return.
Login based blocks carry a monthly allowance. A marketing push or a renewal season can spike logins past the block and trigger overage billing that no one forecast.
The common advice is to standardize on member based licensing because it is predictable and simpler to administer. We disagree. In our engagement experience, a single model applied across every external audience overpays by a wide margin whenever a large share of users are genuinely occasional. We have seen login based licensing cut external cost by 30 to 50 percent for support audiences that visit a few times a year. The buyer side move is to segment external users by real login frequency, then license each segment on the model that fits, and revisit the split every renewal as the audience shifts.
Four moves keep external licensing affordable as the audience grows. They depend on data you already have in login analytics.
External audiences shift. A model that fit at signature can be wrong a year later. Re segment before each renewal and move users to the cheaper fit. The data lives in your own login reports.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
External licensing is not a single decision. It is a segmentation problem. Price each audience on how often it actually logs in, and the bill takes care of itself.
Yes. Salesforce rebranded Community Cloud as Experience Cloud. The external user license families carried over. Older contracts may still use community names, and those entitlements remain valid.
Member based bills a flat fee for every provisioned external user. Login based bills on monthly logins sold in blocks. Member based suits frequent users, login based suits occasional ones.
Customer Community is the lowest cost external type because it carries light object access for high volume self service. Partner Community is the most expensive because it adds sales objects.
Login based costs more when users log in frequently. Daily external users on login blocks often cost 2 to 4 times what a member based seat would. Model logins before choosing.
Yes, and you usually should. Mixing member based for heavy users with login based for occasional users almost always beats forcing one model across every external audience.
Login based blocks carry a monthly allowance. Spikes from campaigns or renewal seasons push logins past the block and trigger overage. Size blocks to the busy month to avoid this.
Segment by real login frequency, match each segment to the right model, and deactivate dormant provisioned users. Re modeling external licensing commonly cuts cost by 30 to 50 percent for occasional audiences.
No. External users are licensed separately through Experience Cloud and do not consume full CRM seats. Used well, they keep a large external audience off expensive internal licenses.
The discount audit, the uplift cap language, the reduction rights clause, the co term reset, and the population split model that beats the bundled upsell.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
External licensing is not a single decision. It is a segmentation problem. Price each audience on how often it actually logs in, and the bill takes care of itself.
