Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More

Health Cloud: Cannot assign Health Cloud Starter or Provider Relationship Management permission set license to Salesforce Integration license users

Publish Date: May 24, 2026
Description

This article explains why you cannot assign Health Cloud permission set licenses to a Salesforce Integration license user and how to configure an API-only integration user that needs access to Health Cloud objects. Customers describe this as: "Unable to assign Health Cloud Provider Relationship Management PSL to Integration User — this doesn't work if my integration user is using the Salesforce Integration user license" and "In the Winter '26 sandbox I could assign Health Cloud Starter permission set license to a Salesforce Integration license user, but in the Spring '26 preview sandbox I get an error and cannot assign it."

When you open the user record for an integration user (User License = Salesforce Integration, Profile = Salesforce API Only System Integrations or Minimum Access - API Only Integrations), navigate to Permission Set License Assignments, click Edit Assignments, and select Health Cloud Starter, Health Cloud Platform, Health Cloud Provider Relationship Management, Health Cloud Provider Search, or Health Cloud Advanced Therapy Orchestration, the assignment fails with the error: "Integration User can't be assigned the Health Cloud Starter permission set license, because Integration User's user license doesn't support it." The same behavior occurs when assigning a permission set that contains the Manage Health Cloud system permission, or when attempting to access objects such as Care Program [CareProgram], Care Program Provider [CareProgramProvider], Care Program Enrollee [CareProgramEnrollee], HealthcarePractitionerFacility, HealthcareProviderSpecialty, CareSpecialty, ClinicalServiceRequest, MedicationRequest, HealthcareFacilityNetwork, or PlanBenefit through Data Loader, Apex, or the Metadata API.

Root cause

The Salesforce Integration user license is a minimum-access license intended only for server-to-server API operations on standard CRM objects. It does not support Industry Cloud permission set licenses (Health Cloud Starter, Health Cloud Platform, Health Cloud Provider Relationship Management, etc.) and does not support the Manage Health Cloud system permission. Health Cloud standard objects are gated behind these PSLs and are therefore inaccessible to Integration license users. This is a hard platform constraint, not a sandbox or release-specific defect; behavior may have appeared to work in older sandboxes due to inconsistent enforcement, and stricter validation in Spring '26 now blocks the assignment consistently.

Affected editions: Enterprise, Performance, Unlimited, and Developer Editions with Health Cloud or Life Sciences Cloud.

Affected user license: Salesforce Integration.

Affected profiles: Minimum Access - API Only Integrations, Salesforce API Only System Integrations.

Resolution

Use one of the following supported paths to give an API-only integration user access to Health Cloud objects. Do not continue trying to assign Health Cloud Starter, Health Cloud Platform, or Health Cloud Provider Relationship Management PSLs to a Salesforce Integration license user — this is not supported by the platform.

Cause 1: Integration user must remain on the Salesforce Integration user license

  1. Navigate to Setup > Users > Users and open the integration user record.
  2. Confirm User License is Salesforce Integration and Profile is Minimum Access - API Only Integrations [MinimumAccess_APIOnlyIntegrations] or Salesforce API Only System Integrations.
  3. In the user detail page, locate Permission Set License Assignments and click Edit Assignments.
  4. Select Salesforce API Integration and click Save. Do not select Health Cloud Starter, Health Cloud Platform, or Health Cloud Provider Relationship Management — these are not supported on this license and will return the assignment error.
  5. Navigate to Setup > Permission Sets and create a new permission set. For License, select Salesforce API Integration. Do not select a Health Cloud PSL on the permission set.
  6. In the new permission set, grant Object Permissions (Read, Create, Edit, Delete as required) only on standard CRM objects that the Salesforce Integration license supports (for example Account, Contact, Case). Health Cloud standard objects such as Care Program Enrollee [CareProgramEnrollee], HealthcarePractitionerFacility, HealthcareProviderSpecialty, CareSpecialty, ClinicalServiceRequest, MedicationRequest, HealthcareFacilityNetwork, and PlanBenefit cannot be granted through this permission set.
  7. Assign the new permission set to the integration user via Setup > Users > [Integration User] > Permission Set Assignments > Edit Assignments.
  8. Confirm the issue is resolved by logging in as the integration user (or using the user's OAuth credentials in Data Loader) and reading or writing only the supported standard CRM objects. Health Cloud objects will remain inaccessible on this license — use Cause 2 if Health Cloud object access is required.

Cause 2: Integration user requires access to Health Cloud objects (Care Program Enrollee, HealthcarePractitionerFacility, MedicationRequest, etc.)

  1. Navigate to Setup > Users > Users and open the integration user record.
  2. Click Edit. Change the User License from Salesforce Integration to Salesforce, and change the Profile to a full Salesforce profile such as Standard User or a custom profile cloned from Standard User. This consumes one full Salesforce or Health Cloud user license seat.
  3. Click Save.
  4. On the user detail page, click Permission Set License Assignments > Edit Assignments. Select the Health Cloud PSL required for the target object: Health Cloud Starter for Care Program [CareProgram], Care Program Provider [CareProgramProvider], and Care Program Enrollee [CareProgramEnrollee]; Health Cloud Provider Relationship Management for HealthcarePractitionerFacility and HealthcareFacilityNetwork; Health Cloud Platform where listed by the object's documentation. Click Save.
  5. Navigate to Setup > Permission Sets and assign the matching permission set (for example Health Cloud Starter or Health Cloud Foundation) to the user via Permission Set Assignments > Edit Assignments. Note that assigning the PSL alone is not sufficient — the corresponding permission set must also be assigned, as confirmed in case evidence.
  6. If the user must still be restricted to API-only access, set the profile's Login Hours and Login IP Ranges, or use a permission set that does not grant UI access, instead of relying on the Salesforce Integration license.
  7. Confirm the issue is resolved by running the original Data Loader extract or API call against the target Health Cloud object (for example Care Program Enrollee [CareProgramEnrollee] or HealthcarePractitionerFacility) and verifying that records return without a permission error.

Cause 3: Life Sciences Cloud orgs needing HealthcarePractitionerFacility access

  1. If the org is licensed for Life Sciences Cloud and the integration user must remain on the Salesforce Integration license, assign the Health Cloud Foundation permission set to the user via Setup > Permission Sets > Health Cloud Foundation > Manage Assignments > Add Assignments. The Health Cloud Foundation permission set provides access to HealthcarePractitionerFacility and is supported with the Minimum Access - API Only Integrations license per Salesforce Support guidance.
  2. If Health Cloud Foundation is not present in the org, the only supported alternative is to convert the user to a full Salesforce license as described in Cause 2.
  3. Confirm the issue is resolved by querying HealthcarePractitionerFacility through Data Loader or the REST API as the integration user and verifying that records are returned.
Knowledge Article Number

005385054

 
Loading
Salesforce Help | Article