Early in the discovery and solution meetings, it was determined that the client would primarily...

Salesforce security should be implemented by separating object and field permissions from record-level access. Permission sets and the Financial Services-provided permission sets determine which objects, fields, applications, and Financial Services capabilities a user can access. This approach is preferable to attempting to manage every requirement exclusively through custom profiles because permission sets provide modular, additive access that can be assigned according to job function.

For record visibility, Organization-Wide Defaults establish the baseline access level. Because the stated requirement is that records remain private, OWD must be configured restrictively for the relevant objects. Salesforce recommends establishing the most restrictive appropriate OWD first and then using the remaining sharing mechanisms to selectively broaden access.

The Role Hierarchy then satisfies the managerial-access requirement. Users higher in the hierarchy can inherit access to records owned by, or shared with, users below them. Salesforce specifically identifies the role hierarchy as the mechanism for extending record visibility upward through the management structure.

Explicitly sharing every subordinate ' s individual records with each manager would introduce unnecessary administration and duplicate functionality already provided by the hierarchy.