Salesforce · Integrations · Licensing

Salesforce Integration User Licenses: How to Use Your Five Free API-Only Users

Every Enterprise, Unlimited and Performance Edition org includes five Salesforce Integration user licenses. They let each system that talks to Salesforce run as its own API-only user, without using up a full licence. Here is what the licence includes, how to set up an integration user, how it should authenticate after the Spring ’26 changes, and where it does not fit.

Key Takeaways

  • The Salesforce Integration user license is a user licence for system-to-system integrations. Users on it can work only through the API and can never log in to the Salesforce interface.
  • Enterprise, Unlimited and Performance Edition orgs include five of these licences, and Developer Edition orgs include one. You can buy more through your Salesforce account executive.
  • The licence comes with the Minimum Access - API Only Integrations profile and the Salesforce API Integration permission set license. Data access is granted through permission sets you build for each integration.
  • Since Spring ’26, new connected apps cannot be created by default. New REST integrations should use an external client app with the OAuth 2.0 client credentials flow, running as the integration user.
  • A dedicated user per integration gives you least privilege and clean audit trails. It does not give an integration its own API allowance: API limits are shared by the whole org.

What is the Salesforce Integration user license? It is a Salesforce user licence designed for system-to-system integrations. A user assigned to it can reach Salesforce data and features only through the API, never through any user interface. Supported editions include a small number at no extra cost, so each external system, such as an ERP, a marketing platform or a middleware tool, can connect as its own tightly scoped user.

We first wrote about these licences in 2023, when Salesforce introduced them. This version is rebuilt from Salesforce’s current Help documentation, developer guidance and Spring ’26 release notes, checked in October 2026. It corrects what our first post got wrong (these are not vendor trials, and they do not depend on company size or industry), and adds the setup steps, the authentication changes and the mistakes we see most often. It is written for Salesforce admins, architects and RevOps leaders at growing and mid-market companies who run several integrations and want them secure, traceable and off their full user licences.

Section 01 · Definition

What Does the Salesforce Integration User License Include?

Three pieces that work together: the user licence itself, a locked API-only profile, and a permission set license that unlocks the permissions an integration may need. The licence restricts the user to the API. The profile enforces that restriction and cannot be changed to allow interface access. The permission set license lets you grant object and user permissions through permission sets, one integration at a time.

ComponentWhat it doesWhat you control
Salesforce Integration (user licence)Grants access to Salesforce data and features only through the API. It cannot be used by people who need any user interface.Which integration user holds each licence
Minimum Access - API Only Integrations (profile)Enables API access and restricts the user to the API. These two settings cannot be turned off, including on clones of the profile.Defaults such as record types, page layout assignments, login hours and IP ranges
Salesforce API Integration (permission set license)Entitles the user to many of the user and object permissions found on the System Administrator profile. It entitles; it does not grant.The permission sets and permission set groups you build and assign, scoped to each integration

Salesforce explains the model in Give Integration Users API Only Access. Its licences overview puts the wider rule simply: permissions are locks and licences are rings of keys. Every user holds exactly one user licence, and permission set licenses add keys on top. Here, the permission set license adds the keys, and your permission sets decide which locks the integration may open.

One naming detail matters if your org is older. Before the Spring ’24 release the licence came with a profile called Salesforce API Only System Integrations. Salesforce’s developer team reported a known issue with it, which incorrectly gave CRUD permissions on custom objects, and replaced it with Minimum Access - API Only Integrations. The old profile is deprecated and remains only in orgs provisioned before Spring ’24. Salesforce recommends moving integration users to the new one.

Section 02 · Editions

How Many Free Integration User Licenses Does Salesforce Include?

Five in each Enterprise, Unlimited and Performance Edition org, and one in each Developer Edition org. Salesforce provisions them automatically with the edition: there is nothing to apply for and no form to fill in. Other editions are not listed as supported. If you need more than the included licences, Salesforce Help directs you to your account executive to buy add-on licences.

