User License
A User License is the base license assigned to every Salesforce user that sets the foundational level of access they can ever have.
Definition
A User License is the base license assigned to every Salesforce user that sets the foundational level of access they can ever have. It decides which standard objects, custom apps, and platform features the login can reach. Salesforce, Salesforce Platform, Chatter Free, and the Experience Cloud licenses such as Customer Community and Partner Community are all User License types.
Each user holds exactly one User License, chosen when the user record is created. Permission Set Licenses, Feature Licenses, and Permission Sets layer on top to grant capabilities within that license, but none of them can reach past the ceiling the User License defines.
How User Licenses shape every user's access
The three-layer access model
Salesforce builds user access from three license layers, and the User License is the bottom one. First comes the User License, which gives a baseline level of access and decides the kind of login a person has. Salesforce documentation is direct about this: every user requires a user license to access Salesforce, and each user can hold only one. Second come Permission Set Licenses and Feature Licenses. These entitle a user to features not included in the assigned User License, such as Service Cloud, Sales Engagement, or Salesforce Knowledge. A user can be assigned any number of them. Third come Permission Sets and Profiles, which grant the actual object, field, and feature permissions a user works with day to day. The order matters because each layer only operates inside the boundary of the one beneath it. A Permission Set can switch on a permission, but only if the User License already includes the feature that permission controls. Understanding this stack is the difference between an access request you can fulfill in minutes and one that needs a new license purchase.
Standard licenses: Salesforce and Salesforce Platform
The two standard internal User Licenses are Salesforce and Salesforce Platform, and the gap between them is the one admins hit most often. The Salesforce license gives full access to standard CRM objects and AppExchange apps. A user with this license can work with Leads, Opportunities, Cases, Forecasts, Campaigns, and any custom app. The Salesforce Platform license is for internal users who need custom apps but not the full CRM. It includes core objects like Accounts, Contacts, Reports, Documents, and custom objects, plus apps you build or install. What it deliberately leaves out is the heavy CRM set: Leads, Opportunities, Forecasts, and Campaigns are not available, regardless of permissions assigned. There is also a Salesforce Platform Login license, which offers the same features as the seat-based Platform license but with usage-based pricing measured in logins rather than a fixed seat per user. Picking the right one is a cost decision as much as a functional one. Putting an internal-app-only user on a full Salesforce license wastes money, while putting a sales rep on Platform blocks the pipeline they need.
External users and Experience Cloud licenses
When the people logging in are customers or partners rather than employees, you reach for Experience Cloud (Community) User Licenses. These are sized and priced differently because external user counts run much larger than internal headcount. Customer Community is the lightest, built for high-volume business-to-consumer scenarios like a self-service help center where users read Knowledge articles and view their own Cases. Customer Community Plus adds access to reports and dashboards plus standard role-based sharing, which suits external users who need a richer, more record-driven experience. Partner Community targets business-to-business relationships and opens up sales data such as Leads, Opportunities, and Campaigns for channel and partner relationship management. Around these sit more specialized options: External Identity for identity services like single sign-on and self-registration, External Apps for custom external experiences with limited CRM access, and Channel Account, which pools licensing by partner rather than counting individual users. Each external license carries its own object access ceiling and its own data-volume model, so the choice ties directly to what the external audience does and how many of them there are.
Why the User License is a hard ceiling
The single most useful thing to internalize about a User License is that it is a ceiling, not a suggestion. A Permission Set cannot grant access to an object the User License does not include. If you assign a Salesforce Platform user a Permission Set that references Opportunity, the Opportunity access simply does not take effect, because the license has no Opportunity entitlement to switch on. This trips up admins who assume permissions are the only gate. When a user reports they cannot see a tab or object that the permission audit says they should have, the User License is the first thing to check. The same ceiling applies to Permission Set Licenses. A Sales Engagement Permission Set License can only be assigned to users whose underlying User License supports it. This design keeps licensing honest. It means an org cannot quietly grant CRM-grade access to a pool of cheaper Platform or Community seats through clever permission stacking. For an architect, it also means license selection is a genuine design decision made early, not a setting you casually flip later.
Tracking entitlement and avoiding the cap
User Licenses are sold in fixed counts per type, and Salesforce enforces those counts. Run out of a given license and you cannot activate another user of that type until you buy more or free one up by deactivating someone. That makes monitoring a real operational task, not a nice-to-have. You view your org's licenses on the Company Information page in Setup, where each User License type shows its total purchased count alongside how many are currently used. The Lightning Usage App adds an Active Licenses view that tracks active user licenses, permission set licenses, and feature licenses over time, which is handy for spotting a trend before it becomes a blocker. The practical risk is a Monday-morning onboarding that stalls because the last Salesforce seat went out the previous week. Mature teams watch utilization against headcount plans and start a true-up conversation with their account team well before the count hits zero. Deactivating departed users promptly also recovers seats, since a deactivated user no longer consumes its license.
Changing a license and the User object link
Under the hood, the User record stores the assignment through its license-related fields, and the UserLicense object in the platform represents each license type your org owns. Because the User License is foundational, changing it on an existing active user is constrained and sometimes not possible in place. Some transitions, such as moving a user from Chatter Free to Salesforce, are supported directly. Others, especially shifts between very different license families, are blocked, and the standard path becomes deactivating the user and creating a new one on the correct license. That recreation is not free. A brand-new user is a new record, so historical ownership, activity history tied to the old user, and personal settings do not automatically follow. This is exactly why license selection deserves thought at creation time. Getting it right up front avoids the disruptive rework of swapping a license later. When a role genuinely changes (a Platform user moves into a full sales role, for example), plan the switch as a small migration: confirm the target license has free seats, document record reassignment, and schedule it rather than doing it ad hoc.
How to assign a User License when creating a user
You do not create a User License directly; you select one when you create the user record. The license you choose at this step sets that user's access ceiling, so confirm the role first. Create a user in Setup under Users.
- Open the New User screen
In Setup, go to Users then Users, and click New User. For several people at once, use Add Multiple Users instead.
- Enter identity details
Fill in the name, alias, email, and username. The username must be unique across all Salesforce orgs and is formatted like an email address.
- Choose the User License
Pick the User License that matches the role, for example Salesforce for a full CRM user or Salesforce Platform for an internal-app-only user. This selection filters which Profiles you can pick next.
- Select a Profile and save
Choose a Profile compatible with that license, set role and other options, then save. Salesforce sends the activation email so the user can set a password.
The base license that sets the user's access ceiling; it controls which Profiles and features are available.
The Profile must be compatible with the chosen User License; the picklist filters to matching Profiles only.
A globally unique login in email format, required for every user record.
A valid address that receives the activation message and system notifications.
- The User License you pick limits the Profiles you can select; a Profile built for Salesforce will not appear for a Platform user.
- You cannot save a user if no seats of the chosen license type remain; check the count on Company Information first.
- Switching a user's License later is restricted and often requires deactivation and recreation, which breaks record ownership and history.
Trust & references
Cross-checked against the following references.
- Understand License TypesSalesforce
- Standard User LicensesSalesforce
Straight from the source - Salesforce's reference material on User License.
- Licenses OverviewSalesforce
- Experience Cloud User LicensesSalesforce
Hands-on resources to go deeper on User License.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. In which area of Salesforce would you typically find User License?
Q2. Why is understanding User License important for Salesforce admins?
Q3. What is the primary benefit of User License for Salesforce administrators?
Discussion
Loading discussion…