Locations Resources Contact 📅 Book a Meeting
Salesforce Licensing

Salesforce Community Licensing: The Enterprise ITAM Guide

📘 This guide is part of our Salesforce Licensing Knowledge Hub — your comprehensive resource for Salesforce licensing, compliance, and cost optimization.

An independent Salesforce licensing advisoryy breakdown of Salesforce Experience Cloud community licences — licence types, member-based vs login-based pricing models, compliance pitfalls, cost optimisation strategies, and negotiation tactics for CIOs, ITAM teams, and procurement leaders.

📄 Comprehensive Guide ⏱ 18 min read 🔄 Updated July 2025
$2–$25 Per-user/per-login list price range across community licence tiers
20%+ Typical shelfware in enterprise community licence estates
7–10% Annual Salesforce uplift built into standard renewal terms
30–50% Enterprise-achievable discount off list for community licences

What Is Salesforce Community Licensing?

Salesforce Experience Cloud (formerly Community Cloud) enables organisations to build branded portals and communities for customers, partners, and external stakeholders. Salesforce community licensing governs how these external users access Salesforce data and functionality — and it works fundamentally differently from standard internal user licences.

Unlike full CRM seats, community licences are purpose-built for external users who need limited access to specific Salesforce objects and features. They come in several tiers, each with distinct capabilities, cost structures, and technical limits. For Salesforce's official product overview, see the Experience Cloud product page.

For enterprise ITAM teams, mastering these licence models is essential. Community deployments can scale to hundreds of thousands of external users — meaning even small per-user cost differences compound into millions of dollars over a Salesforce contract terms. The choice between licence types, and between member-based and login-based pricing, directly determines whether your Salesforce community is a cost-efficient engagement platform or an escalating line item that grows unchecked.

"Community licences look cheap on paper, but enterprises routinely overspend by 30–40% because they don't match licence types to actual user behaviour. The difference between a $5 Customer Community seat and a $25 Partner licence — multiplied by 50,000 users — is $12 million per year. Getting this wrong is one of the most expensive ITAM mistakes we see."

— Fredrik Filipsson, Co-Founder, Redress Compliance

Community Licence Types and Features

Salesforce offers several community licence types, each designed for different external user groups. Understanding the capabilities and limits of each is critical for right-sizing your estate. For a broader view of all Salesforce licence categories, see our complete Salesforce licence types guide.

Licence TypeTarget UsersCRM Object AccessRoles & SharingBest For
Customer CommunityExternal customers (B2C)Cases, Knowledge Articles, limited custom objectsNo role hierarchy; basic sharingHigh-volume self-service portals
Customer Community PlusExternal customers (B2B)All standard objects incl. Opportunities, LeadsFull role hierarchy and sharing modelComplex customer communities needing collaboration
Partner CommunityResellers, distributors, partnersFull CRM objects incl. Leads, Opportunities, CampaignsFull role hierarchy and sharingPRM portals; partner deal registration
External AppsMassive-scale external appsCustom objects, API access, platform featuresConfigurableHigh-volume custom portals (100K+ users)
Employee CommunityInternal employees / contractorsAccounts, Contacts, limited custom objectsLimitedInternal intranets, HR portals at lower cost

Key Differences That Drive Cost

The most important distinctions between licence types are CRM object access and sharing model support. Customer Community licences exclude Opportunities and Campaigns entirely — this is intentional, as it keeps costs low for basic self-service use cases. The moment your business requirement includes pipeline visibility, deal registration, or advanced data sharing, you are forced into Plus or Partner tiers at 3–5× the cost.

Each licence type also has technical limits on the number of custom objects users can access. Customer Community is capped at a lower number than Plus or Partner. ITAM teams must coordinate closely with Salesforce administrators to ensure community expansions do not exceed these licensed capabilities.

Over-Engineering Alert: Assigning Partner Community licences to all external users when most only need basic self-service access is the single most common waste driver. Audit your user base before assigning licence types — the savings are immediate and significant.

📋

Whitepaper: Salesforce Shelfware Playbook

Uncover the blind spots in your Salesforce estate. Learn how to audit logins, API activity, and integration usage — then turn that data into leverage during your next renewal or SELA negotiation.

