Managing Future Updates to Permission Sets and Permission Set Groups

We have redesigned Accounting permissions and the FinancialForce security model. This provides a robust and focused approach to manage user security. From Fall 2021, we have started to introduce a series of functional permissions. As this functionality is being delivered over successive releases and is not yet complete, we recommend that you do not implement the functional permissions contained in this release.

In future releases, FinancialForce will make changes to permission sets and permission set groups for Accounting.

If you deploy unamended FinancialForce permission set groups and unamended FinancialForce permission sets, these will be automatically upgraded in future releases. This approach requires the least manual intervention at each release.

If you have customized permission set groups that contain unamended FinancialForce permission sets, the permission sets will be automatically upgraded in future releases. This approach reduces the need to manually update permission set groups following each release.

Note: If you have cloned a FinancialForce permission set, the permission set will not be upgraded. An administrator must make the changes manually. We recommend you do not clone or amend the FinancialForce permission sets. You can use permission set groups to amend the access as needed.

Best Practice

We recommend the following:

• Use the permission sets provided by FinancialForce rather than cloning. By doing this, you are not required to make changes to your cloned permission sets when permission sets are upgraded in future FinancialForce releases.
• Use the permission set groups provided by FinancialForce. You can extend or modify the permissions using custom permission sets or muting functionality.
• Avoid combining permissions for multiple Salesforce packages into the same permission set or permission set group.