Universal Containers has selected a small and diverse group of users to review inactive accounts.

A sharing rule can extend record-level access only after the user has the fundamental object permission required to use the object. The affected users have no Read permission on Account, so membership in a public group and a sharing rule that exposes inactive Accounts cannot make those records visible. Salesforce evaluates security in layers: the license and object permissions establish whether a user can use an object at all; Field-Level Security controls individual fields; and record-level mechanisms such as OWD, role hierarchy, sharing rules, teams, and manual sharing determine which records are available. A page layout does not grant record or object access, and the position of the Account owner in the role hierarchy is irrelevant when the user ' s profile prevents Account access entirely. The administrator must first grant appropriate Account Read permission through the profile or a permission set, then allow the sharing rule to determine which Accounts the user can reach. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, profiles, permission sets, interaction between object permission and record sharing, and layered security evaluation.