Understanding Login-Based Licenses in Salesforce: A Complete Guide

When working on large-scale Salesforce implementations, especially for communities (now called Experience Cloud), one common challenge is managing millions of users cost-effectively. This is where Login-Based Licenses come into play.

In this article, I’ll explain what they are, how they work, their advantages, and some pitfalls you should be aware of before implementing them.

🔑 What is a Login-Based License?

In Salesforce, most licenses are named user licenses – meaning each person who needs access is assigned a license. This works well for employees or partners who log in regularly.

But what if you have a large customer base (say, millions of retail customers) who log in occasionally — maybe once or twice a month? Buying a full license for each user becomes impractical and expensive.

That’s where Login-Based Licenses help.

👉 With a Login-Based License, you don’t pay for each user individually. Instead, you purchase a bundle of logins per month. A login is consumed only when a user signs in.

⚙️ How Does It Work?

• You buy a pack of logins per month (e.g., 10,000 logins).

• Any number of users can exist in your Salesforce org.

• Each time a user signs in, one login is deducted from the pool.

• If a user does not log in, no cost is incurred.

For example:

• You have 1 million registered users.

• On average, only 50,000 users log in during a month.

• Instead of buying 1 million full licenses, you can purchase 50,000 logins — saving significant cost.

✅ Advantages of Login-Based Licenses

1. Cost Efficiency

   • Perfect for large communities where only a fraction of users are active each month.

2. Scalability

   • You can support millions of registered users without worrying about license assignment.

3. Flexibility

   • Users who log in rarely still have access when they need it.

4. Pay-As-You-Use

   • You’re essentially charged for usage, not registration.

⚠️ Disadvantages & Limitations

1. Usage Spikes Can Hurt

   • If suddenly too many users log in (say during a product launch), you may run out of logins and need to purchase more.

2. Not Ideal for Daily Users

   • If the same users login every day, a named license may actually be cheaper.

3. Complex Forecasting

   • Predicting the number of logins per month can be tricky. Overestimating leads to wasted cost, underestimating may block users.

4. Different Features Across Licenses

   • Login-based licenses don’t always include the same features as named user licenses. You must check Salesforce documentation carefully.

📊 Login-Based vs Named User Licenses

💡 Real-World Example

A retail company creates a customer portal in Salesforce Experience Cloud.

• Total registered customers: 3 million

• Active monthly users: 200,000

• Average logins per customer: 2 per month

Instead of buying 3 million full licenses, the company can simply buy 400,000 monthly logins (200k users × 2 logins each).

This reduces cost dramatically while still giving users access when needed.

🎯 Key Takeaway

Login-Based Licenses in Salesforce are an excellent option when dealing with large, infrequently active user bases. They provide a flexible, cost-effective model for customer communities, but require careful monitoring and forecasting to avoid unexpected limits.

When designing a Salesforce licensing strategy, always analyse:

• User base size

• Average login frequency

• Peak usage trends

A smart mix of Named User and Login-Based Licenses can help you achieve the best balance of cost and performance.