Salesforce Experience Cloud (formerly Community Cloud) enables organisations to build branded portals and communities for customers, partners, and external stakeholders. Community licensing governs how these external users access Salesforce data and functionality. It works fundamentally differently from standard internal user licences. The licence type, the pricing model (member-based vs login-based), and the tier assignment collectively determine whether your community costs are optimised or whether you are overspending by 40 to 60%.
Salesforce Experience Cloud enables organisations to create portals and communities for external users: customers, partners, and employees. Community licensing governs how these external users access Salesforce data and functionality.
Unlike standard internal user licences (Sales Cloud, Service Cloud), community licences come in specialised types with unique cost structures and usage limits. For ITAM teams at global enterprises, mastering these licence models is crucial for managing spend and avoiding compliance issues.
Community licences enable secure, branded engagement with external stakeholders at scale. But they require careful planning to implement cost-effectively. The primary cost driver is the number of external users or login volume. As communities scale to thousands or millions of users, costs can grow quickly. The wrong pricing model or tier assignment can mean 40 to 60% overspend that compounds every year through built-in uplifts.
Self-service portals for customers. Access to Cases, Knowledge, and custom objects. No access to Opportunities or Leads. No role-based sharing model (organisation-wide defaults only). Scales to millions of users. The lowest-cost community licence, designed for high-volume customer self-service scenarios where users need to submit cases, search knowledge articles, and interact with custom objects.
All standard objects including Opportunities and Leads. Role-based sharing and visibility. Reports and dashboards. Designed for B2B customer communities where more refined data access is required. Higher per-user cost than base tier (roughly 3x). Only choose Plus when you genuinely need role-based sharing or access to standard objects beyond Cases and Knowledge.
Leads, Opportunities, Campaigns access. Full role hierarchy and sharing. Partner Relationship Management (PRM) features. The most feature-rich community licence, designed for resellers, distributors, and channel partners who need to manage deals and collaborate on pipeline. 5x the cost of base Customer Community.
External Apps licences support high-volume external applications with extensive custom development, extra API calls, and storage. Scales to 100,000+ users with premium pricing and volume economics. Employee Community (Employee Apps) licences provide limited Salesforce access (Accounts, Contacts, basic custom objects) for internal employees or contractors who do not need full CRM functionality. Ideal for HR portals, internal knowledge bases, or helpdesks at significantly less than standard Sales/Service Cloud licences.
| Licence Type | Key Use Case | Objects Accessible | Sharing Model | Approx. List Price |
|---|---|---|---|---|
| Customer Community | Self-service portals, knowledge base | Cases, Knowledge, custom objects | Organisation-wide defaults only | ~$2/login or ~$5/member/mo |
| Customer Community Plus | B2B customer engagement | All standard objects incl. Opportunities | Role-based sharing | ~$6/login or ~$15/member/mo |
| Partner Community | Channel partner/reseller portals | Leads, Opportunities, Campaigns, Cases | Full role hierarchy | ~$10/login or ~$25/member/mo |
| External Apps | High-volume custom applications | Custom + limited standard | Varies | Custom / volume-based |
| Employee Community | Internal portals (HR, intranet) | Accounts, Contacts, limited custom | Limited | Lower than full CRM |
Salesforce offers two pricing models for community licences. Choosing the wrong one is the single most common source of community licence overspend.
Fixed monthly fee per named user, regardless of login frequency. Highly predictable costs. Best for users who log in frequently (daily/weekly). The risk: high waste if many registered users rarely log in. Cost scales linearly with user count. Often purchased in bundles of 20+ members.
Pay per login session, pooled across all community users monthly. Best for users who log in infrequently (monthly/quarterly). Low waste because you only pay for actual usage. Cost scales with activity, not registration. Variable costs depending on actual login volume. Often purchased in bundles of 100+ logins/month.
If a user logs in 3 or more times per month, member-based is typically cheaper. If a user logs in fewer than 3 times per month, login-based wins. For large communities with mixed usage patterns, login-based usually wins because it eliminates the cost of dormant accounts.
| Factor | Member-Based | Login-Based |
|---|---|---|
| Pricing model | Fixed monthly fee per named user | Pay per login session (pooled monthly) |
| Best for | Frequent users (daily/weekly logins) | Infrequent users (monthly/quarterly) |
| Cost predictability | Highly predictable, fixed per user | Variable, depends on actual login volume |
| Waste risk | High if many registered users rarely log in | Low, you only pay for actual usage |
| Scalability | Cost scales linearly with user count | Cost scales with activity, not registration |
| Minimum purchase | Often bundles of 20+ members | Often bundles of 100+ logins/month |
A global insurer had 50,000 Customer Community member licences for a policyholder portal. Analysis showed only 12,000 users logged in monthly, with an average of 1.8 logins per active user per month. They were paying for 38,000 unused member licences. Switched to login-based at renewal: annual savings of $420K (58% reduction) with no change in user experience.
| Licence Type | Member Price (List) | Login Price (List) | Enterprise Range (Negotiated) |
|---|---|---|---|
| Customer Community | ~$5/user/month | ~$2/login | $1 to $3/login at volume |
| Customer Community Plus | ~$15/user/month | ~$6/login | $3 to $8/login at volume |
| Partner Community | ~$25/user/month | ~$10/login | $5 to $15/login at volume |
The primary cost driver. As communities scale to thousands or millions of users, costs grow quickly. This makes the choice of licence model (member vs login) and tier (Customer vs Plus vs Partner) critical. A 100,000-user community on the wrong tier and pricing model can overspend by $1M+ annually.
Needing role-based sharing or access to Opportunities forces you into higher-tier licences (Plus or Partner), which cost 3 to 5x more per user. Many organisations default to Customer Community Plus when base Customer Community would suffice. Challenge every Plus or Partner assignment with the question: does this user group genuinely need features beyond Cases, Knowledge, and custom objects?
Salesforce typically builds 7 to 10% annual price increases into standard renewal terms. If not capped in the initial contract, costs escalate significantly over a 3 to 5 year term. A 7% annual uplift compounds to 22.5% over 3 years. Required minimum licence quantities (often in bundles of 20+), annual commitments, and multi-year terms further impact the cost structure.
Paying for 10,000 member licences when only 2,000 are active is an ITAM red flag. And it is more common than most teams realise. Typical enterprise community licence estates carry 20%+ shelfware. This unused capacity compounds with annual uplifts, meaning you pay more each year for licences nobody uses.
| Pitfall | Risk Level | Impact | Mitigation |
|---|---|---|---|
| Wrong licence model (member vs login) | High | 30 to 60% overspend annually | Analyse login frequency data before committing |
| Over-provisioning (shelfware) | High | 20 to 50% of licences unused | Quarterly usage audits; deactivate dormant users |
| Wrong tier assignment | Medium | 3 to 5x cost per user | Map actual feature needs to minimum sufficient tier |
| Uncapped renewal uplifts | Medium | 7 to 10% annual increase compounding | Negotiate price caps in initial contract |
| Exceeding login pools | Medium | Overage charges or service disruption | Monitor monthly; set internal alerts at 80% |
| Ignoring Employee Community option | Medium | Paying full CRM price for light internal users | Evaluate Employee Community for internal portals |
Choosing member-based pricing for a large user base where most users log in infrequently. We routinely see enterprises paying 40 to 60% more than necessary because they defaulted to member-based without analysing actual login patterns. The fix is simple: pull login frequency data and model both pricing scenarios before committing or renewing.
Pull login frequency data for all community users. Identify inactive accounts (no login in 90+ days) and deactivate them. Reclaim member licences that are sitting unused. This single practice, consistently applied, typically recovers 15 to 25% of community licence spend.
Map each external user group to the minimum sufficient licence tier. Many organisations default to Customer Community Plus when base Customer Community would suffice. The difference is 3x per user. Challenge every Plus or Partner assignment with concrete feature requirements, not assumptions about what users might need.
Calculate the break-even point for your specific user base. If average logins per user per month are below 3, login-based is almost always cheaper. Run this analysis at every renewal using actual data from the preceding 12 months, not projections from when the community was first deployed.
Running multiple communities on separate contracts fragments your negotiating leverage. Consolidate into a single agreement where possible. Volume across all communities should be aggregated when negotiating pricing tiers and discounts.
For users who only need SSO/authentication without accessing Salesforce objects, Salesforce Identity licences (~$5/user/month) are dramatically cheaper than community licences. Many community portals have a segment of users who authenticate but never interact with Salesforce data. These users should be on Identity licences, not community licences. See Maximising Value from Identity Licences.
Present actual login frequency and user activity data in negotiations. Salesforce reps cannot argue against your own usage metrics showing 60% of member licences are dormant. Data transforms the negotiation from a vendor-controlled pricing discussion into an evidence-based commercial conversation.
Community licences have significant margin for Salesforce. Enterprise deals with 10,000+ users should target 30 to 50% off list price. Larger deployments (50,000+ users) may achieve even greater discounts. The key is knowing your volume gives Salesforce revenue certainty that justifies the discount.
Standard Salesforce contracts include 7 to 10% annual price increases. Negotiate a cap of 3 to 5% maximum, or lock pricing for the full contract term. A 7% annual uplift over a 3-year term compounds to 22.5% above initial pricing. Over 5 years it reaches 40%. Capping this at 3% reduces the 5-year compounding to 15.9%, saving hundreds of thousands on large community estates.
Negotiate the ability to switch between member and login-based pricing at renewal, or even mid-term if usage patterns change significantly. Also negotiate the right to downgrade tier assignments (from Plus to base Customer Community) without penalty if feature requirements change.
Community licence negotiations have more leverage when bundled with a larger CRM renewal. Do not negotiate them in isolation. The total Salesforce relationship value gives you more commercial leverage than a standalone community deal.
Salesforce's fiscal year ends January 31. The best discounts are typically available in Q4 (November to January), when account executives are motivated to close deals against annual targets. If your renewal timing allows, align community licence negotiations to this window.
Choosing member licences without analysing actual login frequency. Enterprises routinely overspend 40 to 60% by not modelling login-based alternatives. The fix: pull 90 days of login data and run the comparison before every renewal.
Assigning Customer Community Plus or Partner licences when base Customer Community meets the actual feature requirements. The cost difference is 3 to 5x per user. Every user group should be mapped to the minimum sufficient tier based on documented feature needs.
Paying for thousands of member licences where 20 to 50% of registered users have never logged in or have not logged in for 6+ months. Deactivate dormant accounts quarterly. Every unused licence costs money and inflates your renewal baseline.
Auto-renewing at 7 to 10% annual uplifts without negotiation. Over a 3-year term, this compounds to 21 to 33% above initial pricing. Every renewal is a negotiation opportunity. Treat it as one.
Missing the leverage of bundling community licences with CRM renewals or new product purchases. Your total Salesforce spend is your leverage. Use it.
Committing to a pricing structure that works at 10,000 users but becomes uneconomical at 100,000 users. Negotiate volume tiers upfront that provide automatic discounts as your community grows beyond defined thresholds.
Paying for community licences for users who only need SSO authentication, when Salesforce Identity licences cost a fraction of the price. Segment your user base: if a user never interacts with Salesforce objects, they should not be on a community licence.
Lacking the reporting to track login frequency, active users, and licence utilisation. Without this data, you cannot optimise, negotiate, or identify waste. Build login frequency reporting into your ITAM platform before the next renewal cycle.
Document every community licence type, quantity, pricing model (member vs login), contract terms, and renewal dates. Map each licence to its assigned user group and business purpose. This inventory is the foundation for every optimisation and negotiation activity that follows.
Pull login frequency reports for all community users. Calculate: total active users (logged in within 90 days), average logins per user per month, peak monthly login volumes, and inactive/dormant accounts. This data drives every decision from pricing model selection to shelfware elimination.
Using the usage data, calculate the cost of your current structure vs alternatives. Compare member-based vs login-based economics. Identify users who could be downgraded to a lower tier or switched to Identity licences. Quantify the savings opportunity for each change.
Compile usage data, competitive alternatives, and target pricing into a negotiation brief. Identify key asks: price caps, right-to-downgrade, volume tiers, non-production environments. Time the negotiation around Salesforce's fiscal calendar (Q4: November to January).
Establish quarterly licence utilisation reviews. Set automated alerts for login pool thresholds (80%). Integrate community licence tracking into your ITAM platform. Create a process for deactivating users who have not logged in for 90+ days. Without ongoing governance, optimisation erodes within one renewal cycle.
Customer Community provides basic self-service access (Cases, Knowledge, custom objects) without role-based sharing. Customer Community Plus adds access to all standard objects (including Opportunities and Leads), supports the full Salesforce roles and sharing model, and enables reports and dashboards. Plus is designed for B2B scenarios requiring more refined data access but costs roughly 3x more per user. Only choose Plus when you genuinely need role-based sharing or access to standard objects beyond Cases and Knowledge.
Analyse your users' login frequency. If the average user logs in 3+ times per month, member-based is typically cheaper. If users log in less than 3 times per month, login-based provides better economics because you only pay for actual usage. For large communities with mixed usage patterns, login-based usually wins because it eliminates the cost of dormant accounts. Pull 90 days of actual login data before deciding.
Enterprise deals with 10,000+ users should target 30 to 50% off list price. Larger deployments (50,000+ users) may achieve even greater discounts. Key factors: volume commitment, contract length, bundling with CRM renewals, and timing relative to Salesforce's fiscal year-end (January 31). Community licences have significant margin, meaning Salesforce has room to negotiate.
For very large communities, consider External Apps licences or negotiate custom volume-based pricing with Salesforce. Login-based models tend to be most economical at scale since you only pay for active sessions. Also evaluate whether some users only need authentication (Salesforce Identity licence) rather than full community access.
Not by default. Salesforce locks you into your chosen model for the contract term. However, you can and should negotiate the right to switch at renewal (or even mid-term) as part of your initial contract. This flexibility is especially important for growing communities where usage patterns are still evolving.
Employee Community (Employee Apps) licences provide limited Salesforce access (Accounts, Contacts, basic custom objects) for internal employees or contractors who do not need full CRM functionality. They are ideal for HR portals, internal knowledge bases, or helpdesks, and cost significantly less than standard Sales/Service Cloud licences. If you are paying full CRM licence costs for employees who only use an internal portal, Employee Community licences can reduce that cost substantially.
Redress Compliance provides independent Salesforce advisory: licence optimisation, community pricing benchmarking, contract negotiation, renewal preparation, and audit defence. We help enterprises right-size community licences, switch pricing models, negotiate volume discounts, and cap renewal uplifts. Complete vendor independence. No Salesforce partnerships, no resale commissions.
Salesforce Advisory ServicesIndependent Salesforce advisory helping enterprises optimise community licence types, pricing models, and contract terms. Fixed-fee engagement models.