Loading

Salesforce Nonprofit Cloud: Permission Set Licenses Missing, Disabled, or Maximum Licenses-Based Issues

Veröffentlichungsdatum: Jul 16, 2026
Beschreibung

This article helps you diagnose why Nonprofit Cloud (NPC) permission set licenses (PSLs) are missing, disabled, or fully consumed when you try to assign them to users.

You may see one or more of these behaviors: after a license transfer from an NPSP org to a new Nonprofit Cloud org, PSLs for features like Fundraising Access or Group Membership are not created; a PSL appears in the org but is disabled and you cannot enable it; the Einstein Activity Capture PSL does not appear in your Enterprise Edition org's Permission Set Licenses list; or when you try to assign a PSL you receive "All Program and Case Management for Experience Cloud Site permission set licenses are in use for maximum licenses. Contact your Salesforce.com representative." even though the Manage Assignments page shows no users assigned. 

Lösung

Work through the cause that matches your symptom.

Cause 1: The permission set license is not provisioned to your org at all.

  • Go to Setup > Company Information [Organization].
  • Scroll to the Permission Set Licenses related list.
  • Look for the Nonprofit Cloud PSLs you need, for example [Fundraising Access], [Advanced Program Management], [Care Plans Access], and [Group Membership].
  • If a PSL is not listed, it is not provisioned to your org and cannot be enabled from Setup. Request provisioning through your Account Executive (AE). If you have no dedicated AE or you use free Power of Us (P10) licenses, contact the Power of Us Team: Americas PowerOfUSDesk@salesforce.com or 1-800-667-6389; EMEA PowerOfUsDeskEMEA@salesforce.com; APAC PowerOfUsDeskAPAC@salesforce.com.
  • After a license transfer between orgs, PSLs do not transfer automatically. Provision the feature PSLs in the new org using the same AE or Power of Us process.

Cause 2: All PSL seats are consumed and you get "All Program and Case Management for Experience Cloud Site permission set licenses are in use for maximum licenses. Contact your Salesforce.com representative."

  • Go to Setup > Company Information [Organization] > Permission Set Licenses.
  • Click the PSL name, for example [Program and Case Management for Experience Cloud Site].
  • Compare Total Licenses to Used Licenses. If Used equals Total, every seat is assigned.
  • If Manage Assignments shows no users, the seats are consumed through a permission set group, not a direct assignment. Go to Setup > Permission Sets, open each permission set that requires this PSL, and check whether it is a member of a permission set group assigned to users. Every user in that group consumes one seat.
  • To free a seat, remove the permission set group or direct PSL assignment from users who do not need the feature. Set the value: in Setup > Users, open the user, and under Permission Set License Assignments click Del next to the PSL.
  • If you need more seats than your allocation, request additional PSLs through your AE or the Power of Us Team above.

Cause 3: The used-license count does not match your number of Salesforce users.

  • PSLs are counted per assignment, not per user license. A user consumes one PSL seat only when the PSL is assigned directly or through a permission set group.
  • Go to Setup > Company Information > Permission Set Licenses > <PSL name> > Manage Assignments to see exactly which users hold the PSL.
  • Do not reduce the count below the number of users who need the feature. Reducing PSLs removes feature access for assigned users.

Cause 4: A Data Processing Engine (DPE) or scheduled flow fails after you removed the Fundraising PSL from the creating user.

  • The DPE and flow run as the user set as the default workflow user or the flow's running user, and that user must retain the [Fundraising Access] PSL and the required permission sets.
  • Go to Setup > Process Automation Settings and confirm the Default Workflow User has [Fundraising Access] assigned under their Permission Set License Assignments.
  • Reassign [Fundraising Access] to the user who owns the DPEs and scheduled flows, then reactivate the affected flows.

Cause 5: Einstein Activity Capture PSL does not appear.

  • Einstein Activity Capture is a separate entitlement and is not part of the Nonprofit Cloud PSL set. Confirm your contract includes Einstein Activity Capture, then request provisioning through your AE.
  • If a user is assigned the Einstein Activity Capture user permission but has EAC Email Capture set to Off, sending through Gmail or Office 365 is unavailable per known issue KI-50535; there is no workaround at this time.

Special case: You cannot assign the "Fundraising Access Digital Agent" PSL to a Salesforce Integration User. This is by design; that PSL supports only agent (digital/external agent) users, not the Salesforce Integration license type.

Confirm the issue is resolved by opening Setup > Company Information > Permission Set Licenses, verifying the required PSL is present with available seats (Used less than Total), then assigning it to a test user under Setup > Users > <user> > Permission Set License Assignments and confirming the target feature (for example the Fundraising or Program Management app) loads without error.

Nummer des Knowledge-Artikels

005389026

 
Laden
Salesforce Help | Article