A Salesforce Platform license is enough when a user needs custom apps, accounts, contacts, reports, and dashboards — but does not need the core CRM objects: Leads, Opportunities, Campaigns, and Forecasts. If a person's job lives in a custom app, an AppExchange app, or back-office data entry, the cheaper license usually covers them. If they sell, work a pipeline, or manage campaigns, they need the full Salesforce license. The savings are real, but so is the risk: assigning Platform licenses to users who touch Opportunities breaks their workflow mid-quarter. Vantage Point's Salesforce consultants run license-fit audits that map roles to licenses before renewal, not after.
Salesforce's own documentation draws the line cleanly. The Salesforce user license is designed for users who require full access to standard CRM functionality and AppExchange apps — the entire sales and service toolkit. The Salesforce Platform license is designed for users who need access to custom apps but not standard CRM functionality.
What Platform users keep: accounts, contacts, reports, dashboards, documents, custom tabs, custom objects, custom apps built in your org or installed from AppExchange, and core platform automation like Flow.
What Platform users lose: the standard objects and apps that define CRM — Leads, Opportunities, Campaigns, and Forecasts are the big four. A Platform-licensed user who opens an Opportunity simply cannot.
That single boundary drives every licensing decision. Everything else — profiles, permission sets, sharing — operates within whichever side of the line the license puts the user on.
The Platform license earns its discount when the user's daily work lives outside core CRM objects. Good fits typically include:
The bad fits are just as clear: anyone who owns or works Opportunities, runs lead conversion, manages Campaigns, or relies on Forecasts. A field-sales rep, an SDR working leads, or a marketer building campaign influence reports all need the full license.
Salesforce sells a few flavors, and the differences matter at procurement time:
| License | Access | Best for |
|---|---|---|
| Salesforce (full) | All standard CRM objects, custom apps, AppExchange | Sales, service, and marketing users |
| Salesforce Platform | Custom apps; accounts, contacts, reports, dashboards; no Leads/Opportunities/Campaigns/Forecasts | Custom-app and back-office users at a fixed per-user price |
| Salesforce Platform Login | Same access as Platform, priced by logins instead of seats; a login is consumed once per day per user | Occasional users whose usage is genuinely sporadic |
| Lightning Platform – One App (legacy) | One custom app (up to 10 custom objects), read-only accounts and contacts | Very narrow single-app use cases; largely superseded |
| Salesforce Integration | API-only access, no UI | System-to-system integration users, not humans |
Two practical notes from Salesforce's documentation. First, licenses arrive packaged in SKUs, and the name on your contract may differ from the license name you see in Setup > Company Information — confirm the underlying license, not just the SKU label. Second, the Platform Login variant is genuinely usage-based: users consume one login per day no matter how many times they sign in that day, and usage can be tracked through login history and Salesforce's Digital Wallet tooling.
Work from the role, not the org chart. A disciplined mapping process:
The failure mode is never subtle, but it is always badly timed. A Platform-licensed user who suddenly needs Opportunities — a territory change, a promotion, a new cross-functional project — hits a wall mid-task. Downgrades mid-contract are harder than upgrades, so teams that over-buy Platform seats to save money can end up buying full licenses on top while the Platform seats sit idle.
The opposite waste is quieter: full Salesforce licenses assigned to people who have never opened an Opportunity in two years. License audits regularly find a meaningful share of seats misassigned in both directions — which is why license right-sizing pairs naturally with a broader license utilization review, and why the savings from consolidation can be substantial, as one license-consolidation case study shows.
Vantage Point's Salesforce team runs license-fit audits that map roles to object usage, model Platform and Platform Login economics against real login history, and sequence conversions so nobody loses access mid-quarter. For organizations that want licenses governed continuously, our managed services and ongoing support fold license reviews into every renewal cycle. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver.
Vantage Point can audit your license assignments against actual usage and build a right-sizing plan for your next renewal. Talk to Vantage Point about a Salesforce license audit.
Custom apps (built in your org or installed from AppExchange), custom objects and tabs, accounts, contacts, reports, dashboards, documents, and platform automation such as Flow. They cannot access the core CRM objects: Leads, Opportunities, Campaigns, and Forecasts.
No. The Opportunity object is outside the Platform license's entitlement, and no profile or permission set can grant it — object access cannot exceed what the user license allows. A user who needs Opportunities needs a full Salesforce license.
A login-based variant with the same access as the Salesforce Platform license, priced per login rather than per seat. Users consume one login per day regardless of how many times they sign in that day, making it economical for genuinely occasional users.
Often, but not always. Apps built on custom objects generally work; apps that extend Leads, Opportunities, or Campaigns require the full license. Confirm each app's licensing requirements in its listing or with the vendor before converting users.
Yes — mixing is the normal pattern. Full licenses for CRM-facing roles, Platform licenses for custom-app and back-office users. The mix should be reviewed at every renewal because roles drift over time.
It is safe only after verifying the user touches no restricted objects. Check their reports, list views, owned records, and workflow dependencies on Leads, Opportunities, and Campaigns first — and reassign anything they own on those objects before switching the license.