Salesforce editionIntegration user licenses includedWhat to do
Enterprise5Move your most important integrations first; buy more if you run more than five.
Unlimited5Same as Enterprise.
Performance5Same as Enterprise.
Developer1Enough to build and test one integration pattern.
Other editionsNot listedNot among the supported editions. Check with Salesforce before you plan around it.

Counts come from Salesforce’s user licences reference. To see what your org has, open Setup, search for Company Information, and look for Salesforce Integration under User Licenses and Salesforce API Integration under Permission Set Licenses. The Active Licenses tab in the Lightning Usage App tracks usage over time. Salesforce does not publish an add-on price in Help, so get a quote from your account executive rather than relying on figures quoted elsewhere.

Section 03 · Why It Matters

Why Should Every Salesforce Integration Have Its Own User?

Because a dedicated user limits what each integration can reach, shows exactly which system changed which record, and contains the damage if one set of credentials leaks. Salesforce recommends one user for every integration, following the principle of least privilege. The Integration user license makes that affordable, because the user no longer needs a full Salesforce licence.

Least privilege

Each integration gets a permission set with only the objects, fields and operations it needs. An ERP sync never sees service cases it has no reason to read.

Traceability

Created By and Last Modified By show the system, not a person. Login history and audit questions get a precise answer, one integration at a time.

Smaller blast radius

If one system is compromised, you rotate one secret and deactivate one user. Every other integration keeps running.

Full licences back for people

An integration that sits on a full Salesforce licence today can move to an included Integration licence, freeing the full one for a person who needs the interface.

One expectation to correct early: a dedicated user does not give an integration its own API capacity. Salesforce’s API request limits are enforced against all API calls made to the org in a 24-hour period, not per user. Separate users do help with per-user limits, though. Salesforce’s integration patterns guide notes that a user can hold only 10 open query cursors at a time, and suggests each application use a designated integration user rather than sharing credentials.

Section 04 · Setup

How Do You Set Up a Salesforce Integration User Step by Step?

Create the user on the Salesforce Integration licence and the Minimum Access - API Only Integrations profile, assign the Salesforce API Integration permission set license, then grant access through a permission set built for that one integration. Finally, connect the external system with the right authentication method and test everything in a sandbox before production.

1. Confirm your licences.
→ Setup › Company Information. Check that Salesforce Integration appears under User Licenses and Salesforce API Integration under Permission Set Licenses, with enough unused of each.
2. List what the integration actually does.
→ Write down every object it reads, creates, updates or deletes, the fields involved, and whether it uses REST, SOAP or Bulk API. This list becomes the permission set.
3. Create the user.
→ Setup › Users › New User. Choose the Salesforce Integration user licence and the Minimum Access - API Only Integrations profile. Name it after the system, for example “ERP Integration”, and use an email address your team monitors, not a personal one.
4. Assign the permission set license.
→ On the user record, add the Salesforce API Integration permission set license. On its own it grants nothing; it makes the permissions available to assign.
5. Build a permission set for this integration only.
→ Create a permission set with the license set to Salesforce API Integration. Enable only the object, field and user permissions from step 2, then assign it to the integration user (or use a permission set group).
6. Connect the external system.
→ For REST, create an external client app, enable the OAuth 2.0 client credentials flow and set the integration user as the run-as user. For SOAP and Bulk API, use the SOAP login() call. Section 05 covers the choice.
7. Test, then record an owner.
→ Prove every operation in a sandbox, including failures from missing access. In production, note who owns the integration, where its secret is stored and when it was last rotated.

The steps follow Salesforce’s own walkthrough, Invoke REST APIs with the Salesforce Integration User and OAuth Client Credentials, which uses an ERP integration as its example. Keep the profile for defaults, record types, page layouts, login hours and IP ranges only, and manage every other permission in permission sets. Users on the profile can also see objects that are accessible to all users, so review those before go-live. If permission sets are new to your team, our guide to Salesforce profiles and permission sets explains the model.

Section 05 · Authentication

How Should a Salesforce Integration User Authenticate in 2026?

