Access Denied error or the edit options or other folders are missing from the SharePoint library
Why this can happen
- Your diocesan Microsoft account does not have permission to access this SharePoint library, folder or file. If you were sent a link from a colleague, please check with them they have given you the correct permission and, if not, grant you the correct permission. See the following articles:
- This scenario can happen when you are testing a link works to a SharePoint folder or file works. For example an anyone link with password for the Diocesan Meetings Portal. To resolve please continue reading this article...
Scenario 2: Reason you can't edit and/or other folders are missing
Your internet browser session currently has the permission that was granted to the SharePoint link rather than your own diocesan Microsoft account.
Scenario 2: How to tell you are signed in correctly
If you are signed in correctly with your diocesan Microsoft account you should see your name in the top right corner. If it's missing then you are not currently signed in as yourself in your current browser session .
![]() |
![]() |
Not signed in (top right) | Signed in (top right) |
Scenario 2: How to resolve
- If you see the Access Denied message (image top of this page)
- Select the Sign in with the account provided... option underneath and sign in with your diocesan Microsoft account.
- If you are still in the SharePoint library
- Clear your internet browser cache and cookies:
- Microsoft Edge: Go to More Options . . . > Settings > Privacy, search, and services > Delete browsing data > Choose what to clear
-
Google Chrome: Go to More Options . . . > Settings > Privacy and security > Clear browsing data
- Alternatively copy and paste this in your address field: chrome://settings/clearBrowserData
- Select Time range All time
- Select to delete Cookies and Cached images and files
- Select Clear now or Delete data
- Refresh the page and sign in with your diocesan Microsoft account if requested
- Clear your internet browser cache and cookies:
Scenario 2: How to avoid next time
- If testing SharePoint anyone links, use a private / incognito browser session instead:
- If using a link to a meetings portal group, go to the meetings portal directly instead of using the link: