Question

Difficulty: EasyProfiles and Object/Field-Level Security

An administrator needs to ensure that users assigned to the Standard User profile cannot view or edit the custom field Bonus_Amount__c on Opportunity records across reports, list views, and API integrations. Which configuration change should the administrator make to fulfill this requirement?

  1. Set the Field-Level Security for Bonus_Amount__c to hidden on the Standard User profile by removing Read and Edit access.Answer
  2. B
    Remove the Bonus_Amount__c field from the Opportunity page layout and hide the field using Dynamic Forms component visibility rules.
  3. C
    Create a new custom profile for each individual user needing access and assign field access on a per-profile basis.
  4. D
    Add the users' IP addresses to the Organization-Wide Network Access settings to restrict access to sensitive fields.

Answer

Set the Field-Level Security for Bonus_Amount__c to hidden on the Standard User profile by removing Read and Edit access.
Field-Level Security (FLS) is the authoritative security mechanism in Salesforce for controlling field visibility and editability across the entire platform, including reports, list views, and API calls. Removing Read access via FLS ensures the field is completely hidden from users assigned to that profile.

Step-by-Step Solution

1
Identify the security scope required by the scenario.
The requirement demands restricting access across all user interfaces, reports, list views, and API calls.
UI-only restrictions (such as page layouts or Dynamic Forms) do not restrict access in reports or API calls.
2
Select the appropriate access control mechanism in Salesforce.
Field-Level Security (FLS) on the profile directly controls visibility and editability across all surfaces.
Removing Read access via FLS completely hides the field from the specified profile.

Key Concept

Field-Level Security (FLS) enforcement vs UI visibility
Rate this question