Licensing

Licensing is one of the most nuanced areas of CTA system architecture. The right license mix directly impacts cost, feature availability, and user experience. Getting it wrong means either overpaying (giving full CRM licenses to users who only need a portal) or under-licensing (blocking features that the architecture depends on).

License Categories Overview

Salesforce licenses fall into distinct categories, each with different cost structures and capabilities.

flowchart TD
    A[Salesforce Licenses] --> B[User Licenses]
    A --> C[Feature Licenses]
    A --> D[Permission Set Licenses]
    A --> E[Usage-Based Entitlements]

    B --> B1[Full CRM]
    B --> B2[Platform]
    B --> B3[Experience Cloud]
    B --> B4[Identity]
    B --> B5[Chatter]

    C --> C1[Marketing Cloud]
    C --> C2[Knowledge]
    C --> C3[Service Cloud Voice]

    D --> D1[Einstein Analytics]
    D --> D2[Shield]
    D --> D3[Industry-Specific]

    E --> E1[API Calls]
    E --> E2[Storage]
    E --> E3[Platform Events]
    E --> E4[Data Cloud Credits]

Full CRM Licenses

These are the core Salesforce licenses for internal users who need full CRM functionality.

Sales Cloud License

Feature	Included
Accounts, Contacts, Opportunities	Yes
Leads, Campaigns	Yes
Forecasting	Yes
Products, Price Books, Quotes	Yes
Territory Management	Yes
Einstein Activity Capture	Add-on or UE edition
Revenue Intelligence	Add-on
Sales Engagement (HVS)	Add-on

Service Cloud License

Feature	Included
Cases, Solutions	Yes
Knowledge (basic)	Yes
Entitlements, Milestones	Yes
Omni-Channel Routing	Yes
Service Console	Yes
Live Agent / Messaging	Add-on
Service Cloud Voice	Add-on
Field Service	Add-on
Einstein Bots	Add-on

Sales + Service (Combined) License

A combined license that includes both Sales and Service Cloud functionality. This is more cost-effective than purchasing both separately and is appropriate when users need both selling and case management capabilities.

When to recommend combined

If more than 30-40% of your user base needs both Sales and Service functionality, the combined license is almost always more cost-effective than buying separate licenses and managing which users get which. The administrative overhead of two license types often exceeds the cost savings.

Platform Licenses

Platform licenses provide access to custom applications built on the Salesforce platform without access to standard CRM objects (Opportunities, Cases, Campaigns, Forecasts, etc.).

Platform Starter (formerly Force.com App Subscription)

Capability	Limit
Custom apps	1
Custom objects per app	10
Custom tabs	10
Standard objects	Accounts, Contacts only
API access	Yes
Reports & Dashboards	Yes (on accessible objects)
Flows	Yes
Apex	Yes

Platform Plus (formerly Force.com One App)

Capability	Limit
Custom apps	Unlimited
Custom objects	110
Custom tabs	25
Standard objects	Accounts, Contacts only
API access	Yes
Reports & Dashboards	Yes
Flows	Yes
Apex	Yes

When to Use Platform Licenses

flowchart TD
    A[Does user need<br/>Opportunities, Cases,<br/>Campaigns, or Forecasts?] -->|Yes| B[Full CRM License Required]
    A -->|No| C{Does user need<br/>more than 1 custom app<br/>or 10 custom objects?}

    C -->|Yes| D[Platform Plus]
    C -->|No| E[Platform Starter]

    B --> F{Sales, Service,<br/>or Both?}
    F -->|Sales only| G[Sales Cloud]
    F -->|Service only| H[Service Cloud]
    F -->|Both| I[Sales + Service]

    style B fill:#9d0208,color:#fff
    style D fill:#2d6a4f,color:#fff
    style E fill:#2d6a4f,color:#fff
    style G fill:#457b9d,color:#fff
    style H fill:#457b9d,color:#fff
    style I fill:#457b9d,color:#fff

Platform license gotcha

Platform licenses provide access to Accounts and Contacts but not to Opportunities, Cases, Campaigns, or Forecasts. If your custom app uses any of these standard objects — even indirectly through lookups or automation — a Platform license will not work. Audit all object dependencies before recommending.