Download the Playbook →

Member-Based vs Login-Based Licensing Models

A distinctive feature of Salesforce community licensing is the choice between two fundamentally different pricing models. This decision has a direct, material impact on your total cost of ownership.

DimensionMember-BasedLogin-Based
Pricing UnitFixed cost per named user / monthCost per login session (24-hour window)
Cost PredictabilityHigh — fixed monthly commitmentVariable — depends on actual usage
Best ForKnown, active user base with frequent accessLarge, variable user base with infrequent access
Break-Even PointMember model wins when users log in 3+ times/monthLogin model wins when users log in <3 times/month
Unused Licence RiskHigh — you pay even if users never log inLow — no login = no cost consumed
ScalabilityMust purchase additional seats proactivelyPool scales across all community users

The 3-Login Rule of Thumb

Across most community licence tiers, the economic crossover point sits at approximately 3 logins per user per month. If an external user accesses the community more than three times monthly, the flat member-based fee is typically cheaper than paying per-login. Below that threshold, the login pool model delivers better value.

Enterprise communities are rarely homogeneous. Most contain a mix of power users (daily access) and occasional visitors (quarterly or annual). The optimal strategy is often a hybrid approach: member licences for your top-tier active users and a shared login pool for the long tail of infrequent visitors.

"We consistently see enterprises defaulting to member-based licences without analysing actual login behaviour. In one engagement, a manufacturing client with 40,000 community users discovered that 60% logged in fewer than twice a quarter. Shifting those users to login-based licensing saved them $1.2 million annually — with zero impact on user experience."

— Fredrik Filipsson, Co-Founder, Redress Compliance
Need help analysing your community login data? We can benchmark your estate. Salesforce Optimisation →

Pricing, Cost Drivers, and Enterprise Benchmarks

Community licence pricing varies significantly by licence type and pricing model. The table below shows the standard list prices as of 2025. For official Salesforce pricing details, refer to Salesforce's Experience Cloud pricing page.

Licence TypeMember-Based (per user/month)Login-Based (per login)Typical Use Case
Customer Community$5 USD$2 USDLarge customer self-service portals with many infrequent users
Customer Community Plus$15 USD$6 USDB2B customer communities requiring advanced sharing and frequent logins
Partner Community$25 USD$10 USDPartner portals (resellers, B2B) needing full CRM data access
External Apps$35 USD$15 USDMassive-scale or custom external applications on the Salesforce platform

What Actually Drives Community Licensing Cost

User volume is the primary cost driver. As communities scale to tens of thousands or millions of users, the compounding effect of per-user pricing is enormous. A 100,000-user Customer Community at list price costs $500,000/month ($6M/year) on member licences alone.

Feature requirements force tier upgrades. Needing role-based sharing or Opportunity access pushes you from Customer Community ($5) to Plus ($15) or Partner ($25) — a 3–5× multiplier that compounds at scale.

Contract minimums are a hidden cost trap. Salesforce typically requires minimum licence quantities (often bundles of 20 or more) and multi-year commitments. Combined with the standard no-reduction clause — you cannot decrease licence counts mid-term — over-purchasing at contract signing becomes locked-in waste. See our guide on managing Salesforce licensing minimums and true-ups for detailed strategies.

Unused licences represent pure waste. Paying for 10,000 member licences when only 2,000 are active is an ITAM red flag — and far more common than most organisations realise.

Case Study — Global Retailer

$1.8M annual savings

A global retailer with 85,000 Customer Community Plus licences was paying $15.3M annually. A Redress Compliance audit revealed that 52,000 users logged in fewer than twice per quarter. By shifting infrequent users to login-based licensing, right-sizing the member pool to 33,000, and renegotiating at renewal, the client reduced annual spend by $1.8M while maintaining full community functionality.

📊

Whitepaper: Benchmarking Salesforce Discounts

Uncover real-world discount ranges, compliance risks, and negotiation tactics — based on multi-million-dollar Salesforce deals across CRM, Platform, Analytics, and Marketing Cloud.

Download the Benchmark Report →

Common Pitfalls and Compliance Risks

