Loading
Feature degradation | Gmail Email delivery failureRead More

Advanced Approvals Readiness for Permission Set License Assignment

Publish Date: Oct 10, 2025
Description

Permission Set Licenses (PSLs) for Advanced Approvals were provisioned to existing CPQ Plus Customer Production Orgs in February 2020. Customers who purchase Salesforce CPQ Plus after the Spring '20 Production release have PSLs provisioned to their Production Orgs on an ongoing basis. Licensing for Salesforce Advanced Approvals are enforced via PSL assignment for users beginning in version 228 (Winter '21). The Managed Package License is no longer enforced on the user level after this version and introduction of PSLs. Prior to upgrading to AA version 228, PSLs have no influence on user access to AA objects or features.
 

NOTE:

  • Do not un-assign Managed Package Licenses (MPL) from users during the transition phase (AA 224 & 226). No changes are required for MPL assignments as this license becomes a site-wide license following the upgrade to AA 228.
    • Sandbox Org users need a PSL in order for them to access AA licensed custom objects. Sandbox users previously were not required to have a MPL assigned because the license for Salesforce AA in Sandbox Orgs prior to 228 was applied as a Site-wide License.
  • Manage Licenses button changes after upgrading to AA package versions 228 or later. Initially this button was removed after version 228 but was brought back by the Core platform in release 236 for the Enable for Platform Integrations feature. With the Managed Package License transitioning to a site-wide license, the Manage Licenses functionality is no longer needed to assign MPLs to users so we've removed this ability from the Manage Licenses page. if you still have the ability to assign MPLs two weeks after upgrading to version 228 or higher, please log a ticket with Salesforce Support for assistance.
  • The auto-upgrade to AA 228 fails if admins have not taken the appropriate actions prior to the upgrade to AA 228 (Winter '21). 
  • Starting in AA 224 (Spring '20), the Check Upgrade Readiness Tool became available and can help admins understand which users need a PSL assigned.
  • Follow the steps below for Production and Sandbox Orgs on AA versions 224 (Spring '20) or 226 (Summer '20). 
Resolution

Use the Check Upgrade Readiness Tool

The Check Upgrade Readiness Tool can be found at:

Setup > Installed Packages > Salesforce Advanced Approvals > Configure > Approval Settings
 

Admins must use the Check Upgrade Readiness Tool as soon as possible in their Production Orgs in preparation for enforcement of PSLs. The purpose of this tool is to help admins identify which users may be required to have PSLs assigned. The tool can be used as often as needed to prepare for upgrade to AA 228. The tool should be used every time users are added or deactivated between installation of AA 224 and prior to the upgrade to version 228.  

View this video to see the check upgrade readiness tool in action.
 

1. Click ‘Check Upgrade Readiness’. Three sections are shown:

Errors
Your org has x active users with assigned permission sets who do not have assigned Managed Package Licenses.
Your org has x inactive users with assigned permission sets. Permission Set Licenses cannot be assigned to inactive user.

CSVs
Users with Permission Set but no Package License
Inactive Users with Permission Set
Users Who Need a Permission Set License

Org Readiness Details
Advanced Approvals Managed Package Licenses Provisioned: x
Advanced Approvals Managed Package Licenses Assigned: x
Users with Advanced Approvals Permission Sets Assigned: x
Advanced Approvals Permission Set Licenses Provisioned: x
Advanced Approvals Permission Set Licenses Assigned: x
 

2. Best practice is to clear the errors first using CSVs 'Users with Permission Set but no Package License' and 'Inactive Users with Permission Set'. When all errors are corrected, two sections are visible:

CSVs
Users Who Need a Permission Set License

Org Readiness Details
Advanced Approvals Managed Package Licenses Provisioned: x
Advanced Approvals Managed Package Licenses Assigned: x
Users with Advanced Approvals Permission Sets Assigned: x
Advanced Approvals Permission Set Licenses Provisioned: x
Advanced Approvals Permission Set Licenses Assigned: x
 

3. Now assign PSLs by using the CSV ‘Users Who Need a Permission Set License’. When all users have been assigned PSLs, one section is visible:

Org Readiness Details
Advanced Approvals Managed Package Licenses Provisioned: x
Advanced Approvals Managed Package Licenses Assigned: x
Users with Advanced Approvals Permission Sets Assigned: x
Advanced Approvals Permission Set Licenses Provisioned: x
Advanced Approvals Permission Set Licenses Assigned: x


Once all errors have been handled from the readiness check the only remaining task is to assign the PSLs. This can be done manually or admins can bulk assign permission set license assignments via Data Loader.

4. Assign PSLs in Sandbox Orgs. This can be accomplished by sandbox refresh if PSL assignments are complete in the Production Org. Alternatively, the Match Production Licenses without a refresh tool can be used to provision PSLs to the Sandbox. Thereafter, the Check Upgrade Readiness Tool can be used to assign PSLs to users in Sandbox. When all AA users have been assigned a PSL and the package is ready to upgrade, the following message appears:

​​​​Your org's readiness check completed without errors. Any admin action that changes user assignments will require another upgrade readiness check.
 

NOTE: Integration Users, Non-CPQ, or Advanced Approvals users may be seen on the reports. Review this article if you find the org has these users. Any admin action that updates users may in turn require another upgrade readiness check to confirm there are no new errors. Users assigned to Permission Sets with Modify All / View all Data do not appear on the upgrade readiness report.

 

Applications included in Permission Set License Readiness

The Check Upgrade Readiness tool currently supports Salesforce CPQ and Advanced Approvals. Salesforce Billing currently uses site licenses, and is therefore not impacted by the change to PSLs.

Custom Permission Sets included in Permission Set License Readiness

Custom permission sets may contain access to Advanced Approvals objects that could be flagged by the Readiness Tool as needing provisioning. Users whose assigned custom permission sets contain AA object permissions requires an AA license and AA PSL. Keep in mind that a custom CPQ permission set could also contain permissions to Advanced Approvals, which may be flagged with the AA Readiness Tool. 
 

Developer Orgs and PSL Assignment

Developer Edition (DE) Orgs are not associated with Production Orgs, therefore Salesforce updated the underlying definition of the DE Orgs before the Summer '20 release to include the necessary Permission Set Licenses for CPQ and Advanced Approvals (exact quantities to be determined).

All new DE Orgs created after Winter '21 have the necessary licenses required for installation of CPQ or Advanced Approvals versions 228 and beyond.

 

Profile

When utilizing the Enhanced Profile User Interface, profile edits are limited to a single object at a time to decrease page load times. To simplify the permission removal process, administrators can disable this feature to allow edits to multiple object permissions at one time. Here is the path to disable this feature:

Setup > User Management Settings > Disable “Enhanced Profile User Interface”

Refresh the profile page to see the updated layout and remove all LCO and their dependent object permissions at the same time to resolve the error.

Knowledge Article Number

000380999

 
Loading
Salesforce Help | Article