Experience Cloud Licenses

Experience Cloud (formerly Community) licenses are for external users — customers, partners, or other third parties who access Salesforce through a portal.

License Type Comparison

License	Access Level	Object Access	Sharing	Cost Tier	Best For
Customer Community	Basic self-service	Cases, Knowledge, limited custom objects	Limited (no roles)	Lowest	High-volume self-service portals
Customer Community Plus	Full customer portal	Full object access	Role-based hierarchy	Medium	Complex customer portals with sharing
Partner Community	Partner relationship management	Opportunities, Leads, custom objects	Role-based + partner sharing	Higher	Channel/partner management
External Apps	API + custom app access	Custom objects only	Limited	Per-login or per-member	Authenticated external apps
Channel Account	Lightweight partner access	Limited partner objects	Limited	Lower than Partner	Large partner networks with simple needs

Experience Cloud offers two pricing models:

Member-based: Fixed cost per named user per month. Best when users log in frequently (daily or weekly).

Login-based: Cost per login event. Best when users log in infrequently (monthly or less). A login counts as any 24-hour period in which the user accesses the community.

Scenario	Recommended Model
Customer support portal (daily usage)	Member-based
Annual renewal portal (once a year)	Login-based
Partner deal registration (weekly)	Member-based
Investor relations (quarterly)	Login-based
Patient portal (monthly visits)	Evaluate break-even point

Break-even calculation

Calculate the break-even point: if a member license costs $6/month and a login costs $1.50/login, the break-even is 4 logins/month. Below 4 logins, login-based is cheaper. Above 4, member-based wins. Always model expected usage patterns.

Customer Community vs Customer Community Plus

This is one of the most critical licensing decisions for portal architectures.

Capability	Customer Community	Customer Community Plus
Role hierarchy	No (all users share one role)	Yes (up to 3 levels)
Sharing rules	No	Yes
Delegated admin	Limited	Yes
Reports	Limited	Yes (with dashboards)
Flows (screen flows)	Yes	Yes
API access	No	Yes
Custom objects	10	Unlimited
Record visibility	Account-based only	Role + sharing-based

The key question: Does the portal need record-level visibility controls beyond simple account-based access? If yes, Customer Community Plus is required.

Identity Licenses

Identity licenses provide authentication and SSO capabilities without CRM data access.

Salesforce Identity License

Feature	Included
SSO (SAML, OIDC)	Yes
Social Sign-On	Yes
MFA	Yes
My Domain	Yes
Connected Apps	Yes
CRM data access	No
Custom objects	No
API access	Limited

External Identity License

For external users who only need authentication — no CRM access at all. Useful as the cheapest way to provide authenticated access to external apps via Salesforce as the Identity Provider (IdP).

When to use: You need Salesforce as an IdP for external users who will never access Salesforce data directly. Often combined with custom Heroku or third-party applications.

Chatter Licenses

Chatter Free

Free license for users who only need Chatter collaboration features.

Feature	Included
Chatter posts and comments	Yes
Groups	Yes
Files	Yes
People and profiles	Yes
CRM data	No
Reports	No
Custom objects	No

Chatter External

Free license for external users (customers, partners) who are invited to specific Chatter groups.

When to use: You want to collaborate with external stakeholders in Chatter without giving them any CRM or portal access. Good for project-based collaboration with vendors.

Edition Selection

Choosing between Enterprise, Unlimited, and Performance editions is an architectural decision. Use this visual to evaluate the key differentiators.

flowchart TD
    A["Edition Decision"] --> B{"Need Shield<br/>(encryption, audit,<br/>event monitoring)?"}

    B -->|"Yes, bundled"| C["Performance Edition"]
    B -->|"Yes, add-on OK"| D{"Need Premier<br/>Support included?"}
    B -->|"No"| D

    D -->|"Yes"| E{"Need 120 MB/user<br/>data storage?"}
    D -->|"No, add-on OK"| F{"Custom objects<br/>exceed 200?"}

    E -->|"Yes"| G["Unlimited Edition"]
    E -->|"No"| F

    F -->|"Yes"| G
    F -->|"No"| H{"100 dev sandboxes<br/>needed?"}

    H -->|"Yes"| G
    H -->|"No"| I["Enterprise Edition"]

    style C fill:#9d0208,color:#fff
    style G fill:#457b9d,color:#fff
    style I fill:#2d6a4f,color:#fff