For REST integrations, through an external client app using the OAuth 2.0 client credentials flow, with the integration user as the run-as user. For SOAP-based APIs, including Bulk API, through the SOAP login() call. Since Spring ’26, Salesforce has disabled the creation of new connected apps by default, so new integrations should start on external client apps.

MethodUse it whenStatus in 2026
External client app + client credentials flowA headless server-to-server integration that always runs as the same integration user, on a system that can keep a secret safeRecommended
SOAP login() callThe integration uses a SOAP-based API, including Bulk APISupported
Existing connected appAn integration already running on a connected app you created before Spring ’26Keeps working plan migration
New connected appOnly when a specific need rules out external client appsOff by default needs Salesforce Support
Username-password flowLegacy integrations onlyAvoid not available on external client apps

The Spring ’26 release note confirms that existing connected apps continue to work and that packaged connected apps installed in a new org are unaffected. It recommends external client apps for all new integrations and migrating existing connected apps to them. Salesforce’s architect highlights add a practical warning: CI/CD pipelines that create connected apps through the Metadata API will now fail. The feature comparison confirms the username-password flow will not be offered for external client apps, and notes that local external client apps are not copied to a sandbox when you create or refresh it.

Securing the client credentials flow

  • Treat the consumer key and secret like a password. Anyone who holds them can get an access token as your integration user. Salesforce advises changing the secret periodically, and immediately if it may be exposed.
  • One app per integration, one user per app. Pre-authorise only the integration user, so rotating one secret affects one integration.
  • Use your My Domain URL. The flow does not support login.salesforce.com or test.salesforce.com, and it issues no refresh token: the client requests a new access token when the old one expires.
  • Pass secrets in the request body or header, never in a URL query string.

Details are in Salesforce’s client credentials flow documentation and the external client apps overview.

Section 06 · Fit

When Does the Integration User License Fit, and When Doesn't It?

It fits any integration that only ever talks to Salesforce through the API. It does not fit anything that needs a person, or a tool, to use the Salesforce interface. Most server-to-server work qualifies. The exceptions are usually third-party apps whose setup expects a full Salesforce user, and integrations that need permissions the API Integration permission set license does not cover.

Good fit. ERP, finance and billing syncs; data warehouse and analytics loads; middleware jobs built on platforms such as MuleSoft, Workato or Celigo that connect with their own credentials; custom apps that call the REST, SOAP or Bulk APIs on a schedule or on an event.

Poor fit. Anyone who must log in to Salesforce, even occasionally to check data; apps whose vendor documentation asks for a full Salesforce licence or an administrator login; and integrations needing permissions outside the API Integration permission set license. Check the vendor’s documentation before you move a packaged app’s user.

To see exactly which permissions you can grant, open Setup › Company Information, select the Salesforce API Integration permission set license and review its list. If an integration needs something that is not there, it needs a different licence, and that is worth knowing before cut-over rather than after.

Section 07 · Migration

How Do You Move Existing Integrations onto Integration Users?

Inventory first, then move one integration at a time: build its user and permission set in a sandbox, switch its credentials, watch it run, and only then free the old full licence. Start with the integrations that hold the most access today, often ones still running as an administrator or as an employee who has since changed roles.

PhaseWorkDone when
1. InventoryList every integration, the user it runs as, its licence, its connected or external client app, and the APIs it callsEvery API user has a named owner and purpose
2. PrioritiseRank by risk: shared users, admin-level access, personal logins, legacy profile, username-password flowThe first five candidates are agreed
3. Build in a sandboxIntegration user, permission set, external client app; run the integration’s full test cycleNo insufficient-access errors on real scenarios
4. Cut overSwitch the external system’s credentials or run-as user in production during a quiet windowA full business cycle runs without errors
5. Reclaim and monitorDeactivate the old user, release its full licence, set a secret rotation date and review access quarterlyLicence count and audit trail are clean

