You are here:
Additional Considerations for Troubleshooting Access Issues
Review these object-specific considerations and additional features that can affect what your users can see or access.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| The available user and data management options vary according to which Salesforce edition you have. |
- For objects with built-in sharing, it’s important to make sure that you correctly identified which object is causing the issue because it can be unclear. For example, if a user is manually sharing a case, the receiving user must have at least Read access to the associated parent account, or the sharing user must have the ability to also share the account. If you’re troubleshooting an error, you must check access for the parent account, not just the child case.
- Be mindful of automation features or triggers tied to certain actions that can cause access issues. For example, a user gets an error when attempting to edit a custom object record. It’s possible that the user is missing permissions for that custom object, but consider other possibilities if this object doesn’t appear to be the issue. For instance, editing the custom object can trigger a workflow that involves additional objects that the user doesn’t have access to. Or, if record ownership is changed inside the workflow, the user can lose access.
- Private contacts, or contacts that aren’t associated with an account, aren’t impacted by your sharing configuration. Only the owner of the contact, administrators, and users with the correct permissions can view it, and sharing rules don’t apply.
- Private opportunities, or opportunities where the Private field is true, aren’t impacted by your sharing configuration. Only the owner of the opportunity, administrators, and users with the correct permissions can view it, and sharing rules don’t apply.
- Sharing works differently for some external users. For example, unauthenticated guest users can only receive access from guest user sharing rules. Their external org-wide defaults are always set to private, and they can’t receive access to records through manual shares. High-volume users don’t have roles, and their sharing is controlled by sharing sets and share groups. Review the related doc on Experience Cloud sharing features for more information if you’re troubleshooting for external users.
- If you exhaust all sharing rule troubleshooting options, and access still isn’t as expected, you can consider recalculating an object’s sharing rules. Because recalculating sharing rules can take a while, you only want to initiate a manual recalculation in case of errors. For more information, see Recalculate Sharing Rules Manually.
- If Profile Filtering is enabled, users can’t see profile names unless they have the View All Profiles user permission. Enabling this option can prevent users without this permission from loading records with fields that reference profile names.
Did this article solve your issue?
Let us know so we can improve!
