A Salesforce Administrator at a financial services firm needs to restrict access to a sensitive custom field, Credit_Score__c, on the Account object. Currently, 25 support representatives share a single custom Support profile that grants Read and Edit access to all Account fields. However, only 3 senior support representatives require access to view and edit Credit_Score__c. Which configuration solution should the administrator implement to meet this security requirement while maintaining maintainability?
- Remove Field-Level Security access for Credit_Score__c from the Support profile, create a Permission Set granting Read and Edit access to Credit_Score__c, and assign it to the 3 senior representatives.Cevap
- BClone the Support profile to create a Senior Support profile with Credit_Score__c access enabled, then reassign the 3 senior representatives to the new profile.
- CConfigure Dynamic Forms component visibility on the Account Lightning Record Page to hide the Credit_Score__c field when the user is not a senior representative.
- DSet the Organization-Wide Default sharing setting for the Account object to Private and define a criteria-based sharing rule for the 3 senior representatives.
Cevap
Remove Field-Level Security access for Credit_Score__c from the Support profile, create a Permission Set granting Read and Edit access to Credit_Score__c, and assign it to the 3 senior representatives.
The correct solution enforces least privilege at the profile level by restricting Field-Level Security (FLS) for all support representatives, while using a Permission Set to additively grant access to the 3 senior representatives. This keeps profile administration clean and scalable.
Adım Adım Çözüm
Anahtar Kavram
Field-Level Security (FLS) baseline restrictions combined with Permission Sets for additive access control.