Section 2 · Configuration and Setup · 15% of exam
2.5 Sharing model, record access, and folders
Exam objective
Given a request, apply the sharing model using org-wide defaults, roles, hierarchy, public groups, teams, sharing rules, and report or dashboard folders. Org-wide defaults establish the baseline record access for an object. If a user needs more access, role hierarchy, sharing rules, teams, or manual sharing may extend access depending on the object and configuration. Roles support hierarchical access; public groups let administrators target sets of users, roles, or other groups in sharing rules. Use a team when collaboration is tied to particular records and members need defined access. Use sharing rules when a repeatable group of users needs access to records based on ownership or criteria. Check whether the requirement is to expose records broadly or only selected records; broadening the baseline can affect much more data than intended.
Report and dashboard folders control who can access the analytics asset. Record sharing controls which records appear in the report results. A user may have access to a report folder but still see fewer records because of record-level visibility.
Additional concepts
Record access is layered
Start with the object’s org-wide default, then consider ownership, the role hierarchy, teams, sharing rules, and other supported sharing mechanisms. Roles organize hierarchical access; public groups provide reusable audiences for sharing. A team is typically tied to collaboration on a particular record, while a sharing rule extends access to a defined population.
Analytics access is separate
A report or dashboard folder determines whether the user can open or manage the asset. Record sharing determines which rows the user can see, and field permissions can affect data availability. If someone opens a report but sees fewer rows, changing folder access may not address the cause.
A sales manager needs visibility into a subordinate team’s opportunities. Review the role hierarchy and object’s sharing baseline first; if only a subset of records should be shared, use a narrower team or sharing rule where appropriate.
Access is cumulative. Verify effective access from the affected user’s perspective after adding a sharing mechanism.
Key takeaways
- Org-wide defaults form a baseline; sharing mechanisms can extend access.
- Roles, public groups, teams, and sharing rules have different targeting models.
- Folder access and record visibility are separate checks.
