Lesson 17 of 22 · All lessons

Section 7 · Security and Access · 7% of exam

7.1 The Layers of Salesforce Access

3 min read Updated Nov 19, 2026

Exam objective

Select foundational record-sharing mechanisms and explain how they contribute to visibility.

Official references: https://help.salesforce.com/s/articleView?id=sf.security_overview.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_userprofiles.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&language=en_US&type=5

Core concepts

Record-level visibility controls which records users can view or edit after they have object permission. Organization-wide defaults establish the baseline sharing access for records of an object. When the baseline is restrictive, additional mechanisms can open access to appropriate users. The role hierarchy can provide access upward for users who manage records owned below them, subject to configuration and object behavior. Sharing rules can extend access based on ownership or record criteria.

Manual sharing can grant access to a particular record when an authorized user needs to collaborate. Teams can support collaboration around accounts, opportunities, or cases when configured and appropriate. Public groups collect users, roles, or other groups so a sharing rule can target a business audience. These mechanisms solve different patterns; choose based on whether the need is broad and repeatable or limited to specific records and collaborators. Example: A company sets Cases to private because only assigned teams should view them. Supervisors need visibility into their teams’ work through the role hierarchy or suitable sharing configuration. A specialist team needs read access to Cases with a particular product category. A criteria-based sharing rule may fit if the audience and criteria are stable. Granting every support user broad access would be simpler but would violate the stated need for separation. Record sharing does not grant access to the object or fields. A sharing rule cannot make a user a Case user if they lack Case object permission. Likewise, a user may see a record but not edit it if their effective permissions are read-only. Sharing is generally additive to baseline access and should be designed together with object permissions and roles. When the scenario says “ensure the right users can see these records,” identify the baseline and the audience. If access should be generally restricted, org-wide defaults are foundational. If a defined audience needs additional access, consider a sharing rule, hierarchy, team, or manual share based on the pattern. If the user needs permission to read the object itself, adjust object access separately.

Sharing behavior can vary by object and org configuration. Treat official documentation and the described business rule as authoritative for a specific implementation.

Ask whether access should be default, hierarchical, rule-based, team-based, or an exception for one record.

Extra concept

Extra concept: A role hierarchy is designed around record visibility and management relationships. It is not the same thing as an org chart or job title list; build it to reflect access needs.

Key takeaways

  • Record-level visibility controls which records users can view or edit after they have object permission.
  • Manual sharing can grant access to a particular record when an authorized user needs to collaborate.
  • Example: A company sets Cases to private because only assigned teams should view them.
  • Official references: https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&language=en_US&type=5

Check your knowledge

Answer exam-style Security and Access questions with answers and explanations.

Practice Security and Access
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Foundations simulator: same number of questions, same time limit.

Get Complete Access