Managing community licensing at enterprise scale introduces risks that most organisations underestimate. The combination of large external user populations, variable usage patterns, and rigid contract terms creates a landscape where expensive mistakes are disturbingly common.

PitfallWhat HappensFinancial ImpactMitigation
Over-Licensing (Shelfware)Purchased member licences far exceed active users20–40% of community spend wasted on unused seatsQuarterly usage audits; deactivation policies
Under-LicensingLogin pool exhausted mid-month; users blockedEmergency purchases at list price; user disruptionMonitor at 80% threshold; auto-alerts
Wrong Licence TypePartner licences assigned to users who only need self-service3–5× overspend per user at scaleMap user requirements to cheapest qualifying tier
Rigid Contract TermsNo-reduction clause prevents adjusting mid-termYears of locked-in over-commitmentNegotiate annual true-down rights at signing
Login Carry-Over ConfusionUnused logins do not roll over month to monthOverpurchased login pools reset to zero each monthSize login pool to peak-month usage, not average
Technical Limit BreachesCommunity customisations exceed licence allowancesRe-architecture costs; forced tier upgradesCoordinate admins with ITAM on licence capabilities

Credential Sharing Risk: When community licences are too restrictive, some organisations find users sharing logins to access features they need. This violates Salesforce's terms and can trigger compliance enforcement during renewals. Right-sizing licences eliminates this risk entirely.

The SELA Trap for Community Licences

Enterprises with Salesforce Enterprise Licence Agreements (SELAs) often bundle community licences into the agreement. While this can yield volume discounts, it also obscures per-component pricing and makes it difficult to identify community-specific waste. SELAs have been shown to result in organisations paying significantly more than necessary compared to itemised contracts — and community licences buried inside bundled deals are frequently the worst offenders.

Case Study — US Financial Services Firm

30% cost reduction on Salesforce SELA

A major US financial institution discovered approximately 3,000 unused community and CRM licences within its bundled SELA. A Redress Compliance audit and renegotiation eliminated the shelfware, right-sized the remaining licences, and secured a 30% reduction in total Salesforce spend — including community licence costs.

Optimising Community Licences at Enterprise Scale

For global enterprises serving tens of thousands of external users, community licence management is an ongoing discipline — not a one-time procurement decision. Effective optimisation requires continuous visibility into usage patterns, governance processes, and strategic contract management.

Regular Usage Audits

ITAM teams should receive and review monthly usage reports covering login counts, active user counts, and licence utilisation rates. Track trends over time: is login volume rising with community growth? Are a significant percentage of member licences unassigned or assigned to inactive users? Use this data to adjust licence quantities or convert between models at renewal.

Governance and Access Policies

Implement formal governance for community onboarding. Ensure each new partner or customer user is assigned the correct and lowest-cost qualifying licence type. Automate de-provisioning of external users who have not logged in for a defined period (e.g., 90 days). Strong identity management and periodic access reviews prevent licence bloat from forgotten accounts — a chronic problem in large-scale communities.

Licence Model Adjustments

Salesforce allows customers to mix licence types within a community and, to some extent, convert between models at renewal. Enterprises should reassess their model mix annually. An influx of active users might warrant shifting more users to member-based licensing; conversely, declining engagement might make login-based pools more economical.

Contract Negotiation Leverage

Include community licences in your overall Salesforce negotiation strategy. Leverage your total Salesforce spend to negotiate better community rates. Key provisions to pursue include annual true-up/true-down rights without penalty, login pooling across multiple community sites, and explicit volume discount tiers that kick in as your community grows.

"The most sophisticated ITAM organisations treat community licence management as a continuous feedback loop: usage data feeds into quarterly reviews, which drive model adjustments, which inform the next renewal negotiation. This cycle consistently delivers 15–25% savings over 'set and forget' approaches."

— Fredrik Filipsson, Co-Founder, Redress Compliance
📑

Whitepaper: Cracking the Salesforce SELA

Hidden clauses, risk traps, and how to counter them. Learn what enterprise leaders need to know before signing their next Salesforce Enterprise Licence Agreement — including how community licences get buried in bundles.

Download the SELA Report →

Need Expert Salesforce Licensing Guidance?

