AeroSpace Tech Solutions recently added a custom field named Background_Check_Status__c to the Contact object to track candidate security clearance details. Management requires that only three HR managers have visibility and edit access to this sensitive field. All other employees, including standard users and sales representatives, must be prevented from seeing or modifying this field anywhere in Salesforce, including reports, list views, and API queries. Which configuration should the System Administrator implement to meet this requirement efficiently?
- Remove Read and Edit access for the field across all profiles via Field-Level Security, create a Permission Set granting Read and Edit access to the field, and assign the Permission Set to the three HR managers.Cevap
- BClone the standard user profile to create a custom profile with field access enabled, and assign this new profile to the three HR managers.
- CRemove the field from the Contact page layout and configure Dynamic Forms component visibility rules to show the component only when the user's role is HR Manager.
- DAdd the HR managers' IP addresses to the organization-wide Network Access list and set the Contact object Organization-Wide Default (OWD) to Private.
Cevap
Remove Read and Edit access for the field across all profiles using Field-Level Security, create a Permission Set granting Read and Edit access for the field, and assign the Permission Set to the three HR managers.
The correct approach enforces field restriction at the data level by setting Field-Level Security (FLS) to hidden for all base profiles, and then granting Read and Edit access to the three HR managers using a Permission Set. This adheres to Salesforce best practices for granting additive permissions without causing profile sprawl.
Adım Adım Çözüm
Anahtar Kavram
Profiles and Field-Level Security vs. Permission Sets