An administrator at Cloud Kicks needs to restrict access to a sensitive custom field, Executive_Notes__c, on the Account object. All members of the Account Management team share a custom profile that grants access to Account records. However, only two team leads require access to view and edit Executive_Notes__c. This field must remain completely hidden from all other Account Management team members across reports, list views, search results, and API integrations. Which solution meets these security requirements while following Salesforce administrative best practices?
- Set Field-Level Security for Executive_Notes__c to remove Read and Edit access on the base Account Management profile, then assign a Permission Set granting Read and Edit access to the two team leads.Cevap
- BHide the Executive_Notes__c field on the Account Lightning Record Page by applying Dynamic Forms component visibility rules targeted at the team leads' user roles.
- CClone the Account Management profile to create a dedicated Team Lead profile with Read and Edit access to Executive_Notes__c, and reassign the two team leads to this new profile.
- DAdd the corporate network IP range to Organization-Wide Network Access to enforce profile-level field visibility rules for Executive_Notes__c across API connections.
Cevap
Set Field-Level Security for Executive_Notes__c to remove Read and Edit access on the base Account Management profile, then assign a Permission Set granting Read and Edit access to the two team leads.
Field-Level Security (FLS) controls field access universally across all Salesforce tools, including reports, list views, search results, and API integrations. Removing access on the shared base profile and granting access to specific users via a Permission Set adheres to the principle of least privilege while maintaining a clean, scalable profile architecture.
Adım Adım Çözüm
Anahtar Kavram
Field-Level Security and Permission Sets vs. Profiles