A user reports that they cannot see a specific custom object despite having the correct profile assigned. What is the most likely cause and how would you verify?

The most likely cause for a user not being able to see a specific custom object, even when their profile seems correctly assigned, is a combination of object-level permissions and sharing settings that might be misconfigured or overlooked. Several specific scenarios could be at play. First, while the profile may have the general "Read" permission, the user might not have been given the necessary object-level access through the correct profile setup. For example, the profile may allow users to view a list of custom objects, but not access them. Second, sharing settings could restrict access. Even if a user's profile allows access, the organization-wide default might be set to "Private" for the custom object. If the user does not own the records within the object, nor are they given access via sharing rules, they would be unable to see the records, despite having the general object-level permission. Another possibility is that the visibility settings for the user's record type might have been configured to exclude the user profile from access. Third, the user might not have been granted field-level access. While the object might be visible, specific fields may be hidden. If a necessary required field is hidden, it may cause users not to see the object and its records. Finally, it could be related to the user's role in the Salesforce role hierarchy. If they are in a lower role, and the sharing model is set to grant access to owners and those in the hierarchy, then they will not be able to see records owned by users at higher levels and outside of sharing rules.

To verify the actual root cause, a methodical approach is required. First, navigate to the profile settings for the specific user in question and verify the assigned profile’s object permissions. Confirm that the "Read" permission is explicitly enabled for that custom object, and that the permission is set correctly (if the user needs more access) based on the use case of the custom object. Then, examine the organization-wide default sharing settings for that object. If it's set to "Private," verify if any sharing rules are in place that would give the user access to records of that custom object. The record type visibility settings should be verified if the object uses record types. The profiles that can view the record type should be configured correctly. Checking field-level security settings can confirm that necessary fields are visible for the user’s profile. Finally, also look at role hierarchy and make sure there aren't any sharing rules or settings that would conflict with the user’s role. It's also valuable to examine the user’s sharing access on individual records, particularly if the object’s sharing is governed by a “private” setting. If none of these settings resolve the visibility issue, consider reviewing the user’s login history to identify any anomalies or restrictions. A systematic approach is key to effectively pinpoint and resolve the visibility issue.