Salesforce Record Access Practice: OWD, Roles and Sharing Rules
Unlimited record access practice for the Sharing and Visibility Architect, Platform Administrator II and Platform Developer exams: read the org-wide default, role hierarchy, sharing rules, team, manual share and object permissions, then tap the access the user gets. A wrong pick names the slip, such as giving hierarchy access downward.
- Record
- Owner
- Org-wide default
- Permissions
- Team
- Manual share
- Public group
- Sharing rules
Role hierarchy
Internal users, one per role. Implicit sharing between accounts and their child records is left out. Permissions are the user’s object permissions from the profile and permission sets.
Exam practice
Access to Records is 39% of the Platform Sharing and Visibility Architect exam, record access is part of Security and Access in Platform Administrator II, and Platform Developer asks you to prevent data access security vulnerabilities. Start with the free real exam questions, then get the full pack.
Record access FAQ
What does the org-wide default do?
It sets the access users have to records they don’t own. For most objects the choices include Private, Public Read Only and Public Read/Write. Private: only the owner and users above the owner’s role can view and edit. Public Read Only: everyone can view, and only the owner and users above can edit. Public Read/Write: everyone can view and edit. The role hierarchy, sharing rules, teams and manual shares can only open access up from there.
How does the role hierarchy give access?
Users higher in the role hierarchy get the same access as the users below them, to records those users own and to records shared with them. Access never flows down: a rep doesn’t see a manager’s records through the hierarchy. For custom objects an admin can turn off Grant Access Using Hierarchies; then only the owner and users granted access get it.
Can a sharing rule restrict access?
No. Sharing rules only grant wider access and can’t restrict access below the org-wide default. To create sharing rules, the default must be Private or Public Read Only. If several rules give a user different levels, the user gets the most permissive one.
What is the difference between owner-based and criteria-based sharing rules?
An owner-based rule shares records owned by members of a role, a role and its subordinates, or a public group. A criteria-based rule shares records whose field values match, whoever owns them. Users above the rule’s recipients in the role hierarchy get the same access, on custom objects only while Grant Access Using Hierarchies is on.
What if a user gets access in two ways?
Salesforce uses the most permissive grant. If Maria shares a record Read/Write with Frank and a sharing rule gives Frank’s group Read Only, Frank keeps Read/Write.
Do object permissions limit what sharing gives?
Yes. Read lets a user only view records and Edit lets a user read and update them, and both respect sharing. Org-wide defaults can never grant more access than the object permissions, so a user with Read but no Edit gets Read Only from a Read/Write share, and a user without Read sees nothing.
What do View All and Modify All do?
They override sharing. View All Records lets a user view every record of that object; Modify All Records lets a user read, edit, delete, transfer and approve every record. Neither overrides field-level security.
How do account teams and manual sharing add access?
An account team member gets the access set on their team member record, which must be equal to or less restrictive than the org-wide default. Manual sharing lets the owner, users above the owner, users with Modify All on the object and admins share one record with a user, group or role. By default manual shares are deleted when the record owner changes.
Does Apex code follow the same record access?
Only when the class asks for it. A class declared with sharing enforces the sharing rules of the current user. A class declared without sharing doesn’t, and can reach records the user otherwise can’t access.
What does the drill leave out?
Implicit sharing between accounts and their opportunities, cases and contacts, territories, restriction rules, external users, Apex sharing and opportunity teams. It also never asks about a manager of a public group member, because the group’s own Grant Access Using Hierarchies setting decides that. This is the tool’s own scope, not a Salesforce rule.
Sources
- Salesforce, Record-Level Access: Under the Hood (PDF, Winter ’27): access grants, Role and RoleAndSubordinates groups, the sample scenarios with Maria, Marc, Bob, Frank and Sam, and the most permissive grant winning.
- Salesforce Help: Organization-Wide Sharing Defaults, Organization-Wide Default Access Settings, Create a User Role (Grant Access Using Hierarchies on custom objects), Control Who Sees What.
- Salesforce Help: Sharing Rules, Sharing Rule Types, Sharing Rule Considerations, Manual Sharing, Considerations for Using Account Teams.
- Salesforce Help: Object Permissions and “View All” and “Modify All” Permissions Overview.
- Trailhead, Data Security module: Control Access to Records.
- Apex Developer Guide: Using the with sharing, without sharing, and inherited sharing Keywords.
- Exam guides: Platform Sharing and Visibility Architect (Access to Records 39%) and Platform Administrator II (Security and Access 20%) and Platform Developer (User Interface 25%, which includes data access security).
- Checked 20 November 2026. The tool’s own approach: scenarios are generated, with internal users and one user per role. An independent re-solver (Salesforce’s group membership and sharing row model, read from the scenario text) agreed with the drill on 8,000 generated scenarios.
Checked 20 November 2026 against Salesforce Help, the Record-Level Access: Under the Hood guide, the Trailhead Data Security module and the current exam guides.
- DrillServiceNow ACL practiceDecide if a read or write is granted and tap the ACL that decides it.
- DrillAWS IAM policy evaluation practiceDecide if a request is allowed or denied across identity policies, bucket policies, SCPs and permissions boundaries, and pick what decides it.
- DrillSplunk SPL practiceSay what a search returns from a small event table: NOT and !=, wildcards, where, eval, stats, top, dedup and sort.