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.
1. What Is Salesforce Community Licensing?
Salesforce Experience Cloud enables organisations to create portals and communities for external users — customers, partners, and employees. Community Salesforce 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 require careful planning to implement cost-effectively. The primary cost driver is the number of external users or login volume, and as communities scale to thousands or millions of users, costs can grow quickly.
2. Community Licence Types and Features
Customer Community
- Self-service portals for customers
- Access to Cases, Knowledge, custom objects
- No access to Opportunities, Leads
- No role-based sharing model
- Scales to millions of users
Customer Community Plus
- All standard objects including Opportunities
- Role-based sharing and visibility
- Reports and dashboards
- B2B customer communities
- Higher per-user cost than base tier
Partner Community
- Leads, Opportunities, Campaigns access
- Full role hierarchy & sharing
- PRM (Partner Relationship Mgmt)
- Most feature-rich community licence
- Best for resellers, distributors
External Apps
- High-volume external applications
- Extensive custom development
- Extra API calls and storage
- Scales to 100K+ users
- Premium pricing, volume economics
| 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 |
3. Member-Based vs Login-Based Models
| Factor | Member-Based | Login-Based |
|---|---|---|
| Pricing model | Fixed monthly fee per named user | Pay per login session (pooled monthly) |
| Best for | Users who log in frequently (daily/weekly) | Users who log in infrequently (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 |
| Break-even | If a user logs in ≥3 times/month, member-based is typically cheaper. If <3 times/month, login-based wins. | |
📋 Case Study — Insurance Company Switches to Login-Based
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.
4. Pricing, Cost Drivers, and Benchmarks
| Licence Type | Member Price (List) | Login Price (List) | Enterprise Range (Negotiated) |
|---|---|---|---|
| Customer Community | ~$5/user/month | ~$2/login | $1–$3/login at volume |
| Customer Community Plus | ~$15/user/month | ~$6/login | $3–$8/login at volume |
| Partner Community | ~$25/user/month | ~$10/login | $5–$15/login at volume |
Key cost drivers
- Number of external users or login volume: The primary driver. As communities scale to thousands or millions of users, costs grow quickly — making the choice of licence model critical.
- Feature requirements: Needing role-based sharing or access to Opportunities forces you into higher-tier licences (Plus or Partner), which cost 3–5× more per user.
- Contract terms: Required minimum licence quantities (often in bundles of 20+), annual commitments, and multi-year terms impact the cost structure.
- Annual uplift: Salesforce typically builds 7–10% annual price increases into standard renewal terms. If not capped in the initial contract, costs escalate significantly over a 3–5 year term.
- Unused licences (shelfware): Paying for 10,000 member licences when only 2,000 are active is an ITAM red flag — and more common than most teams realise.
5. Common Pitfalls and Compliance Risks
| Pitfall | Risk Level | Impact | Mitigation |
|---|---|---|---|
| Wrong licence model (member vs login) | 🔴 High | 30–60% overspend annually | Analyse login frequency data before committing |
| Over-provisioning (shelfware) | 🔴 High | 20–50% of licences unused | Quarterly usage audits; deactivate dormant users |
| Wrong tier assignment | 🟠 Medium | 3–5× cost per user | Map actual feature needs to minimum sufficient tier |
| Uncapped renewal uplifts | 🟠 Medium | 7–10% annual increase compounding | Negotiate price caps in initial contract |
| Exceeding login pools | 🟡 Low-Med | Overage charges or service disruption | Monitor monthly; set internal alerts at 80% |
| Ignoring Employee Community option | 🟡 Low-Med | Paying full CRM price for light internal users | Evaluate Employee Community for internal portals |
The most expensive community licensing mistake: choosing member-based pricing for a large user base where most users log in infrequently. We routinely see enterprises paying 40–60% more than necessary because they defaulted to member-based without analysing actual login patterns.
6. Optimising Licences at Enterprise Scale
- Audit usage quarterly: 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.
- Right-size licence tiers: Map each external user group to the minimum sufficient licence tier. Many organisations default to Customer Community Plus when base Customer Community would suffice.
- Model member vs login economics: 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.
- Consolidate communities: Running multiple communities on separate contracts fragments your negotiating leverage. Consolidate into a single agreement where possible.
- Leverage Salesforce Identity licences: For users who only need SSO/authentication without accessing Salesforce objects, Salesforce Identity licences (~$5/user/month) are dramatically cheaper than community licences.
- Monitor for seasonal spikes: If your community has seasonal usage patterns (e.g., open enrolment periods), ensure your login pool accounts for peaks without permanently over-provisioning.
Need help optimising your Salesforce community licensing? Our team has saved clients millions.
Get Expert Advisory →7. Negotiation Strategies for Community Licences
- Use data as leverage: 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.
- Negotiate volume discounts aggressively: Community licences have significant margin for Salesforce. Enterprise deals with 10,000+ users should target 30–50% off list price.
- Cap annual uplifts: Standard Salesforce contracts include 7–10% annual price increases. Negotiate a cap of 3–5% maximum, or lock pricing for the full contract term.
- Demand right-to-downgrade: Negotiate the ability to switch between member and login-based pricing at renewal, or even mid-term if usage patterns change significantly.
- Bundle community with CRM renewals: Community licence negotiations have more leverage when bundled with a larger CRM renewal. Don't negotiate them in isolation.
- Time negotiations around Salesforce fiscal year-end: Salesforce's fiscal year ends January 31. The best discounts are typically available in Q4 (November–January).
8. The 8 Most Costly Community Licensing Mistakes
1. Defaulting to member-based without data
Choosing member licences without analysing actual login frequency. Enterprises routinely overspend 40–60% by not modelling login-based alternatives.
2. Over-tiering users
Assigning Customer Community Plus or Partner licences when base Customer Community meets the actual feature requirements.
3. Ignoring shelfware
Paying for thousands of member licences where 20–50% of registered users have never logged in or haven't logged in for 6+ months.
4. Accepting default renewal terms
Auto-renewing at 7–10% annual uplifts without negotiation. Over a 3-year term, this compounds to 21–33% above initial pricing.
5. Negotiating community licences in isolation
Missing the leverage of bundling community licences with CRM renewals or new product purchases.
6. Not modelling growth scenarios
Committing to a pricing structure that works at 10,000 users but becomes uneconomical at 100,000 users. Negotiate volume tiers upfront.
7. Overlooking Identity licences
Paying for community licences for users who only need SSO authentication, when Salesforce Identity licences cost a fraction of the price.
8. No usage monitoring infrastructure
Lacking the reporting to track login frequency, active users, and licence utilisation — making it impossible to optimise or negotiate with data.
9. 5-Step ITAM Action Checklist
- Audit current community licence inventory: 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.
- Analyse actual usage data: 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.
- Model optimal licensing structure: 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.
- Build negotiation position: 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.
- Implement ongoing governance: 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 haven't logged in for 90+ days.