Edition vs add-on math

Before recommending an edition upgrade, calculate whether buying the specific feature as an add-on is cheaper. Upgrading 500 users from Enterprise to Unlimited to get Shield might cost more than buying Shield as an add-on on Enterprise. Always model the numbers.

Einstein and AI Licenses

Einstein License Landscape

Product	What It Does	License Model
Einstein Activity Capture	Syncs email + calendar to Salesforce	Per-user add-on or UE edition
Einstein Lead Scoring	Predictive lead scoring	Included in some editions
Einstein Opportunity Scoring	Win probability prediction	Included in some editions
Einstein Discovery	Automated analytics + predictions	CRM Analytics Plus license
Einstein Bots	Conversational AI for Service	Service Cloud add-on
Einstein GPT / Copilot	Generative AI across clouds	Einstein 1 edition or add-on
Einstein Search	AI-powered search	Included in most editions

Einstein licensing complexity

Einstein licensing is one of the most confusing areas in Salesforce. Features are bundled differently across editions, and the landscape changes frequently. Always verify current bundling with Salesforce pricing documentation or your account executive.

Data Cloud Licenses

Data Cloud (formerly Customer Data Platform / Salesforce CDP) unifies customer data across systems.

Component	What It Provides
Data Cloud credits	Processing and storage units (consumption-based)
Data Cloud for Marketing	Customer segmentation for Marketing Cloud
Data Cloud for Service	Unified customer profile for agents
Data Cloud segments	Audience creation and activation
Identity resolution	Cross-system customer matching

Key architectural implication: Data Cloud is consumption-based (credits), not per-user. This changes the cost model from predictable monthly to usage-based, requiring capacity planning.

MuleSoft Licenses

Product	Purpose	License Model
MuleSoft Anypoint Platform	API management + integration	vCore-based (compute units)
MuleSoft Composer	Low-code integration	Per-user + flow-based
MuleSoft RPA	Robotic process automation	Per-bot

When MuleSoft is architecturally justified: Complex multi-system integration landscapes (5+ systems), need for API-led connectivity (experience, process, system API layers), or when the organization has a strategic API management initiative.

When MuleSoft is overkill: Simple point-to-point integrations between 2-3 systems, or when native Salesforce integration (Platform Events, Outbound Messages, Flow HTTP callouts) is sufficient.

Tableau Licenses

License Type	User Type	Capabilities
Tableau Creator	Analysts, data engineers	Full authoring, Prep, data connections
Tableau Explorer	Business users	Explore existing workbooks, create views
Tableau Viewer	Consumers	View and interact with published dashboards
Tableau Site	Server/Online deployment	Hosting and management

See Reporting & Analytics for when to use Tableau vs CRM Analytics vs standard reports.

Shield Licenses

Salesforce Shield is a set of security and compliance tools sold as an add-on (or included in Performance edition).

Component	What It Does
Platform Encryption	Encrypt data at rest (deterministic or probabilistic)
Event Monitoring	Login forensics, API usage tracking, data access auditing
Field Audit Trail	Retain field history beyond 18 months (up to 10 years)

Shield and architecture

Shield Platform Encryption affects search, filtering, and sorting on encrypted fields. This has direct architectural implications — you cannot use encrypted fields in WHERE clauses (deterministic encryption has limited filter support), SOQL aggregate functions, or formula fields. Plan your data model around encryption requirements.

Industry Cloud Licenses

