# Salesforce license types for a five-person sales team: which user license each person needs

https://salesbond.app/blog/salesforce-license-types-five-person-sales-team/
Published: 2026-10-21 · Updated: 2026-10-26

A Salesforce user license decides which features one person can use, and each user holds exactly one. For a five-person team of four reps and a manager, that means five full CRM user licenses. The admin is not a sixth seat: admin rights go on the manager’s existing user as a profile.

The rest of this piece is about the details that change the invoice: how a license differs from an edition and a permission set, which add-on layers sit on top, how to count what you hold, and the mistakes we see most on small teams.

The add-on layers have their own price math, including the [Agentforce add-on and the $5 user license](https://salesbond.app/blog/agentforce-for-sales-pricing-five-person-sales-team/).

## License, edition, permission set: three things people call “the license”

When a rep says “I need a license for that”, they can mean three different purchases, and only one of them is a license.

The user license is attached to a person. Salesforce’s own training puts it in one line: “A user license determines which features the user can access in Salesforce” ( [Trailhead: Add New Users](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_user_setup_mgmt/lex_implementation_user_setup_mgmt_adding_users-hoc)). The same unit adds that the license decides which profiles you can even pick for that user.

The edition is attached to the org. It sets the feature ceiling for everyone and, together with the number of licenses you bought, the head count: “The maximum number of users you can add is determined by your Salesforce edition and the number of user licenses you purchase” (same unit). The sales editions on sale today are Starter Suite, Pro Suite, Core, Advanced and Max ( [Salesforce Sales Cloud pricing](https://www.salesforce.com/sales/pricing/)). Which one a five-person team should pick is a separate question, and we keep it out of this article.

Profiles and permission sets live inside the license. Trailhead’s licensing module is blunt about the limit: a profile or a permission set is “a subset of the functionality defined in a user license or permission set license”, and neither can exceed it ( [Trailhead: Give Users the Functionality They Need](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/give-users-the-functionality-they-need)). So the order of questions is always the same. Edition first, then one user license per person, then the profile and permission sets on top. When a rep hits an [insufficient privileges error](https://salesbond.app/blog/salesforce-insufficient-privileges-manager-checklist/), start from that order and this manager checklist.

## The license types a sales team actually meets

For a sales team, the license types that matter are the full CRM user license, the narrower user licenses, and permission set licenses that sit on top of a user license. Everything else on Salesforce’s list belongs to other products.

Salesforce’s training calls the first one the Full CRM user license, “for users who need access to CRM functionality” ( [Trailhead: Understand How Licenses Work](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work)). If a person owns leads and opportunities, this is their license.

Then there are the narrower ones. Trailhead’s own example is Chatter Free, for someone who needs Chatter “without allowing them to see any data in Salesforce” (Add New Users unit). The one small teams ask about most is the Salesforce Platform license, usually because it is cheaper. Before you put anyone who works deals on it, read what it includes in Salesforce Help’s [Licenses Overview](https://help.salesforce.com/s/articleView?id=platform.users_licenses_overview.htm) and the pages it links to. We would not move a rep onto it to save money.

Permission set licenses are the layer that quietly multiplies the invoice. “While a user can have only one user license, the user can be assigned multiple permission set licenses”, and they exist to “augment the functionality provided by the assigned user license” (Understand How Licenses Work). They usually arrive with an add-on: buy one, and your org gets new user or permission set licenses that someone then has to assign to named people ( [Trailhead: Keep Up with Upgrades and Add-ons](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/keep-up-with-upgrades-and-addons)).

Our rule for small teams: the base license is a per-person decision and is almost always the full CRM one. The layers are per-feature decisions, and each one should be able to name the person who uses it.

## Who needs what: a five-person map

Four reps and one manager, and the manager also does the admin work. Here is how we would lay out the seats, and why there is no admin row with its own license.

| Person | User license | Profile | Layers on top |
| --- | --- | --- | --- |
| Rep 1, 2, 3, 4 | Full CRM | One sales profile for all four | Only the permission set licenses for features they personally use |
| Sales manager (also the admin) | Full CRM | Administrator profile on the same user | Same as reps; visibility comes from the role hierarchy and sharing, not from a different license |

![Seat map: four reps and a manager each hold one Salesforce license; admin is a profile on the manager, not a sixth seat](https://salesbond.app/wp-content/uploads/2026/10/salesforce-license-types-five-person-sales-team-2.png)

The reps are the easy part. Anyone who owns opportunities needs the full license and a profile that lets them create and edit the sales objects. Trailhead’s current advice is to start users on the Minimum Access – Salesforce profile and add what they need through permission sets and permission set groups (Add New Users unit). On four reps who all do the same job one shared sales profile is usually fine too; pick one approach and stick to it.

The manager needs the same base license as the reps. What makes a manager a manager in Salesforce is not the license but the role. “Users at the top of the hierarchy can see all the data owned by users below them” (Add New Users unit), and the reports built on top of that are what a manager actually opens; we described [what a manager opens weekly in Sales Cloud](https://salesbond.app/blog/salesforce-sales-cloud-manager-weekly-use/) separately. Roles are not available in every edition, according to the same unit, so check yours before planning on hierarchy-based visibility.

The admin is where most five-person budgets go wrong. In a team this size there is rarely a sixth human whose job is Salesforce. Admin is a set of rights you put on an existing user, and since “each user is assigned one user license” (Understand How Licenses Work), the manager with admin rights still holds one seat. The only time the admin costs a license is when an outside consultant or an ops person needs their own login. Then they are user number six, and that’s a line you budget consciously, not something you discover on the renewal.

What if your five are three reps, a manager and an ops person who does the admin? Then the ops person needs their own license too, and the count is still five. The rule doesn’t change: one person, one user license, admin rights on whoever does the job.

## How many Salesforce licenses do I have, and who is not using theirs

Every license type in your org is a UserLicense record with two numbers on it, `TotalLicenses` and `UsedLicenses`, plus a `UsedLicensesLastUpdated` timestamp ( [Salesforce Field Reference: UserLicense](https://developer.salesforce.com/docs/platform/field-reference/references/field-reference/salesforce-field-reference-userlicense.html)). That timestamp is the useful part. The used count is a snapshot, not a live number, so if you deactivated someone this morning and the count did not move, look at when it was last updated before you open a ticket. Your admin can pull all three with a one-line query on UserLicense.

For the per-person view, open Setup, type Users in the Quick Find box and select Users (Add New Users unit). On five people you can go through it by eye in two minutes. Write the list down anyway, because it is also the list you will send to finance at renewal.

“Used” does not mean “working”. A seat is used the moment an active user holds it, whether or not that person has touched an opportunity this quarter. The honest check is to put the user list next to the opportunity list: who owns open opportunities, who has updated one recently, who has done neither. The person who has done neither is either a license to free up or a rep to talk to, and both are worth knowing. We walked through the opportunity side of that check in [the opportunity audit for a sales manager](https://salesbond.app/blog/salesforce-opportunity-audit-sales-manager/).

A disclosure, since this is the exact list we look at: we build SalesBond, a sales management layer on top of the CRM a team already uses, Salesforce included. Its Team Performance tab shows a manager per-rep execution, which is the other half of a license audit. The license count tells you how many seats you pay for. That view tells you who is earning theirs. [Check your CRM with SalesBond](https://salesbond.app/) if you want it without building the reports.

## Where small teams pay twice

Paying for an admin seat nobody logs into is the first one, and we covered it above. The second is subtler, and it is about leavers.

### Freeze vs deactivate

When a rep leaves, the reflex is to freeze the user. Freezing stops the login, but Salesforce’s training is explicit that “freezing user accounts doesn’t make their user licenses available in your organization” ( [Trailhead: Add New Users](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_user_setup_mgmt/lex_implementation_user_setup_mgmt_adding_users-hoc)). Deactivating does, and it is the permanent option, since “You can deactivate users, but you can’t delete them” (same unit). Freeze is the right first move when you need the person out in the next minute, say a compromised account, or when you have cleanup to do first. It is the wrong final state. Reassign thier records and deactivate, otherwise the opportunities sit with an inactive owner and nobody works them; we have a separate piece on [finding records that nobody owns](https://salesbond.app/blog/salesforce-queues-unowned-records-audit/).

### The other three

The wrong base license. Someone gets a narrower license because “they only need the dashboard”, and a month later they need to log a call on an opportunity. Now you are buying the full license anyway and have spent a month on workarounds.

A permission set license bought for the whole team when one person uses the feature. These are assigned per user, so the question at purchase time is not “does the team want this” but “which named user will have it assigned next week”. If the answer is one name, buy one.

Shared logins. One license is one user, and the moment two people share it every ownership report, every activity count and every forecast roll-up stops describing a person. The money you save is less than the the management you lose.

## When to change the edition instead of buying more licenses

Buying a sixth license and moving to a higher edition solve different problems, and the symptom tells you which one you have. If the sixth person needs to do what the other five already do, that is a license: add one, assign the profile, done. If the request is for a feature nobody in the team has, for example a forecasting or territory capability the current edition does not carry, no number of extra licenses will supply it, because the edition sets the ceiling for everyone, as the Trailhead quote above says. The fix there is a different edition for the whole org, and Trailhead’s licensing module notes that an upgrade brings new licenses an admin then has to assign and new permissions to grant (Keep Up with Upgrades and Add-ons). That is the point where the “which edition for five people” question belongs, and it deserves its own comparison rather than a paragraph here. The practical test we use is to write down the one thing the team cannot do today. If a single existing user could do it after a permission set and a permission set license, its a layer. If nobody in the org can do it at any permission level, it is the edition. If it is a sixth person, it is a seat.

## FAQ

**What does a Salesforce license cost?**
 Salesforce prices its sales editions per user per month, and the number depends on the edition you are on; the current per-user prices for Starter Suite, Pro Suite, Core, Advanced and Max are on [Salesforce’s pricing page](https://www.salesforce.com/sales/pricing/). Add-ons and the permission set licenses that come with them are priced on top.

**How many Salesforce licenses do I have?**
 Each license type in your org carries a total and a used count ( `TotalLicenses` and `UsedLicenses` on the [UserLicense object](https://developer.salesforce.com/docs/platform/field-reference/references/field-reference/salesforce-field-reference-userlicense.html)), and your admin can query both. The used count is refreshed on a schedule, so check `UsedLicensesLastUpdated` before you trust a change you made today.

**Does the admin need a separate license?**
 Only if the admin is a separate person. Each user holds one user license ( [Trailhead: Understand How Licenses Work](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work)), and admin rights go on that user’s profile. On a team of four reps and a manager who also does the admin, that’s five licenses, not six.

**Can a rep get by on a Salesforce Platform license?**
 We would not plan on it. A rep needs the sales objects the full CRM license is built for, and moving someone back after a month of workarounds costs more than the saving. If you are tempted, read what the Platform license includes in Salesforce Help’s [Licenses Overview](https://help.salesforce.com/s/articleView?id=platform.users_licenses_overview.htm) first.