A healthcare company needs to restrict visibility of a sensitive custom field, Patient_Social_Security_Number__c, on the Contact object. Currently, all internal staff share a single Custom Standard Staff profile that grants Read and Edit access to this field. Management requires that only two Compliance Officers retain access to view and edit this field, while all other staff lose access. What is the recommended, scalable security solution an administrator should implement to fulfill this requirement?
- AClone the Custom Standard Staff profile to create a Compliance Staff profile with access to the field, remove access from the original profile, and reassign the two Compliance Officers to the new profile.
- Remove Read and Edit access for the field on the Custom Standard Staff profile, create a Permission Set granting Read and Edit access to the field, and assign the Permission Set to the two Compliance Officers.Cevap
- CHide the field component on the Contact Lightning Record Page using Dynamic Forms visibility rules based on the user's assigned role.
- DConfigure Profile Login IP Ranges on the Custom Standard Staff profile to restrict access to the field based on network location.
Cevap
Remove Read and Edit access for the custom field on the profile level, create a Permission Set granting access to the field, and assign that Permission Set to the two compliance users.
In Salesforce security architecture, Field-Level Security (FLS) set at the profile level defines the baseline access for all users assigned to that profile. When only a small subset of users requires elevated access to a sensitive field, standard best practice dictates removing FLS access from the base profile and assigning a Permission Set with FLS access to the specific users.
Adım Adım Çözüm
Anahtar Kavram
Profiles establish baseline access (most restrictive), while Permission Sets grant additive access to specific users.