Salesforce’s architects recommend the same inventory for existing connected apps ahead of the move to external client apps, so it is efficient to do both together. Created By and Last Modified By will show the new user from cut-over onwards, so tell report owners in advance if any report filters on Created By or Last Modified By. If you would rather have the inventory done for you, our Salesforce health check covers integration users, permissions and connected apps.

Section 08 · Pitfalls

What Mistakes Should You Avoid with Integration User Licenses?

The most common mistake is moving the integration to the new licence but keeping its old, broad access. The licence only delivers its security benefit when each user’s permission set matches what its integration does. The other mistakes below come from treating the licence as something it is not.

One integration user shared by several systems. You lose traceability and least privilege, and one leaked secret exposes every system. Five included licences cover five integrations; buy more rather than share.
Granting everything the permission set license allows. It entitles the user to many System Administrator-level permissions. Enabling them all recreates an admin account that happens to be API-only.
Staying on the legacy profile. Orgs provisioned before Spring ’24 may still use Salesforce API Only System Integrations, which had the custom-object CRUD issue. Move users to Minimum Access - API Only Integrations.
Expecting extra API capacity. API limits are pooled across the org. A new user changes who makes the calls, not how many the org may make.
Building new integrations on connected apps or the username-password flow. New connected apps are off by default since Spring ’26, and external client apps do not offer the username-password flow. Start on the current pattern.
Treating the licences as a trial. They are user licences provisioned with your edition, not a promotional offer from an integration vendor. Plan them into your licence model like any other user type.
Section 09 · Bottom Line

The Bottom Line

The five included Salesforce Integration user licenses are one of the simplest security improvements an Enterprise or Unlimited org can make. Used well, every integration runs as its own API-only user, with exactly the access it needs and a clear audit trail. Twopir Consulting designs and delivers Salesforce integration services, from integration user and permission design to MuleSoft and Celigo builds and ongoing support. We implement, rescue, optimize, and integrate complex CRM and revenue systems.

  1. 1

    Check Company Information for your Salesforce Integration and API Integration licences.

  2. 2

    Give every integration its own user on the Minimum Access - API Only Integrations profile.

  3. 3

    Grant access through one permission set per integration, never the full entitlement.

  4. 4

    Connect new REST integrations with an external client app and the client credentials flow.

  5. 5

    Inventory existing integrations, move them one at a time, and free the full licences.

Ready to Start

Put Every Integration on Its Own Secure User

Tell us which systems connect to your Salesforce org today. We will map each one to an integration user, a permission set and an authentication method, and plan the move without breaking a sync.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

A limited number are included at no extra cost. Each Enterprise, Unlimited and Performance Edition org gets five Salesforce Integration user licenses, and each Developer Edition org gets one. They are provisioned automatically with the edition. Additional licences are paid add-ons, bought through your Salesforce account executive.

No. The licence grants access to Salesforce data and features only through the API, and its Minimum Access - API Only Integrations profile restricts the user to API access. That restriction cannot be turned off, even on a cloned profile. Anyone who needs to use Salesforce screens needs a different user licence.

Use the Minimum Access - API Only Integrations profile and the Salesforce API Integration permission set license. The profile replaced the deprecated Salesforce API Only System Integrations profile in Spring ’24. Grant data access with a permission set created for the API Integration license and scoped to one integration.

No. Salesforce enforces daily API request limits against all API calls made to the org in a 24-hour period, not per user. A dedicated integration user improves security and traceability, but every integration still draws from the same org-wide allocation, so monitor usage in Setup under System Overview.

Existing connected apps keep working. Since Spring ’26, creating new connected apps is disabled by default and needs Salesforce Customer Support to re-enable. Salesforce recommends external client apps for all new integrations, using the OAuth 2.0 client credentials flow with the integration user as the run-as user.

In Setup, open Company Information. Salesforce Integration appears under User Licenses, and Salesforce API Integration appears under Permission Set Licenses, each with total and used counts. The Active Licenses tab in the Lightning Usage App also tracks licence usage over time.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Salesforce integrations built on MuleSoft, Workato, Celigo and custom APIs, for 500+ clients over 12+ years.