Industry Cloud	Target Sector	Key Features
Health Cloud	Healthcare, Life Sciences	Patient management, care plans, clinical data model
Financial Services Cloud	Banking, Insurance, Wealth Management	Financial accounts, referrals, action plans
Manufacturing Cloud	Manufacturing	Sales agreements, account-based forecasting
Consumer Goods Cloud	CPG, Retail	Retail execution, trade management
Education Cloud	Higher Ed, K-12	Student lifecycle, recruitment, advising
Nonprofit Cloud	NGOs, Foundations	Fundraising, program management, outcomes
Net Zero Cloud	Sustainability	Carbon accounting, ESG reporting
Communications Cloud	Telco, Media	CPQ, order management, service orchestration
Automotive Cloud	Automotive	Vehicle management, dealer performance

Architectural consideration: Industry clouds come with pre-built data models, processes, and UIs. If the customer’s industry aligns, using the industry cloud eliminates significant custom development. However, heavily customized industry clouds can be harder to upgrade.

Feature Licenses vs Permission Set Licenses

Understanding the distinction is critical for CTA exam scenarios.

Feature Licenses

Assigned in user records. Enable specific features for individual users.

Examples: Marketing User, Knowledge User, Service Cloud User, Flow User.

Permission Set Licenses (PSLs)

Assigned through permission sets. More granular than feature licenses. Multiple PSLs can be assigned to a single user.

Examples: Einstein Analytics Plus, Sales Cloud Einstein, Identity Connect, CRM Analytics Plus.

Key difference: Feature licenses are all-or-nothing per user. Permission set licenses allow mixing and matching capabilities through permission sets, giving finer-grained cost control.

Cost Optimization Strategies

License Right-Sizing

Strategy	How to Apply
Audit actual usage	Run login history reports — inactive users cost money
Platform licenses for back-office	Warehouse, HR, or operations staff who need custom apps but not CRM
Community licenses for externals	Never give full CRM licenses to portal users
Chatter Free for collaboration-only	Executives who only use Chatter, not CRM
Login-based for infrequent users	Community users who log in less than monthly
Permission set licenses over edition upgrades	Add specific features via PSLs instead of upgrading the entire org edition

License Optimization Decision Process

flowchart TD
    A[New user needs access] --> B{What do they need?}

    B -->|Chatter only| C[Chatter Free - $0]
    B -->|Authentication only| D[Identity License]
    B -->|Custom app, no CRM objects| E{Complex app?}
    B -->|CRM data| F{Internal or External?}

    E -->|Simple, 1 app| G[Platform Starter]
    E -->|Complex, multiple apps| H[Platform Plus]

    F -->|Internal| I{Which cloud?}
    F -->|External| J{Access level?}

    I -->|Sales| K[Sales Cloud]
    I -->|Service| L[Service Cloud]
    I -->|Both| M[Sales + Service]

    J -->|Self-service only| N[Customer Community]
    J -->|Complex portal| O[Customer Community Plus]
    J -->|Partner| P[Partner Community]
    J -->|API/app only| Q[External Apps]

    style C fill:#2d6a4f,color:#fff
    style G fill:#2d6a4f,color:#fff
    style N fill:#2d6a4f,color:#fff

Common Anti-Patterns

Anti-Pattern	Problem	Fix
Full CRM for everyone	Massive over-spend	Audit and right-size to Platform where possible
Customer Community Plus for simple portals	Paying for sharing model nobody uses	Downgrade to Customer Community
Separate Sales + Service licenses when most users need both	Higher cost + admin overhead	Switch to combined licenses
Ignoring login-based pricing	Overpaying for infrequent external users	Model usage patterns and switch
Buying UE edition for one feature	Premium edition cost for a single capability	Evaluate if PSL or add-on is cheaper

Org Strategy — Edition and license choices constrain org strategy
Reporting & Analytics — Analytics licenses (CRM Analytics, Tableau) affect reporting strategy
Platform Capabilities — License type determines available governor limits and features
Trade-Offs — License optimization trade-off analysis
Security — Shield licensing for encryption and audit requirements

Sources

Salesforce Help: User Licenses
Salesforce Help: Feature Licenses
Salesforce Help: Permission Set Licenses
Salesforce Help: Experience Cloud Licenses
Salesforce Help: Platform Licenses
Salesforce Help: Salesforce Shield
Salesforce Help: Data Cloud Overview
Salesforce Pricing: Editions Comparison
Salesforce Architects: License Types Reference