Redress Compliance provides independent Salesforce licensing advisory services — fixed-fee, no vendor affiliations. Our specialists help enterprises optimize Salesforce contracts, evaluate AI add-ons, and reduce renewal costs.

Explore Salesforce Advisory Services →

Negotiation Strategies for Community Licences

Salesforce is one of the most disciplined enterprise sales organisations in the software industry. Their community licence negotiations are no exception. For a comprehensive negotiation playbook covering all Salesforce products, see our CIO Playbook for Salesforce Contract Negotiations.

StrategyWhat It AchievesHow to Execute
Right-Size Before NegotiatingReduces the baseline Salesforce quotes againstAudit usage 6 months before renewal; deactivate unused accounts; document actual active user counts
Benchmark Discount RatesEnsures your quoted price is competitiveCompare against industry benchmarks; 30–50% off list is achievable for enterprise-scale community deals
Negotiate True-Down RightsProtects against paying for users who leaveDemand annual licence reduction clauses with no penalty — especially important for volatile community populations
Time the DealExploits Salesforce's fiscal pressureSalesforce fiscal year ends 31 January (quarters in April, July, October). Align closing with quarter-end for maximum discount leverage
Leverage Competitive AlternativesCreates credible switching pressureResearch Microsoft Dynamics 365 portals, HubSpot, or ServiceNow CSM as alternatives; present cost comparisons
Pool Logins Cross-CommunityMaximises login utilisation across sitesNegotiate a single shared login pool that spans all Experience Cloud sites in your org

Case Study — Global Technology Manufacturer

$4.2M annual savings

A 40,000-employee global technology company engaged Redress Compliance to renegotiate its Salesforce agreement, including a significant community licence component. Through comprehensive usage auditing, licence right-sizing, discount benchmarking, and structured negotiation, the client achieved $4.2M in annual savings with significantly improved contract contract flexibility assessment.

Approaching a Salesforce renewal? Get independent negotiation support. Salesforce Negotiation →

The 8 Most Costly Community Licensing Mistakes

5-Step ITAM Action Checklist

⚖️

Whitepaper: Salesforce Contract Terms That Cost Enterprises Millions

Audit traps, indirect use risks, forced renewals, and price escalators — they're all in your Salesforce agreement. Learn the contract clauses you must remove before you sign.

Download the Contract Guide →

📊 Free Assessment Tool

Evaluating your Experience Cloud licensing? Our free contract flexibility assessment identifies cost optimization opportunities.

Take the Free Assessment →

Frequently Asked Questions

