Overview 

Some Accounting Seed Permission Sets come out-of-the-box. These permission sets can be assigned to any user, but you cannot change the settings within the sets.  

There are two options if you want to assign one of these Accounting Seed Permission Sets to users but want to turn off one or more permissions in the permission set.  

Option 1 (Recommended): Create a Permission Set Group with a muting permission set 

Option 2: Clone the out-of-the-box permission set and adjust permissions 

Option 1: Create a Permission Set Group and assign an Accounting Seed Permission Set with a Muting Permission Set
This is the recommended method and is the easiest to maintain. When you assign an Accounting Seed Permission set to a Permission Set Group, it is updated when new releases are pushed out to your org. The only maintenance required is on the Muting Permission. With a new release, choose which new objects and fields are available to users. If you do not want to expose new objects/fields, mute them in the Muting Permission Set. 

Review new objects and fields added with a release 

When a release is pushed to your org, you can review the new Objects and Fields that were added with the new release by either  

• reviewing the release Configuration Changes article (for more recent releases) 
  
  or  

• View Setup Audit Trail by navigating to Setup, searching for View Setup Audit Trail in the Quick Find box, then selecting it to run this report. There is an option to download it to Excel to view all changes for the past 6 months. In the downloaded file you can search for Created custom object and Created custom field to view the objects and fields that were added with the new release. You can filter to show only added objects and fields on the day the release was pushed. 

Create a Permission Set Group 

Permission Set Groups allow you to add one or more permission sets to a group, including a Muting Permission Set.   

1. Navigate to Setup.

2.  Search for Permission Set Groups in the Quick Find box, then select Permission Set Groups.  

2. Click the New Permission Set Group button. 

3. Type a name in the Label field. 

4. The default API Name is based on what is entered in the Label field. You can change this or leave as is.  

Add Permissions to Permission Set Group 

After you create a Permission Set Group, add Permission Sets to it 

1. On the Permission Set Group screen, click Permission Sets in Group. 

2. Click Add Permission Set.  

3. Select the permission sets you want to add to the group. 

4. Click the Add button (at the bottom of the screen).  
   The added permission sets displayed on the screen 

5. Click Done.  

Create a Muting Permission Set 

A Muting Permission Set allows you to mute selected permissions.  

1. On the Permission Set Groups screen, click the Permission Set Group. 

2. Click Muting Permission Set in Group. 

3. Click New.  

4. (Optional) Change the Label and/or API Name. 

5. Click Save.  

6. Click the group link in the Muting Permission Set Label column. 

7. Click the Permission Set Group which contains the permissions to be muted. 

8. Click the Edit button. 

9. Select the Muted checkbox(es) next to the Settings to mute. 

10. Click Save. 

11. Repeat steps 7-10 for any other permissions to be muted.  

Assign a Permission Set Group to a User 

1. Navigate to Setup.

2.  Search for Users in the Quick Find box, then select Users. 

2. On the All Users screen, click the user name. 

3. In the Permission Set Group Assignments section, click Edit Assignments. 

4. Use the Add arrow to move the Permission Set Group from the Available Permission Sets box to the Enabled Permission Sets box. 

5.  Click Save.  

Once you’ve assigned the Permission Set Group to the User, unassign any other related Accounting Seed or custom permission sets previously assigned to the user.  

Option 2: Clone the permission set and adjust the permissions 

We do not recommend this method due to the required maintenance of custom permission sets when future releases are pushed to your org. When a new release is pushed, while Accounting Seed updates all of the Accounting Seed Permission Sets, we do not update custom permission sets. This means, for all new objects and fields created in a new release, you will have to manually update all of your custom permission sets to grant access to the new objects and fields.