Examkin

Soru

Zorluk: ZorProfiles and Object/Field-Level Security

An administrator at Northern Trail Outfitters needs to secure a sensitive custom field, Commission_Rate__c, on the Opportunity object. Standard Sales Users must not be able to view or edit this field in the user interface, reports, list views, or API integrations. However, two specific Sales Managers require edit access to Commission_Rate__c, while members of the Finance Audit team require read-only access. Which two configuration steps should the administrator perform to fulfill these security requirements?

  1. Set Field-Level Security for Commission_Rate__c to hidden (uncheck both Visible and Read-Only) on the base Standard Sales User profile.Cevap
  2. Create two distinct permission sets—one granting Edit access and one granting Read-Only access to Commission_Rate__c—and assign them to the appropriate users.Cevap
  3. C
    Remove Commission_Rate__c from the Opportunity page layouts and use Dynamic Forms component visibility rules to hide the field from sales users.
  4. D
    Create customized profiles for the two Sales Managers and the Finance Audit team with tailored Object Permissions for the Opportunity object.

Cevap

The administrator should set Field-Level Security (FLS) to hidden on the Standard Sales User profile and create two permission sets (one for Edit access, one for Read-Only access) to grant the required access to specific users.
To restrict field access universally, Field-Level Security (FLS) must be configured to remove both Read and Edit access on the base profile. To grant exceptional access to specific individuals or sub-teams, Permission Sets are used because Salesforce security uses an additive model where permission sets extend access beyond the profile base.

Adım Adım Çözüm

1
Restrict baseline field access using Field-Level Security
Commission_Rate__c is hidden from all users assigned to the Standard Sales User profile across the UI, reports, search, and API.
Field-Level Security is the primary mechanism in Salesforce for controlling field visibility and access universally.
2
Create additive access permissions using Permission Sets
One permission set grants Read and Edit access on Commission_Rate__c; a second permission set grants Read-Only access on Commission_Rate__c.
Permission sets allow administrators to expand permissions for specific users on top of their baseline profile without modifying the baseline profile.
3
Assign permission sets to targeted users
The two Sales Managers receive the Edit permission set, and Finance Audit team members receive the Read-Only permission set.
This fulfills user-specific and role-specific requirements while maintaining a lean profile architecture.

Anahtar Kavram

Field-Level Security (FLS) restriction combined with Permission Set extension
Bu soruyu puanla

Konular

Profiles and Object/Field-Level Security

Bu konudan daha fazla soru