Loading

PermissionSetLicense Does Not Exist Error Deploying User Access Policy

Publiceringsdatum: Oct 15, 2026
Beskrivning

Issue

When you deploy a User Access Policy to a Salesforce org, the deployment fails with a "PermissionSetLicense does not exist" error. The permission set license (PSL) named in the error is already in the target org.

Symptoms

  • The deployment of one or more User Access Policies fails.
  • Each failing policy action returns an error in this format: Error <PolicyName> The action target <PSL name> of type PermissionSetLicense does not exist.
  • The PSL name in the error uses an underscore where the PSL's key uses a period, for example vlocity_cmt_DocGenIndCmeUserPsl.
  • A query in the target org confirms that the PSL exists.
Example error message
Error Set_UserFunction_to_Blank The action target vlocity_cmt_DocGenIndCmeUserPsl of type PermissionSetLicense does not exist.
Error Set_UserFunction_to_CallCenterAgent The action target vlocity_cmt_DocGenIndCmeUserPsl of type PermissionSetLicense does not exist.
Error Set_UserFunction_to_Developer The action target vlocity_cmt_CommunicationsCloudPlusPsl of type PermissionSetLicense does not exist.

Root Cause

Every permission set license has two identifiers:

  • PermissionSetLicenseKey: the key that the User Access Policy deployment uses to find the PSL.
  • DeveloperName: the API developer name of the PSL.

For PSLs whose key includes a prefix such as a namespace, these two values differ. The key separates the prefix from the name with a period, while the DeveloperName uses an underscore:

PermissionSetLicenseKeyDeveloperName
vlocity_cmt.CommunicationsCloudPlusPslvlocity_cmt_CommunicationsCloudPlusPsl
vlocity_cmt.DocGenIndCmeUserPslvlocity_cmt_DocGenIndCmeUserPsl

When you retrieve a User Access Policy, its PSL action targets refer to the PSL's DeveloperName. When you deploy the policy, Salesforce looks up a PSL target by PermissionSetLicenseKey. The DeveloperName doesn't match any key, so the deployment reports that the PSL doesn't exist, even though it does.

Lösning

Use this workaround: in the retrieved User Access Policy metadata, change each PSL action target from the DeveloperName to the PermissionSetLicenseKey, then redeploy.

Step 1 — Confirm the cause

  1. Copy the PSL name from each error message, for example vlocity_cmt_DocGenIndCmeUserPsl.

  2. In the target org, run this SOQL query:

    SELECT PermissionSetLicenseKey, DeveloperName FROM PermissionSetLicense
    
  3. Find the row where DeveloperName matches the name in the error.

  4. Check the result:

    • If the row exists and its PermissionSetLicenseKey differs from the DeveloperName (for example, a period instead of an underscore after the namespace), this article applies. Continue to Step 2.
    • If no row matches, the PSL isn't available in the target org, and this article doesn't apply. Confirm that the license that provides the PSL is available in the target org before you redeploy.

Step 2 — Update the policy metadata

  1. Retrieve the affected User Access Policy from the source org, or open the copy you already retrieved.
  2. Open the User Access Policy metadata file.
  3. Find each userAccessPolicyActions entry whose type is PermissionSetLicense.
  4. Replace its target value (the DeveloperName) with the matching PermissionSetLicenseKey from Step 1. For example, change vlocity_cmt_DocGenIndCmeUserPsl to vlocity_cmt.DocGenIndCmeUserPsl.
  5. Repeat for every PSL action target listed in the deployment errors.
  6. Save the file.

Step 3 — Redeploy and verify

  1. Deploy the updated User Access Policy to the target org.
  2. Confirm that the deployment completes without "PermissionSetLicense does not exist" errors.
  3. In Setup, review the deployed User Access Policy and check that its permission set license actions show the expected licenses.

Note: If you deploy a policy with a status of Active, its status changes to Design. An admin can then activate the policy again in Setup.

If the error persists

  • Check the edited target value against the query result. Copy the PermissionSetLicenseKey exactly as the query returns it, including the namespace prefix and the period.
  • Make sure you updated every policy and action that the deployment log lists. Each failing action reports its own error.
  • If the deployment still fails, contact Salesforce Support. Include the full deployment error and the PermissionSetLicenseKey and DeveloperName values from the query. 
Knowledge-artikelnummer

003200531

 
Laddar
Salesforce Help | Article