Resolve Access Issues for Sales User in Private Sharing Model

Correct Answer: C

Use sharing rules to extend sharing access to users in public groups, roles, or territories.

Sharing rules give particular users greater access by making automatic exceptions to your org-wide sharing settings.

You can do this based on a sharing rule on record ownership or other criteria.

After you select which records to share, you define which groups or users to extend access to and what level of access they have.

Option A is incorrect because the role hierarchy automatically grants record access to users above the record owner in the hierarchy.

Option B is incorrect because field level security controls whether a user can see, edit, and delete the value for a particular field on an object.

Option D is incorrect because organization wide default is baseline settings in Salesforce which specify which records can be accessed by which user and in which mode.

In a private sharing model, only the owner and users above them in the role hierarchy can access the record. If a sales user located at the bottom of the role hierarchy is having issues accessing a type of record they need, there are several ways to give them access, as listed in the options given.

A. Role Hierarchy: The role hierarchy can be adjusted to give the user a higher role in the hierarchy, allowing them to access the record. This can be done by creating a new role for the user, or by moving them to a higher existing role. However, this approach should only be used if the user's job responsibilities require them to have access to the record, as it can compromise the overall security of the private sharing model.

B. Field Level Security: Field Level Security can be used to control which fields are visible or editable for a particular user. This approach can be useful if the user only needs access to certain fields on the record, and not the entire record. However, it does not provide access to the entire record.

C. Sharing Rules: Sharing Rules can be used to extend access to a record to users who would not normally have access based on their role in the hierarchy. This approach allows for more granular control over who has access to the record, and can be based on criteria such as the record owner, record type, or other custom criteria. However, it can be difficult to manage multiple sharing rules and ensure that they do not conflict with each other.

D. Organization-Wide Default: The Organization-Wide Default (OWD) determines the default level of access that all users have to records in the organization. If the OWD is set to private, for example, users will only be able to access records they own or have been granted access to. However, if the OWD is set to public read-only, all users can view all records in the organization, but can only edit their own records. Changing the OWD can have significant implications for the overall security of the private sharing model, and should only be done after careful consideration.

In summary, the best approach to give the sales user access to the record depends on their job responsibilities and the level of access required. In general, sharing rules are the most flexible and scalable approach, but field-level security, role hierarchy, and OWD can also be used depending on the specific use case.