What is the difference between Customer Community and Customer Community Plus?
Customer Community is a basic licence for external users focused on support and self-service features — Cases, Knowledge Articles, and limited custom objects. Customer Community Plus adds access to all standard CRM objects (including Leads, Opportunities, and Campaigns) and supports full role-based sharing and hierarchy. Plus is required when external users need collaboration capabilities, pipeline visibility, or advanced data access — at approximately 3× the cost.
How do we decide between member-based and login-based licensing?
Analyse your actual user login frequency using at least 3–6 months of data. The break-even point for most licence types is approximately 3 logins per user per month. Users who log in more frequently than that are cheaper on member licences; those who log in less frequently are cheaper on login-based pools. Most enterprises benefit from a hybrid approach — member licences for power users and a shared login pool for occasional visitors.
Can we mix different community licence types in one Salesforce org?
Yes. You can assign different licence types to different users and run multiple community sites with different licensing models within the same Salesforce org. For example, you might operate a customer self-service community using Customer Community licences alongside a partner portal using Partner Community licences.
What are External Apps licences, and when are they needed?
External Apps is a higher-tier licence designed for very high-volume external use cases or custom portals that go beyond standard community functionality. They provide more flexible entitlements and platform capabilities, and can be more cost-effective than standard community licences at extreme scale (hundreds of thousands of users). Consider External Apps when your community requires extensive custom development, API-heavy integrations, or massive user volumes that make standard licence tiers prohibitively expensive.
Do unused logins carry over to the next month?
No. Login-based pools reset at the start of each billing month. Unused logins from one month do not roll over. This is a common source of waste — enterprises should size their login pool for peak-month demand and monitor consumption monthly to avoid both over- and under-purchasing.
Can we reduce community licence quantities mid-contract?
Under Salesforce's standard terms, no. The no-reduction clause means you are committed to the contracted quantity for the full term. Reductions can only be applied at renewal. This is why negotiating annual true-down rights (or at minimum, the ability to adjust at each anniversary) at contract signing is critical — especially for community licences where external user populations can be volatile. Read more about managing Salesforce licensing minimums and true-ups.
How does Salesforce enforce community licence compliance?
Salesforce primarily enforces compliance through technical controls — you cannot create more active community users than you have licences for. However, SELA and broader contract audits can flag discrepancies between licensed entitlements and actual usage patterns. Misclassification (e.g., users on lower-tier licences accessing features beyond their entitlement) can also trigger compliance discussions at renewal.
Should we include community licences in our SELA?
It depends. Bundling community licences into a Salesforce SELA can yield volume discounts, but it also obscures per-component pricing and makes it difficult to identify community-specific waste. If you choose to bundle, insist on line-item transparency for community licence quantities, types, and unit pricing within the agreement.
What discounts should we expect on community licences?
Enterprise-scale community deployments (10,000+ users) should target 30–50% off list price. Very large deployments (100,000+ users) can often achieve even deeper discounts, particularly when bundled with other Salesforce product commitments. Use independent benchmarking data to validate that your quoted pricing is competitive — Salesforce's first offer is almost never their best.
How do community licences interact with Salesforce Platform licences?
Community licences and Platform licences serve fundamentally different purposes. Platform licences are for internal users who need custom app access without full CRM functionality. Community licences are for external users (customers, partners). Some enterprises incorrectly assign Platform licences to external users or community licences to internal employees — both create compliance risk and cost inefficiency.
What about Marketing Cloud community licence interactions?
If your community users receive marketing communications via Salesforce Marketing Cloud, you may have overlapping licence requirements. Marketing Cloud licensing is consumption-based (contacts, messages), while community licensing is user- or session-based. Ensure your ITAM team tracks both to avoid double-counting users or over-provisioning across products.
Where can we find official Salesforce community licence documentation?
Salesforce publishes Experience Cloud licence details on their editions and pricing page. For technical licence comparisons, the Salesforce Help article on community licence types provides detailed feature-by-feature breakdowns. However, list prices and feature descriptions may not reflect negotiated enterprise terms — always benchmark against independent market data.

Is Your Salesforce Community Estate Optimised?

Most enterprises overspend on community licences by 20–40%. Our independent advisory team will analyse your current Salesforce community licensing, identify savings opportunities, and provide negotiation support to secure the best possible terms at your next renewal.

Related Salesforce Licensing Reading

Salesforce Whitepapers & Downloads

Deep-dive research reports to help enterprise leaders take control of their Salesforce licensing estate:

How Redress Compliance Can Help

Salesforce Licence Optimisation

Independent usage analysis, licence right-sizing, and model optimisation to eliminate waste.

Learn More →

Salesforce Contract Negotiation

Expert-led negotiation for renewals, new deals, and enterprise licence agreements.

Learn More →

Salesforce Advisory Services

End-to-end Salesforce licensing strategy across CRM, Platform, Marketing Cloud, and Experience Cloud.

Learn More →
FF

Fredrik Filipsson

Co-Founder of Redress Compliance. Over 20 years of experience in enterprise software licensing across Oracle, Microsoft, SAP, IBM, and Salesforce. Former IBM, SAP, and Oracle executive. Has helped hundreds of Fortune 500 companies optimise costs, defend against audits, and negotiate favourable terms with major software vendors.

Related Guides

Community Licensing Overview Salesforce Contract Terms Salesforce Add-Ons Worth Paying For Salesforce CPQ Licensing Playbook Data Cloud Licensing Agentforce Licensing Guide

Explore More Licensing Hubs

Oracle Licensing Hub Microsoft Licensing Hub SAP Licensing Hub IBM Licensing Hub Salesforce Licensing Hub ServiceNow Licensing Hub

Ready to Take Control of Your Software Licensing?

Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.

Book Your Free Consultation →