#Trailhead Challenges1,157 discussing

Hello Trailhead Support Team,

I am currently working on the Control Access to Fields module, but I am unable to complete the hands-on challenge due to an issue with the Job Application object.

In my Trailhead Playground, the fields Candidate and Position do not allow me to configure or uncheck the Edit access in the Permission Set, and the Muting Permission Set also shows these fields as locked (greyed out). Because of this, the validation always fails with the message that the Manage_Job_Applications permission set does not properly grant read/edit for all fields except Candidate and Position.

I have already:

• Created multiple new Playgrounds (in English and Portuguese).
• Reinstalled the package each time.
• Tried with different browsers (Chrome, Edge) and languages (English, Portuguese).
• Recreated the Permission Set, Permission Set Group, and Muting multiple times.

The result is always the same: Candidate and Position fields remain locked for Edit access, and the module cannot be validated.

Could you please review this issue and either provide a working package ID or unlock the badge manually so I can continue my learning path?

Thank you for your support. 

Luciano

Best regards, 

Manage Salesforce Data Access challenge I have completed all steps upto creating Sales User Muted in Muting permission set and it is nots displaying and if i creating again it showing like it already existed 

Task Name Mute Permissions in Permission Set Groups 

The task 

1. From Setup, in Quick Find type Permission Set Groups and then select Permission Set Groups.
2. Click Sales Processing—the permission set group you created in Unit 2.
3. Under Permission Sets click Muting Permission Set in Group.
4. Click New.
5. For label use Contracts Permissions Muted.
6. For API Name, use Contracts_Permissions_Muted.
7. Save the muting permission set.

Select permissions to mute.

1. Click the name of your muting permission set.
2. In the Find Settings box, enter Contracts, and then select Contracts.
3. Click Edit.
4. Mute the View All Records and Modify All Records object permissions.
5. Save your changes.
6. In the Find Settings box, enter Contracts, and then select Activate Contracts. (Im stuck here as an error appears "insufficient privileges". 
7. Click Edit.
8. Under Sales, mute the Activate Contracts and Delete Activated Contracts permissions.
9. Save your changes.

Now when you add the permissions for Alyssa’s group to the Sales Contracts permission set, they’ll be muted in the Sales Processing permission set group. Let’s add Alyssa’s permissions to the Sales Contracts permission set. Enable these permissions in the Sales Contracts permission set:

1. Activate Contracts app (user) permission
2. Delete Activated Contracts app (user) permission
3. View All Records and Modify All Records object permissions for contracts

When you’re ready to create the Contracts Processing permission set group for Alyssa, you can add the Sales Contracts permission set to it. Members will receive all enabled permissions, including Activate Contracts, Delete Activated Contracts, and View All Records and Modify All Records for the Contracts object. Voila!

Muting and Permission Dependencies

When you mute permissions in muting permission sets, dependent permissions are also affected. For example, suppose that you grant users Create, Read, Edit, Delete, View All Records, and Modify All Records permissions for an object. Now, if you mute the Read permission, Create, Edit, Delete, View All Records, and Modify All Records are also muted because users can’t perform those tasks without the ability to read the data.

That example is fairly straightforward, but dependencies can get tricky. When you mute permissions, pay attention to the permission change confirmation message when you save your changes. For example, if you had muted Activate Orders, then Edit Activated Orders would have been muted as well.

As you work with your permission set groups, keep permission dependencies in mind to avoid removing permissions from users who need them. For more information on permission set group muting dependencies, see Salesforce Help.

Muting in Installed Packages

We have one more benefit of muting permission sets to share. If you subscribe to a managed package, you can mute permissions in permission set groups for features that you’re not ready to adopt yet.

For example, let’s say you create a permission set group and then add a managed permission set, installed from a managed package, to it. You receive an automatic update from the independent software vendor (ISV) for the package, but you aren’t ready to enable a new field that’s now available in the managed permission set. Is this a problem? No. You can receive the update and the benefits it offers but mute this field permission until you’re ready to adopt it for your org.

Nice job! You now know about muting permission sets and have a complete picture of permission set groups. You learned all the benefits of using permission set groups and how to design your permissions model to make use of their flexibility and reusability.

Resources

• Salesforce Help: Muting Permission Sets

Hands-on Challenge

+500 points

Get Ready

You’ll be completing this unit in your own hands-on org. Click Launch to get started, or click the name of your org to choose a different one.

Your Challenge

Mute Permissions in a Permission Set Group

Update the Sales Processing permission set group to prevent its assigned users from editing and deleting contracts.

• Mute the Edit and Delete permissions for contracts:
  • Permission set group: Sales Processing
  • Muting permission set: Contracts Permissions Muted
  • Object: Contracts
  • Permissions to mute: Edit and Delete

This comes up  

You do not have the level of access necessary to perform the operation you requested. Please contact the owner of the record or your administrator if access is necessary. For more information, see Insufficient Privileges Errors. 

Challenge not yet complete in My Trailhead Playground 1

In the Contracts_Permissions_Muted muting permission set, we can’t find the ‘Edit’ and ‘Delete’ object permissions muted for contracts.