Salesforce Sharing and Visibility Certification Practice Exam

What reason explains why an object might be excluded from the list of available objects in a Sharing Set?

1. The object is a custom object and therefore not available for a sharing set.

2. The object's Organization-Wide sharing setting is set to Public Read/Write.

3. The object's Organization-Wide sharing setting is set to Private.

4. The custom object does not have a lookup to Accounts or Contacts.

The correct answer is: The object's Organization-Wide sharing setting is set to Public Read/Write.

The reason an object might be excluded from the list of available objects in a Sharing Set is due to the Organization-Wide sharing settings. When the sharing setting for an object is configured to Public Read/Write, it indicates that all users can view and edit all records without requiring the additional use of a Sharing Set to grant access. This makes the creation of a Sharing Set unnecessary for such objects because the permissions are already sufficiently broad. Thus, the object will not appear in the Sharing Set configuration, as there would be no need for that extra level of sharing when access is already granted at the organizational level. In contrast, if an object's sharing setting is set to Private or if it does not have a lookup relationship to Accounts or Contacts, it would indeed be visible for inclusion in a Sharing Set to facilitate specific sharing needs. Custom objects, regardless of whether they are custom or standard, can be part of Sharing Sets as long as their settings allow for it, leading to the exclusions primarily being driven by the public versus private sharing designation.