Why Can't I Access This SharePoint Site? "Access Denied" and "You Need Permission" Explained
"Access denied" is the most common thing people report about SharePoint, and it has more than one cause. The good news: where you see the message, and what it says, usually narrows it down quickly. This guide goes through the real causes in the order worth checking, with the fix for the person locked out and for the admin who has to sort it out. For the full list of common errors, see SharePoint error messages explained.
Match the message to the cause
| What you see | Most likely cause | Jump to |
|---|---|---|
| "You need permission to access this site" with a Request access option | You aren't in a group, team or list that grants access | Cause 1 and 2 |
| The right site, but the wrong account is signed in | Personal or other-tenant account | Cause 3 |
| "Access Denied. Due to organization policy, you can't access this resource from this untrusted device." | Unmanaged-device policy | Cause 4 |
| A page about your organization's policies, even though you were a member before | Restricted Access Control | Cause 5 |
| A 403 error, or a redirect to another page, for everyone | Site locked with NoAccess | Cause 6 |
| A link that worked last month now fails | Wrong sign-in, expired guest, or a policy change | Cause 7 |
Cause 1: you were never added, or your access was removed
The plain answer is the most common one. Your account isn't in the site's Owners, Members or Visitors group, in the Microsoft 365 group behind a team site, or on a list for the library or folder. People also lose access when they change roles and a group membership is cleaned up.
- If you're the person locked out: use the Request access button if it appears, and name the site and why you need it. The request goes to the site owners (or an address they set).
- If you're the admin: open Check Permissions on the site and enter the person's name to see exactly how, or whether, they have access.
Cause 2: the group they relied on changed
Access often comes from a group, not from the person. If someone left a team, was removed from a Microsoft 365 group, or sat in a security group that changed, their access follows. Two cases cause the most confusion:
- Private and shared channels. Each has its own SharePoint site, and only channel members can reach it. Being in the team isn't enough. See SharePoint groups vs Microsoft 365 groups vs Teams.
- Read-only access on a team site. Microsoft 365 groups don't have a view-only role, so a reader has to be added to the site's Visitors group directly.
To see every route a person has, run a permissions report for that user.
Cause 3: the wrong account
This catches more people than anyone admits. The browser is signed in to a personal account, a second work account, or another tenant, and SharePoint correctly says that account has no access. Check the picture in the top-right corner, sign out of everything, and sign in again with the work account. A private browser window is a quick test. This is also the first thing to check when a link sent to one email address is opened under another.
Cause 4: your device isn't trusted
Admins can block or limit access from devices that aren't compliant or hybrid-joined. Per Microsoft's unmanaged-device guidance, a blocked user sees:
Access Denied. Due to organization policy, you can't access this resource from this untrusted device.
With the milder limited, web-only access option, users on unmanaged devices get browser-only access with no download, print or sync, and they can't open content through apps, including the Office desktop apps. Microsoft also warns that one limited-access file setting can cause unexpected "Access Denied" errors with PDFs and images, because they may have to be downloaded to display.
- User fix: use a managed or compliant device, or the browser if only web access is allowed.
- Admin check: Microsoft says a policy change can take up to 24 hours and won't affect users who are already signed in, so test with a fresh sign-in. Teams may show a different symptom than SharePoint when the Files tab is blocked.
Cause 5: Restricted Access Control
Restricted Access Control (a SharePoint Advanced Management feature) limits a site to members of chosen groups. Per Microsoft's documentation, users not in the control group can't open the site or its content, even if they had prior permissions or a shared link. To get in, a person needs both permission to the content and membership of the control group. Adding someone to the group alone doesn't grant access.
- Channel sites are separate. Microsoft says a policy on a team-connected site doesn't automatically apply to its private or shared channel sites, which need their own setting.
- Admin check: run the access-denials report to see who is being blocked and where, and set the tenant's "Learn more" link so denied users know whom to ask.
Background on the feature is in our guide to Restricted Access Control and overshared sites.
Cause 6: the site is locked
An admin can lock a site with PowerShell. Per Microsoft's lock and unlock page:
- ReadOnly stops people adding, changing or deleting content, and the site shows a maintenance message.
- NoAccess blocks everyone. If a redirect URL is configured, people land there. Otherwise they see a 403 error.
An admin unlocks it with Set-SPOSite -Identity <url> -LockState Unlock. Microsoft notes that the command doesn't work for a site that was closed and made read-only through a site closure policy. Also rule out a deleted site: a site in the deleted sites list gives the same "it's gone" feeling.
Cause 7: a sharing link or guest account stopped working
Links are a separate way in. They fail for a few reasons: the person opens a "specific people" link while signed in as a different address, the site's sharing settings changed, the site is now under Restricted Access Control, or an external guest's account expired. Microsoft's guest expiration guidance says that sharing links don't deactivate on their own, and that a guest loses access when their guest credentials expire. If a guest's access lapsed, an admin can extend it. For what each link type allows, see sharing links explained.
The admin checklist
- Get the exact message, the address, the time and the account used.
- Check the site exists and its lock state.
- Run Check Permissions, or a permissions report, for the person.
- Confirm group, team and, for private or shared channels, channel membership.
- Look at the Microsoft Entra sign-in log and the device policy.
- If the site uses Restricted Access Control, confirm control group membership.
- Fix it in the right place, then have the person sign in fresh and retest.
If you do this often, a permissions report saves the most time, because it shows every group, link and unique permission in one view instead of five admin screens. See how to see who has access to a SharePoint site, or use the free Smart Permissions web part to export it to Excel.
Need help with a tenant full of access problems?
Recurring "I can't get in" tickets usually mean permissions have grown without a plan. Our permissions audit finds the causes and cleans up the structure, or you can get in touch.
Related
Get your first result in about 10 minutes
Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.
- Download the .sppkg package from the latest release.
- Upload it to your tenant App Catalog.
- Add the web part to a SharePoint page.
Email me when a new release ships
No marketing spam. One short email when a new release ships. You can unsubscribe anytime.
Frequently asked questions
Why does SharePoint say "you need permission to access this site"?
Your account isn't in a group, team or permission list that grants access, or the access you had was removed or came from a group that changed. Request access from the site owner, or check you're signed in with the right account.
Why can I open the site on my laptop but get access denied on my phone?
Your organization may block or limit access from devices that aren't managed or compliant. Microsoft's block message reads: "Access Denied. Due to organization policy, you can't access this resource from this untrusted device." Use a managed device or ask your admin.
I'm a team member, so why can't I open a private channel's files?
A private channel has its own SharePoint site, and only members of that channel can reach it. Team membership alone doesn't grant access.
A site returns a 403 error for everyone. What happened?
The site may be locked with the NoAccess lock state. Microsoft says users then see a 403 error, or get redirected to a URL the admin set. An admin can unlock it with Set-SPOSite and the Unlock state.
Why did a sharing link stop working?
Common causes are signing in with a different address than the link was sent to, a link or site-level policy that now blocks it, a site under Restricted Access Control, or a guest account that expired. Microsoft notes that sharing links don't deactivate on their own, and a guest loses access when their guest credentials expire.
How can an admin see who was denied by Restricted Access Control?
Microsoft provides an access-denials report. Run Start-SPORestrictedAccessForSitesInsights with -ActionsBlockedByPolicy in SharePoint PowerShell, then fetch the results to see recent denials, top users and top sites.
Was this page helpful?
One click. No form, no email address.
Missing something in SharePoint Smart Permissions? Feature requests and bug reports go straight to the developer on GitHub — no account needed to read, free account to post.
Request a featureRelated tool
SharePoint Smart Permissions
Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.
Keep reading
How to find external users in SharePoint (free report)
Guest access accumulates quietly: a shared link here, a project team there. Here's how to produce a defensible list of every external user on a site — and what they can actually reach — without PowerShell.
SharePoint Groups vs Microsoft 365 Groups vs Teams: How Access Really Flows
Three kinds of groups, one site. Which one controls access on a team site, a communication site and a Teams channel, where to add people, and the mistakes that cause missing-file tickets.
How to Deploy an SPFx Web Part to the App Catalog
The short admin guide to the SharePoint app catalog: where it lives, who can use it, and the four steps to get an SPFx web part onto a page.
Want a second set of eyes?
Get a SharePoint permissions audit from our team
We review who can see what across your sites, flag oversharing before you roll out Copilot, and help you put a cleanup plan and governance in place.
About the author
Sean Regan
SharePoint & Microsoft 365 consultant with 20+ years of hands-on experience building SPFx web parts, migration tooling and tenant-grade automation. Maintainer of the open-source SharePoint Smart Solutions suite.
