SharePoint hands you "You don't have permission to access this page." There's no detail, no help link, just a brick wall and a "Request access" button that may or may not actually do anything. Before you file a ticket with IT and wait three days, you can diagnose exactly where the problem is in about ten minutes. Better still, you can turn a vague "I can't access SharePoint" complaint into a precise request your admin can fix in five.
SharePoint permissions: the six layers
SharePoint permission errors don't all mean the same thing. They can originate from any of six different layers — and the same generic error message comes up regardless of which one failed.
- Tenant level: your account doesn't have a license for SharePoint at all.
- Site collection: you don't have access to this site.
- Site: you have access to the site collection, but not this specific site within it.
- Library or list: you can see the site, but this library has its own custom permissions that exclude you.
- Folder: you can see the library but a specific folder has unique permissions.
- File: even more granular — a single file has been individually restricted.
Narrowing down which layer is the actual problem is the whole game. Once you know that, the fix becomes obvious — and you can explain to your admin exactly what's wrong instead of saying "SharePoint isn't working."
Step 1: Confirm you have basic SharePoint access
Go to your tenant root: https://<yourcompany>.sharepoint.com (replace with your real tenant name).
- Does it load? You have tenant-level access. The problem is below this layer — keep going.
- Get a "no access" or sign-in loop? Your account is either unlicensed for SharePoint or has been disabled. That's an admin problem; file the ticket here and stop.
Step 2: Try the parent site URL
Take the URL of the page that's denying you, and trim it back to the site root. If you can't access:
https://yourcompany.sharepoint.com/sites/marketing/SitePages/campaign-2026.aspxTry just:
https://yourcompany.sharepoint.com/sites/marketing- Loads fine? You have site-level access. The problem is below — a library, folder, or file with custom permissions.
- Same denial? You're missing access to the site itself. The admin needs to add you to one of the site's permission groups.
Step 3: Walk up the URL piece by piece
If a specific document is failing but the site root loads, try intermediate URLs to find exactly where the wall is.
For:
https://yourcompany.sharepoint.com/sites/marketing/Documents/Campaign 2026/strategy.docxTry in order:
- Just the library:
/sites/marketing/Documents - The folder inside the library: navigate from the library view.
- The file itself.
Whichever level first denies you is the level with custom permissions. Note that level. That's the precise information your admin needs.
Step 4: Check who else has access
If you can get into the library or folder, but not a specific file, the file owner has restricted it explicitly. SharePoint shows you who does have access — useful both for understanding what's going on and for finding someone to ask.
- Find the file in the library list view.
- Click the three-dot menu next to it → Manage access.
- Look at the list of people with access. Are they all from one team? That's a clue about what group should have been added (and you weren't).
If you can't even open Manage access, the restriction is at a level above the file. Move up.
Step 5: Identify the right owner to ask
You need to know who can grant you access. SharePoint sites have owners; libraries inherit from sites; custom permissions can be delegated.
- Open the site root in SharePoint.
- Click the gear icon (top right) → Site contents.
- Click the gear icon → Site permissions.
- You'll see a list of groups (often Site Owners, Site Members, Site Visitors).
- Click Site Owners to see who's in that group.
Those are the people who can grant you access without admin intervention. Often you'll recognize a colleague's name on the list, and a quick Teams message is enough to get unblocked. Way faster than a ticket.
Step 6: Request access correctly
SharePoint has a built-in "Request access" button on most denial pages. Click it, write what you need and why, submit. The catch: the request goes to a specific list of approvers, which might be the site owners list or might be a separate distribution list. If the page doesn't have a request button at all, or your request sits unanswered for days, fall back to direct contact.
A request that gets approved fastest includes:
- The exact URL you couldn't access.
- What you need to do (read, edit, share with someone else).
- How long you need it (a specific timeframe is more likely to be approved than "ongoing").
Special case: conditional access blocking you
If you can access SharePoint on one device but not another, this is almost certainly conditional access — your organization has a policy that only allows SharePoint from compliant or trusted devices. The permission error wording can be misleading; it looks identical to a real permission denial.
Tell-tale signs:
- Works on your work laptop but not your phone or home machine.
- Works in the managed SharePoint mobile app but not in a browser.
- Works on the corporate network but not on hotel Wi-Fi.
If you see these patterns, ask IT for a CA exception or use a compliant device. There's nothing wrong with the file permissions themselves — your device just isn't allowed in.
Special case: external sharing turned off
If you're trying to access SharePoint at a company that isn't your own (a vendor, partner, or client), the site may have external sharing disabled for your domain. The owner can re-share the file with your email address specifically, but they may need to enable external sharing at the site or tenant level first.
Tell them: "external sharing for my domain might be off — please check site settings and confirm that guests outside the organization are allowed."
What to tell IT when you do escalate
A useful support ticket includes all of this:
- The exact URL you can't access.
- The exact error message and a screenshot.
- What you've already confirmed: "I can access the site root but not Documents/Campaign 2026."
- Names of colleagues you've verified do have access.
- Whether the device matters (works on work PC, not personal).
Compared to "I can't access SharePoint," this lets the admin fix the issue in minutes instead of starting from scratch. They'll also think more of you for sending a useful ticket.
The bottom line
Most "you don't have permission" errors are solvable in a chat message rather than a ticket — once you know which layer is denying you and who owns that layer. The URL-walking technique gives you both. Spend the 10 minutes; you'll often be back in within the hour.
And the next time a coworker grumbles about SharePoint permission errors, you'll know exactly what to ask them to check.