Site Collection Admin Cannot Access Settings: Root Cause and Fix

You are a site collection administrator in SharePoint, but when you try to open site settings, you see an access denied error or the settings page is missing. This problem typically occurs because the site collection administrator does not have explicit permissions through the site’s permission structure, or because of a permission inheritance break combined with a missing user information list entry. This article explains the exact root cause of this access issue and provides a step-by-step fix to restore full administrative access to site settings.

Why the Site Collection Admin Cannot Access Settings

The root cause is a mismatch between the site collection administrator designation in the SharePoint admin center and the actual permission state of the user within the site. When you add a user as a site collection administrator, SharePoint grants that user full control at the site collection level. However, this permission is stored in two places: the site collection properties in the content database and the site permission list. If the user information list, also known as the UserInfo list, does not contain an entry for the administrator, the permission assignment fails silently. This leaves the user without any effective permissions, even though they appear as a site collection administrator in the admin center.

Another frequent cause is permission inheritance being broken on the root web. When a site owner breaks inheritance on the top-level site and removes the site collection administrator from the permission list, the admin loses access to settings. The admin center still shows the user as a site collection administrator, but that designation only applies to the site collection root web. If the root web is broken and the user is removed, they cannot reach settings pages.

A third cause involves the SharePoint app pool or timer job delays. After adding a user as a site collection administrator, the change must propagate through the SharePoint Timer Service. If the timer job does not run or is delayed, the user will not have the correct permissions for up to 24 hours. During that window, the user sees access denied when trying to open site settings.

Steps to Fix Site Collection Admin Access to Settings

1. Verify the user is listed as a site collection administrator
   Go to SharePoint admin center > Active sites > select the site. In the panel, check the Site collection administrators section. If the user is not listed, add them and wait 15 minutes for propagation. If the user is listed, proceed to the next step.
2. Check effective permissions at the root web
   Navigate to the site collection root web. Select Settings gear > Site permissions > Check permissions. Enter the user’s email address. The result must show Full Control. If it shows nothing or a different permission level, the user is not properly assigned.
3. Restore permission inheritance on the root web
   If the root web has broken inheritance, go to Site permissions > Permission levels > select the broken inheritance warning. Click Delete unique permissions to restore inheritance from the parent site collection. This action re-adds the site collection administrator with full control. Note that this removes any custom permissions on the root web.
4. Add the user to the User Information List using PowerShell
   If the user is missing from the UserInfo list, use SharePoint Online Management Shell or PnP PowerShell. Run the command: Set-SPOUser -Site -LoginName -IsSiteCollectionAdmin $true. This forces the user to be added to the UserInfo list and grants full control.
5. Run the SharePoint timer job manually
   In SharePoint on-premises, go to Central Administration > Monitoring > Timer Jobs. Find the job named “Site Collection Administrator Promotion.” Run it immediately. For SharePoint Online, wait up to 24 hours or contact Microsoft support to trigger the job.
6. Clear the browser cache and try a private window
   Open a new InPrivate or Incognito window. Navigate to the site collection URL. Sign in with the administrator account. Try accessing Site settings again. Cached credentials or stale permissions can cause false access denied errors.

If SharePoint Still Has Issues After the Main Fix

Site collection admin sees access denied only on subsites

The site collection administrator designation applies only to the root web. If a subsite has broken inheritance and the user was not explicitly added to that subsite’s permissions, they cannot access settings on that subsite. To fix this, either restore inheritance on the subsite or add the user to the subsite permissions with Full Control level.

User is listed as admin but cannot see the settings gear icon

This usually indicates the user is a member of a SharePoint group that has limited permissions, and the group permission overrides the site collection admin designation. Check if the user is also a member of a site group like “Visitors” or “Members.” Remove the user from all other groups except the site collection administrators group. Then run the check permissions tool again.

Access denied after moving a site collection

When you move a site collection between content databases or to a different tenant, the site collection administrator mapping can break. After the move, re-add the user as a site collection administrator in the SharePoint admin center. Then run the PowerShell command from step 4 to ensure the UserInfo list is updated.

User cannot access site settings in SharePoint Online after a license change

If the user’s Microsoft 365 license was removed and then re-added, the user object may lose its site collection admin status. Reassign the site collection administrator role in the SharePoint admin center. Wait for the change to propagate, which can take up to 24 hours. If the issue persists, remove the user from all site groups and add them back as a site collection administrator.

Site Collection Admin vs Full Control Permission Level: Key Differences

Item	Site Collection Admin	Full Control Permission Level
Scope	Entire site collection including all subsites	Only the specific site or subsite where assigned
Access to root web settings	Always granted	Only if assigned at root web
Can manage site collection features	Yes	No, unless also a site collection admin
Visible in SharePoint admin center	Yes, under site collection administrators	No, only in site permissions
Survives permission inheritance break	Yes, at root web level	No, must be added explicitly

Now you can diagnose and fix the site collection admin access issue using the verification steps and PowerShell commands provided. Start by checking the user in the SharePoint admin center and running the check permissions tool. If the problem persists, restore inheritance or update the UserInfo list. For ongoing management, consider using the SharePoint admin center to assign site collection administrators rather than relying on group permissions.