Permission sets are a Salesforce platform feature enabling you to manage user access. Permission sets are provided with the PSA managed package. Use permission sets with user profiles to manage your users' privileges. You can assign permission sets to multiple concurrent users.
PSA includes predefined permission sets for all new functionality to easily provide users access to new features. Managed packages still include custom user profiles provided with earlier versions of PSA, but are no longer updated to include new functionality.
Identifying PSA Permission Sets
PSA Permission sets are provided in three levels:
- Application
- Role
- Action
Assigning PSA Permission Sets
Here are some scenarios of how you can assign PSA permission sets.
- Assign the top level PSA permission set to administrators and appropriate operational users. This is assigning permissions at the Application level (Level 1).
- Assign level 2 permissions based on the role(s) of the user. Level 2 permission sets will be included in PSA in the future.
- Assign a separate permission set for different actions, such as ‘Project Version - Save’ or ‘Skills - Cascade Delete’ (at Level 3).
Each permission set gives users the access required to work with that application, role, or action. A permission set also includes access to any classes and pages that are required to work with an application, role, or action.
For more information on the permission sets included in this release of PSA, see Permission Sets for this Release.
Using PSA Permission Sets
You can use a combination of user profiles and permission sets to manage your users' privileges:
| Use Profiles | Use Permission Sets |
|---|---|
| Manage user privileges for standard Salesforce objects and other applications (excluding PSA). | Assign to individual users. |
| Manage user privileges for other FinancialForce applications such as PSA. | Use for PSA. |
| Manage team-wide privileges. | Assign extra privileges to one or two individuals within the team. |
You cannot edit predefined permission sets. If you need to add extra permissions to a user, create an extra permission set with those permissions and assign both the packaged permission set and the extra one. If the packaged permission sets are too permissive, clone them and edit the copied ones. However, copied permission sets are not updated if the original permission set is changed in a future upgrade. You are responsible for manually updating them as necessary. Predefined permission sets are updated automatically.
Migrating to using PSA Permission Sets
If you are upgrading from an earlier version of PSA, here are some suggestions as to how you can migrate to using permission sets:
- Continue to use your existing user profiles and assign permission sets to users for new functionality only.
- Remove all PSA permissions from your existing user profiles, then assign permission sets to users for all the functionality they need.
- When creating new users, use a profile to manage user privileges for standard Salesforce objects and assign the PSA permission sets to individual users.
You can create list views for groups of PSA permission sets to make them easier to assign to users. To assign permission sets to users, see the suggested Salesforce Help topics below.
Adding Custom Fields to PSA Permission Sets
If you add custom fields to any PSA objects, you must add them to the relevant permission sets. You can also enable access to the custom field in other permission sets, such as PSA – Expense Reports.
Salesforce Help Topics
The Salesforce help topics below provide further information about permission sets and assigning them to users:
- "What are permission sets?"
- "About Permission Sets and Profile Settings in Packages"
- "Assign Permission Sets to a Single User"
- "Assign a Permission Set to Multiple Users"