--- schema_version: "1" id: c06be0ed5f5143a7cc6f9d978f895b33f033c2a26d806c9de9969ee3034c42cd title: Additional Considerations for Troubleshooting Access Issues collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/admin_troubleshoot_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.admin_troubleshoot_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 9291149281673dcdf35aadc98885c1393128e7d9ecb198bb5c71d11d32947c41 description: Review these object-specific considerations and additional features that can affect what your users can see or access. products: - Security - Salesforce Platform release: "264" --- # 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](https://help.salesforce.com/s/articleView?id=platform.networks_secure_community.htm&release=264.0.0&type=5 "Experience Cloud sites help you connect with customers and partners. When building your site, you can use various settings and permissions to protect your data and your customers’ data, and publicly share the site with guest users. Keeping your data secure is a joint effort between you and Salesforce.") 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](https://help.salesforce.com/s/articleView?id=platform.networks_setting_light_users.htm&release=264.0.0&type=5 "Give Experience Cloud site users access to records using sharing sets. A sharing set grants site users access to any record associated with an account or contact that matches the user’s account or contact. You can grant access to records via access mapping, which defines access for each object in the sharing set. Access mappings support indirect lookups from the user and target record to the account or contact. For example, grant site users access to all cases related to an account that’s identified on the user’s contact records. A sharing set applies across all sites that a user is a member of. Record access granted to users via a sharing set isn’t extended to their superiors in the role hierarchy.") and [share groups](https://help.salesforce.com/s/articleView?id=platform.networks_sharing_light_users.htm&release=264.0.0&type=5 "Share groups allow you to share records owned by high-volume Experience Cloud site users with authenticated internal and external users."). 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](https://help.salesforce.com/s/articleView?id=platform.security_sharing_recalculating.htm&release=264.0.0&type=5 "When you make changes to sharing settings, groups, roles, and territories, sharing rules are reevaluated to add or remove access as necessary. You can manually recalculate sharing rules if sharing rule updates have failed or aren’t working as expected."). - 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. #### See Also - [Troubleshooting User Access Issues and Insufficient Privileges Errors](https://help.salesforce.com/s/articleView?id=platform.admin_insufficient_privileges_flowchart.htm&release=264.0.0&type=5 "Review this guidance if you or one of your users is experiencing insufficient or unexpected access for an object, record, field, or feature in Salesforce.")