BrightPath Health requires strict data privacy for sensitive patient information on a custom object named Patient Record. Currently, all 40 clinical coordinators share the custom 'Clinical Coordinator' profile. The management team requires that only 4 compliance auditors can view and edit the national_insurance_id__c field. Furthermore, access to this field must be restricted at the API and reporting levels, not just on the user interface. Which two steps should the Salesforce Administrator take to meet these security requirements? (Choose 2 answers.)
- Set Field-Level Security on the national_insurance_id__c field to remove Read and Edit access from the Clinical Coordinator profile.Cevap
- Create a Permission Set that grants Read and Edit access to national_insurance_id__c and assign it to the 4 compliance auditors.Cevap
- CClone the Clinical Coordinator profile to create a Compliance Auditor profile with field access, then assign the 4 compliance auditors to the new profile.
- DRemove national_insurance_id__c from the standard page layout and use Dynamic Forms visibility filters to restrict its display.
Cevap
The administrator should restrict access on the base profile using Field-Level Security (FLS) and extend field permissions to the four compliance auditors using a Permission Set.
Field-Level Security (FLS) on the base profile secures the field across all interfaces (UI, API, reports). A Permission Set is then used to grant additive read/edit access specifically to the users who need it, adhering to Salesforce security best practices.
Adım Adım Çözüm
Anahtar Kavram
Profiles restrict base Field-Level Security while Permission Sets extend field permissions to specific users.