Exceptions to role hierarchy-based record access
Key Takeaway
The role hierarchy usually passes record access up to managers, but some settings and private records stop it. A private opportunity is the odd one: the hierarchy still works, and opportunity sharing rules are what stop.
Normally, users above someone in the role hierarchy can reach the records that person owns. Several settings and private records stop that upward access, so a manager may not see a subordinate's record. Knowing these exceptions lets you predict who can see a record and choose the right fix.
Default role hierarchy access
By default, users at any role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy.
Users above a record owner in the hierarchy can normally delete that record. If the organization-wide default for cases or leads is "Public Read/Write/Transfer", only the record owner or an administrator can delete the record.
Administrators, and users with "View All Data" or "Modify All Data", have access to view or edit all data.
Hierarchy access, like the rest of the sharing model, controls only which records a user can see. Users still need the matching object permissions, regardless of sharing settings. For example, a user needs the "Read" permission on accounts to see an account.