Salesforce License Types Explained: Which One Do Your Users Actually Need?

When a new hire joins the sales team, someone provisions them a Salesforce Enterprise seat. When a manager asks for Salesforce access to view reports, they get the same Enterprise seat. When the integration that syncs your CRM to your marketing platform needs an API user, it gets an Enterprise seat too.

Enterprise is the default because it's what the admin knows, and because adding a seat is faster than understanding whether a different license type would work. The result: most Salesforce orgs have 20–30% of their seats on licenses that are far more expensive than what the user's actual job requires.

This guide explains what each license type actually covers, which user roles belong on each one, and where the money is most commonly being wasted.

TL;DR: The right license for each user depends on what objects they access, whether they use Sales Cloud or Service Cloud features specifically, whether they need read-only or read-write access, and whether they're internal or external. Most orgs have a meaningful percentage of users on Enterprise or Unlimited who would work fine on Platform or a lighter license — at $140/user/month less.

The core Salesforce license types

Salesforce (Enterprise / Unlimited / Professional)

These are the flagship CRM licenses. They include full access to Sales Cloud, Service Cloud, and the core Salesforce platform.

Enterprise is the right license for active Salesforce CRM users — salespeople, account managers, CSMs, service agents — who need automation, custom reporting, and API integrations. Unlimited is only justified if you're a large org that actively uses multiple sandboxes for development and needs Salesforce's premier support tier.

Common overspend: Read-heavy users (executives who view dashboards, marketing ops who review reports, RevOps analysts who pull data) often end up on Enterprise or Unlimited when they don't use the automation or API features that justify the price.

Salesforce Platform ($25/user/month list)

The Platform license is for users who need to access custom apps built on Salesforce but don't need core Sales Cloud or Service Cloud objects (Leads, Opportunities, Cases, Accounts beyond basic read).

The Platform license includes: access to custom objects, custom apps, Apex/Visualforce pages, Lightning pages, basic Salesforce functionality. It excludes: Leads, Opportunities, Forecasting, Service Console, Territory Management, most Sales Cloud and Service Cloud features.

Right fit for: Internal tool users (finance, HR, operations, legal) who use a custom Salesforce app built on the platform but don't need CRM functionality. Field service workers accessing a custom scheduling app. Internal users who need approval workflows on custom objects but not on opportunities.

The savings math: A user on Enterprise at $165/month who only uses a custom app on Salesforce could be on Platform at $25/month. That's $1,680/user/year saved. Across 15 users, $25,200/year.

Salesforce Platform Plus ($100/user/month list)

A middle tier between Platform and Enterprise. Adds some Sales Cloud and Service Cloud functionality — specifically read access to standard CRM objects. Good for users who need to view (but not manage) accounts, contacts, and opportunities while primarily working in a custom app.

Less commonly discussed than Platform or Enterprise, but worth evaluating for RevOps analysts, business operations users, and anyone doing CRM data QA.

Chatter Free ($0)

Chatter Free is a zero-cost license that gives users access to Chatter (Salesforce's internal collaboration layer), with read access to a limited set of Salesforce data. No objects, no records, no automation — just the feed.

Right fit for: Employees who need to be tagged in Salesforce discussions, receive deal updates via Chatter feed, or approve/review items without needing their own Salesforce license. Legal teams reviewing contracts, finance reviewing deal terms, marketing reviewing account notes.

Most orgs don't use Chatter Free at all, which means users who should be on it are getting full Enterprise licenses instead. If someone's only Salesforce activity is reading deal notes and clicking Approve, Chatter Free covers the job.

Identity ($5/user/month)

Salesforce Identity licenses are for users who only need Salesforce as an identity provider — SSO, MFA, and access to connected apps — without needing any Salesforce CRM or platform functionality.

Niche use case, but worth knowing: if you're using Salesforce Identity to SSO into other tools (not using Salesforce CRM at all), these users should be on Identity, not Platform or Enterprise.

Salesforce add-on licenses (Permission Set Licenses)

Beyond base user licenses, Salesforce sells Permission Set Licenses (PSLs) as add-ons that unlock specific feature sets on top of a base license. These are billed separately and are a major source of hidden waste.

PSLs must be assigned to specific users via the Permission Set License Assignment object in Salesforce. The waste pattern is consistent: PSLs get assigned during a feature rollout or a new product purchase, adoption doesn't materialize, and assignments are never reclaimed. Query PermissionSetLicenseAssign and cross-reference against LoginHistory — you'll find assignments to users who haven't used the feature in months.

External and community licenses

If any of your Salesforce users are customers, partners, or external stakeholders — not employees — they should almost never be on internal Salesforce licenses. Salesforce offers:

• Partner Community — for channel partners and resellers accessing a partner portal
• Customer Community — for external customers accessing a support or self-service portal
• Experience Cloud — the umbrella platform for all external-user portals

External users on internal licenses is a compliance and cost issue. It's more common than you'd expect — especially in orgs that gave a key partner or consultant a “temporary” internal login that became permanent.

Integration user licenses

Service accounts — the Salesforce users your middleware, ETL, and integration tools authenticate as — should use dedicated integration licenses or, at minimum, be on Platform licenses if they only need API access to custom objects.

What you don't want: integration users on full Enterprise licenses with interactive login capability. This is both a cost issue ($165/month for a user that never logs in) and a security issue (a compromised service account credential that can log in interactively has far more blast radius).

Salesforce offers a dedicated Integration User license type for API-only service accounts. It provides full API access at a fraction of the cost of Enterprise. If you have more than 3–4 integration accounts, this is worth auditing.

How to identify the right license for each user

The fastest way to assess this is to pull three things for each active user:

1. Their current license type — from User.Profile.UserLicense.Name
2. Their last 90 days of login activity — from LoginHistory
3. Which objects they actually accessed — from EventLogFile (API Access logs, if enabled) or from their Profile's object permissions

If a user is on Enterprise but their object access is limited to a few custom objects, Platform is probably right. If they're on Unlimited but they never use a sandbox, Enterprise is probably right. If they're on Enterprise and they only view reports, Chatter Free or a read-only external license might work.

This kind of analysis is straightforward to run — but it's tedious to do manually across hundreds of users, and it needs to be done before every renewal, not once and forgotten.

License type decisions are a renewal conversation, not a one-time setup

Salesforce orgs change. People change roles. New products get added. Integration patterns shift. A license mix that made sense 18 months ago may have 40 users on the wrong type today.

The goal isn't to minimize licenses at the expense of productivity — it's to make sure the license type matches the actual job. A rep who spends 4 hours/day in Salesforce needs Enterprise. A CFO who checks a dashboard once a week does not.

Running this analysis quarterly, documenting it, and bringing it to your AE at renewal — with specific downgrade candidates identified — is how you walk into the room with leverage instead of walking in and hoping for the best.