Knowledge Base / Accounts / SharePoint Permissions and Inheritance Problems
Problem
Users get access denied messages, cannot open a document, or see missing files in SharePoint even though they should have permission.
Permission issues are often caused by broken inheritance, incorrect group membership, or a copied library requiring a refresh of rights after a migration or folder change.
Symptoms to check
- A file or folder opens for one user but not another.
- A site or document set appears accessible but returns access denied.
- Newly added users cannot see content that should be visible.
Possible causes
- Permission inheritance was broken at the library or folder level.
- Security groups changed but rights were not updated on the target site.
- The user is a member of the wrong group or has conflicting access settings.
Resolution
- Confirm the user account is in the correct Microsoft 365 group, SharePoint group, or permission role for the site and library they are trying to access.
- Check whether the library, folder, or file has unique permissions. Review whether permission inheritance was intentionally broken or accidentally reset.
- Compare the effective access for the user and note whether the permissions are applied at the site, library, or item level.
- Reset the permission inheritance if the inherited structure is correct, or grant the proper permission level if it was intentionally customized.
- Have the user refresh the browser or reconnect to SharePoint and test access to a sample file before closing the issue.
Prevention and preparation
- Document the approved SharePoint permission model for each site.
- Keep group membership aligned with role-based access and avoid unnecessary local permissions.
- Review inheritance changes before migrating or copying content between sites.
Related guides
Still not fixed? Include the site name, library, user account, and the permission level currently assigned when you escalate the issue.
Submit a ticketLast reviewed: October 2026