ADM-201 · Question #116
Users in separate departments are able to see and edit different fields on Opportunities. The Sales team can edit all fields on the Opportunity while the Support team has read-only access to these…
The correct answer is C. Profile. Field-level security, which determines whether users can see or edit specific fields, is controlled at the Profile level in Salesforce.
Question
Users in separate departments are able to see and edit different fields on Opportunities. The Sales team can edit all fields on the Opportunity while the Support team has read-only access to these fields. Where is field-level Security controlled for users on these teams?
Options
- ASharing Rules
- BRole
- CProfile
- DPublic Groups
How the community answered
(15 responses)- C93% (14)
- D7% (1)
Why each option
Field-level security, which determines whether users can see or edit specific fields, is controlled at the Profile level in Salesforce.
Sharing Rules control record-level access, determining which records a user can see, not which fields on a record they can access or edit.
Role primarily controls record access through the role hierarchy and does not directly govern field-level security.
Profile settings directly control field-level security (FLS), allowing an administrator to specify read-only or editable access for individual fields on an object for users assigned to that profile. This is the primary mechanism for differentiating field access between teams like Sales and Support.
Public Groups are used for grouping users for sharing rules or other mass assignments, but do not directly control field-level security.
Concept tested: Field-level security configuration
Source: https://help.salesforce.com/s/articleView?id=sf.users_profiles_field_level_security.htm&type=5
Topics
Community Discussion
No community discussion yet for this question.