Ursa Major Solar (UMS) uses a public sharing model for accounts. UMS would like to move to a more restrictive sharing model but wants the Sales team…

To transition from a public to a more restrictive sharing model, the first step is to change the organization-wide default (OWD) for the Account object to 'Private' or 'Public Read Only'. This action establishes the new, more restrictive baseline for record access. After locking down the data, a sharing rule is necessary to grant access back to specific users. Because the requirement is to share accounts based on a field value (Record Type = 'Sales'), a criteria-based sharing rule is the appropriate mechanism. This rule will automatically share all accounts that meet this criterion with the specified Sales team role or public group.

A. Update the Sales profile: Profiles control object-level permissions (e.g., the ability to read or edit any account) but do not grant access to specific records owned by other users.

D. Create an owner-based sharing rule: This rule type grants access based on who owns the record, not on the attributes of the record itself, such as its record type.

1. Salesforce Help, "Organization-Wide Sharing Defaults": This document clarifies that OWDs are the first step in securing data. It states, "Organization-wide sharing settings specify the default level of access that users have to each other’s records... Use organization-wide sharing settings to lock down your data to the most restrictive level." This supports option B as the initial action.

2. Salesforce Help, "Create Sharing Rules": This documentation distinguishes between rule types. For criteria-based rules, it states, "Criteria-based sharing rules determine who to share records with based on field values other than ownership." This directly aligns with the requirement to share based on the 'Sales' record type, supporting option C.

3. Trailhead, "Data Security" Module, "Control Access to Records" Unit: This educational module outlines the Salesforce sharing model hierarchy. It explains, "After you've locked down your data with organization-wide defaults, you can use the other record-level security tools to grant access to specific users... Sharing rules are used to extend sharing access to users in public groups, roles, or territories." This confirms the two-step process of setting the OWD (B) and then creating a sharing rule (C).