A VP of sales needs to report on records owned by individuals in various parts of the role hierarchy. The organization-wide default is set to Private. What should a Platform Administrator configure…

The correct answer is B. Sharing Rules. Sharing Rules (B) are used to extend record visibility beyond what the Organization-Wide Default (OWD) allows. With OWD set to Private, users can only see records they own by default. Sharing rules can be configured to grant additional read or read/write access to records owned…

Submitted by valeria.br· Apr 18, 2026Configuration and Setup

Question

A VP of sales needs to report on records owned by individuals in various parts of the role hierarchy. The organization-wide default is set to Private. What should a Platform Administrator configure to achieve this?

Options

AField-Level Security
BSharing Rules
CPermission Sets
DRestriction Rules

How the community answered

(50 responses)

A
4% (2)
B
82% (41)
C
12% (6)
D
2% (1)

Explanation

Sharing Rules (B) are used to extend record visibility beyond what the Organization-Wide Default (OWD) allows. With OWD set to Private, users can only see records they own by default. Sharing rules can be configured to grant additional read or read/write access to records owned by specific roles, role and subordinates, public groups, or territories - covering the requirement of accessing records across various parts of the role hierarchy. Option A (Field-Level Security) controls visibility of individual fields, not records. Option C (Permission Sets) controls object-level CRUD permissions, not record-level visibility. Option D (Restriction Rules) are used to further restrict access - the opposite of what is needed here.

Topics

#Sharing Rules#Record Access#Organization-Wide Defaults#Role Hierarchy

Community Discussion

No community discussion yet for this question.

Full PLAT-ADMN-201 Practice