A Salesforce Administrator needs to configure appropriate security controls to satisfy four distinct security and access requirements. Match each business requirement to the most appropriate Salesforce profile or field/object-level security mechanism.
- Completely hide the Social_Security_Number__c field on the Patient object across all page layouts, reports, list views, and API queries for Intake Specialists.Field-Level Security (FLS)
- Restrict the specific hours of the day during which Call Center Support Specialists assigned to a custom profile are allowed to authenticate into the org.Profile Login Hours
- Grant Read and Create access on the Patient_Notes__c object to only three specific Care Coordinators who share a baseline profile with non-clinical staff.Permission Set with Object Permissions
- Allow Field Technicians assigned to a custom profile to create and edit Equipment__c records, while preventing them from ever deleting any Equipment__c records regardless of ownership.Profile Object Permissions
Answer
Hiding a field globally across layouts, reports, and APIs requires Field-Level Security. Restricting login times for users on a profile requires Profile Login Hours. Selectively granting object access to a subset of users on a shared profile requires a Permission Set. Enforcing a prohibition on deleting records profile-wide requires configuring Profile Object Permissions.
Each requirement maps to its exact Salesforce security setting: Field-Level Security enforces field privacy everywhere including APIs and reports; Profile Login Hours restricts user authentication windows; Permission Sets grant additive object permissions to specific users without altering profiles; and Profile Object Permissions dictate baseline CRUD access including Delete restrictions.
Step-by-Step Solution
Key Concept
Profiles and Object/Field-Level Security Controls