logo
search
Permission & Access Issues

Fix SharePoint “Sorry, You Cannot Access This Document” Error

Partner EditorPartner Editor Oct 12, 2026 869 views

Question details

The user is unable to open a shared SharePoint link after permission changes, receiving an access denied message even when using an “Anyone with this link” URL.

How to Fix the SharePoint “Sorry, You Cannot Access This Document” Error
Product
SharePoint
Device & OS
not provided
Scenario
Clicking on a shared document link in SharePoint after the file's permissions were recently updated or modified.
Observed behavior
The browser displays a “Sorry, You Cannot Access This Document” error, although the link may sometimes load successfully in an Incognito or InPrivate browsing window.
Before you start

Ensure you have the exact shared link provided by the document owner and verify that your Microsoft 365 account credentials are up to date.

Solution 1Recommended

Clear Browser Cache and Sign In Again

Clearing cached data removes conflicting authentication tokens that might be blocking your access to the document.

Often, SharePoint permission errors occur because your browser has stored an outdated access token. Even if your permissions were recently updated, the browser continues to pass the old, invalid credentials to Microsoft 365.

1
Clear Browsing Data

Open your web browser's settings menu (usually accessible via the three dots in the top right corner). Navigate to Privacy and Security, select 'Clear browsing data', and ensure that 'Cookies and other site data' and 'Cached images and files' are checked. Click 'Clear data'.

2
Sign In to Microsoft 365

Go to the Microsoft 365 portal (portal.office.com) and sign in with your authorized account credentials. Make sure you select 'Keep me signed in' if prompted.

3
Open the SharePoint Link

Once fully logged in to the portal, click the shared document link again or paste it directly into the same browser window's address bar to test your access.

Clear Browser Cache and Sign In Again
Quick Workaround: If you do not want to clear your cache immediately, try opening the link in an InPrivate (Edge) or Incognito (Chrome) window to bypass stored cookies.
Free Microsoft Office alternative

Try WPS Office for Hassle-Free Document Sharing

If complex SharePoint permission errors and browser caching issues are slowing down your workflow, WPS Office offers a simplified, lightweight alternative. Enjoy seamless local editing and easy cloud-based sharing without the complicated backend permission struggles.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install WPS Office: Run the downloaded installation file and follow the straightforward on-screen prompts to set up the software.
  3. 3. Create and Share: Open WPS Office, create or open your document, and use the 'Share' button in the top right corner to generate an easily accessible link.
Highly compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight architecture ensures fast installation and smooth performance.Built-in cloud sharing features that are simple to configure and manage.Familiar user interface makes migrating from Microsoft Office effortless.Completely free to use for your daily document processing needs.
microsoft office alternative - wps office

Frequently Asked Questions

Why does an 'Anyone with this link' SharePoint URL give an access denied error?

This usually happens when your browser's cached credentials conflict with the access token provided by the link. Clearing your browser cookies and cache, or using an Incognito window, typically resolves this.

What are HAR logs and why does Microsoft Support need them?

HAR (HTTP Archive) logs record the interaction between your web browser and a website. Microsoft Support uses them to analyze network requests and pinpoint exactly where the backend authentication or permission check is failing in SharePoint.

Can I fix backend SharePoint permission errors myself?

No. If standard troubleshooting like clearing the cache or using a private browsing window fails, only a Microsoft 365 administrator has the required privileges to investigate backend settings or escalate the issue to Microsoft Support.