Northern Ridge University uses a custom object named Scholarship Application. All 17 team members in the admissions department are assigned the custom profile Admissions Counselor, which provides Read, Create, and Edit permissions on the object. The university requires that a sensitive custom field, Financial_Audit_Notes__c, be completely hidden from 15 general counselors, but remain fully viewable and editable by 2 senior compliance officers. Which configuration should the Salesforce Administrator implement to meet this requirement following security best practices?
- Restrict Field-Level Security for Financial_Audit_Notes__c on the Admissions Counselor profile to Visible = False, create a permission set granting Read and Edit access to the field, and assign it to the two senior compliance officers.Answer
- BClone the Admissions Counselor profile to create a Senior Compliance Counselor profile with field access to Financial_Audit_Notes__c, and assign the new profile to the two senior compliance officers.
- CHide the Financial_Audit_Notes__c field section on the Lightning Record Page using Dynamic Forms component visibility filters targeted to the user's role.
- DConfigure Profile Login IP Ranges on the Admissions Counselor profile to include only the IP addresses of the senior compliance officers.
Answer
Restrict Field-Level Security for Financial_Audit_Notes__c on the Admissions Counselor profile to Visible = False, create a permission set granting Read and Edit access to the field, and assign it to the two senior compliance officers.
Field-Level Security (FLS) controls data visibility at the platform level, ensuring that users without access cannot view or edit the field in the UI, reports, or APIs. Setting FLS to hidden on the profile establishes the secure baseline, and creating a permission set allows the administrator to additively grant access to the two senior compliance officers without creating redundant profiles.
Step-by-Step Solution
Key Concept
Field-Level Security and Permission Sets