Feature License
A Feature License in Salesforce is a per-user license that grants access to a specific feature beyond the user's base Salesforce license.
Definition
A Feature License in Salesforce is a per-user license that grants access to a specific feature beyond the user's base Salesforce license. Where a base license (Salesforce, Salesforce Platform, Customer Community) defines the overall product the user is authorized to use, a feature license adds discrete capabilities on top: Marketing User, Service Cloud User, Knowledge User, Sales Cloud User, Mobile User, Live Agent User, CRM Content User, and similar named features. Each feature license has a separate allocation count, and assigning one to a user consumes one unit from that allocation.
Feature licenses are visible on the User record as checkboxes (or a more complex feature-license related list, depending on the license type) and on the org's Company Information page as a list of all feature licenses with used and available counts. They sit between base licenses and permission sets in the Salesforce licensing model: a feature license unlocks the platform-level capability, and permission sets or profiles then grant the user-level permissions to use specific objects, fields, and Apex classes within that capability.
How Salesforce feature licenses work
The licensing hierarchy
Salesforce uses a three-tier licensing model. The base user license defines the overall product (Salesforce vs Platform vs Community). Feature licenses are add-ons that unlock specific capabilities. Permission sets are the fine-grained access controls within those capabilities. A user needs the right combination: the right base license to be a real Salesforce user, the right feature license to access a feature like Service Cloud, and the right permission set to use specific Service Cloud objects.
Common feature licenses and what they unlock
Marketing User unlocks Campaign access, marketing-specific dashboards, and email-blast capabilities. Service Cloud User unlocks Service Cloud objects (Case, Knowledge, Live Agent). Knowledge User unlocks the Knowledge object specifically. Mobile User (in older orgs) unlocked mobile access; this is now built into base licenses. Live Agent User unlocks chat session handling. Each license has its own purpose; assignment depends on the user's role.
Assignment and allocation
Feature licenses are assigned per user on the User detail page. The allocation count for each license is set when the org is provisioned and increases when the customer purchases additional units. Assigning one license to a user consumes one unit from the allocation; deactivating the user releases the unit. You cannot exceed the allocation; attempting to assign a license to one more user than allocated fails with an error.
Bulk assignment and migration
Bulk assignment is supported through Data Loader against the User object, setting the appropriate feature flag fields (UserPermissionsMarketingUser, UserPermissionsKnowledgeUser, etc.). This is the only practical way to assign feature licenses to hundreds of users at once. Plan the migration carefully because errors are per-row and a partial failure leaves the org in an inconsistent state.
Permission set licenses (the modern alternative)
For newer features, Salesforce has shifted from feature licenses to Permission Set Licenses. A Permission Set License grants the same capability but is assigned through permission sets rather than User record flags. The model is more flexible: permission sets are easier to bundle and assign through permission set groups. Newer features (CRM Analytics, Sales Engagement, certain industry clouds) use Permission Set Licenses; the older capabilities still use Feature Licenses.
Auditing feature license usage
Company Information page lists feature licenses with used/available counts. For more detail, query the User object: SELECT Count() FROM User WHERE UserPermissionsMarketingUser = true returns the number of users with the Marketing User license. Reports can be built against User to show consumption trends. Audit at least quarterly; many orgs accumulate licenses on inactive users and discover allocation shortfalls only when trying to provision a new user.
Reclaiming licenses from deactivated users
Deactivating a user releases all their feature licenses back to the org allocation. The reclamation is automatic and immediate. For frozen users (still active but locked out), the licenses are still consumed. Audit User records for frozen accounts and decide whether to deactivate them entirely to free up licenses. This is a common path to recovering licenses without buying more.
Assign and manage feature licenses
Assigning and managing feature licenses involves the User record for single assignments, Data Loader for bulk, and Company Information for monitoring. The steps below cover the full lifecycle.
- Check available allocation
Setup > Company Settings > Company Information. Scroll to Feature Licenses. Confirm the license has available units before assigning.
- Assign to individual user
Setup > Users > select the user > Edit. Check the feature license checkbox (Marketing User, Service Cloud User, etc.). Save.
- Bulk assign through Data Loader
Export current users, populate the relevant UserPermissions field (UserPermissionsMarketingUser = true), and update through Data Loader. Test with a small batch first.
- Verify the assignment
Reload the user record, confirm the checkbox is set. Or query: SELECT UserPermissionsMarketingUser FROM User WHERE Id = ... and confirm true.
- Add corresponding permission set
The feature license unlocks the capability; the permission set or profile grants access to specific objects, fields, and actions. Both are required for the user to actually use the feature.
- Monitor consumption
Build a report on User by feature license fields. Schedule weekly for the IT operations team. Catch shortfalls before they block new hires.
- Reclaim from deactivated users
Run a quarterly audit of inactive users with assigned licenses. Deactivate any user no longer at the company; their licenses return to the allocation automatically.
Unlocks Campaign access and marketing capabilities.
Unlocks Service Cloud objects: Case, Knowledge, Live Agent.
Unlocks the Knowledge object for editing and publishing articles.
Unlocks chat session handling for support agents.
Unlocks CRM Content (Libraries) features. Legacy feature; superseded by Salesforce Files.
- Feature licenses are distinct from Permission Set Licenses. Newer features use the permission set model; confirm which applies before troubleshooting.
- Freezing a user does not release their license. Only deactivation does. Frozen accounts are a common silent drain on allocation.
- Assignment fails per row when bulk loading. A partial failure leaves a mix of assigned and unassigned users; plan a rollback before starting.
- Feature license alone does not grant access. The user also needs the corresponding permission set or profile; assigning only the license produces unexpected access denial errors.
- Some feature licenses are bundled with the base user license (Mobile User in modern orgs). Assigning explicitly is redundant or even produces errors.
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. What is the primary benefit of Feature License for Salesforce administrators?
Q2. Why is understanding Feature License important for Salesforce admins?
Q3. In which area of Salesforce would you typically find Feature License?
Discussion
Loading discussion…