Permission Inheritance Does Not Break on a Subfolder: Fix

You try to break permission inheritance on a SharePoint subfolder, but the option is grayed out or the changes do not apply. This problem occurs when the subfolder inherits permissions from a parent that itself has broken inheritance at a higher level, or when the user lacks the required permission level. This article explains the root cause and provides step-by-step fixes to successfully break inheritance on a subfolder.

Why Permission Inheritance Does Not Break on a Subfolder

SharePoint permission inheritance works from the top of the site collection down to folders and items. When you break inheritance on a folder, that folder becomes a new permission boundary. Any subfolder inside it automatically inherits from that folder, not from the site root. If you try to break inheritance on a subfolder that already inherits from a parent folder with broken inheritance, SharePoint may block the action because the parent’s permissions are not the same as the site’s. This is a common design limitation, not a bug.

Another cause is insufficient permissions. To break inheritance on any folder, you need at least the Full Control permission level on that folder or on the site. If you have Contribute or Read, the “Stop Inheriting Permissions” button is grayed out. Site collection administrators or owners can grant Full Control temporarily.

A less common cause is the “Limited-access user permission lockdown mode” site collection feature. When enabled, this feature restricts user permissions to only the site collection, not subfolders or items. This can prevent breaking inheritance on subfolders even for users with Full Control.

Steps to Fix Permission Inheritance on a Subfolder

1. Check the parent folder’s permission inheritance status
   Navigate to the parent folder that contains your subfolder. Select the folder, click the three dots (ellipsis), and choose Manage access. Look for the message “This folder has unique permissions.” If it does, the subfolder cannot break inheritance because it inherits from this folder. You must first break inheritance on the subfolder’s direct parent, not the site root.
2. Verify your permission level on the folder
   While still in Manage access, click Advanced permissions settings. Check the permissions list for your user account. If you see only Contribute or Read, request Full Control from a site owner. Without Full Control, the “Stop Inheriting Permissions” option remains disabled.
3. Break inheritance on the subfolder
   Once you have Full Control and the parent folder has unique permissions, navigate to the subfolder. Click the three dots and select Manage access. Click Stop Inheriting Permissions. If the button is still grayed out, proceed to the next step.
4. Disable “Limited-access user permission lockdown mode”
   Go to Site Settings (gear icon) > Site collection features. Scroll down to Limited-access user permission lockdown mode. Click Deactivate. This removes the restriction that blocks permission changes on subfolders. After deactivating, return to the subfolder and try breaking inheritance again.
5. Use SharePoint Designer as an alternative method
   Open SharePoint Designer 2013 (free from Microsoft). Connect to your site. In the left navigation, click Site Objects > All Files. Browse to the subfolder. Right-click it and choose Manage Permissions. Click Stop Inheriting Permissions. This bypasses some browser-level restrictions. Note that SharePoint Designer is deprecated but still works for these tasks on SharePoint Server 2019 and SharePoint Online.
6. Use PowerShell to break inheritance
   Open SharePoint Online Management Shell as administrator. Run: Connect-SPOService -Url https://yourtenant-admin.sharepoint.com. Then run: Set-SPOSite -Identity "https://yourtenant.sharepoint.com/sites/yoursite" -DenyAddAndCustomizePages $false. After that, use: Set-SPOFolder -Site "https://yourtenant.sharepoint.com/sites/yoursite" -Web "yourweb" -List "Documents" -Identity "SubfolderName" -UniquePermissions $true. Replace URLs and names with your own. This forces inheritance to break.

If SharePoint Still Has Issues After the Main Fix

“Stop Inheriting Permissions” button is missing entirely

If you do not see the button at all, the subfolder may be inside a document library that has its own permission inheritance settings. Check the library settings: go to Library settings > Permissions for this document library. If the library has unique permissions, you must break inheritance on the library first, then on the subfolder. The library inherits from the site, and the subfolder inherits from the library.

Breaking inheritance succeeds but changes do not save

This typically happens when the user has been granted Full Control through a SharePoint group that is not the site Owners group. For example, if you are added as a member of the “Site Members” group but that group has Contribute, and you are also added directly to the folder with Full Control, the folder’s permission changes may not apply. Remove yourself from the conflicting group and add yourself only with the needed permission level directly on the folder.

Error “Sorry, something went wrong” when breaking inheritance

This error often occurs when the site collection storage limit is reached. Check storage in the SharePoint admin center: Admin centers > SharePoint > Active sites > select your site > Storage limit. If storage is full, free up space by deleting old versions or files, then retry breaking inheritance.

Item	User Permissions	Admin Actions
Check parent folder inheritance	Full Control on parent folder	Browse to parent folder > Manage access > check for unique permissions
Verify user permission level	Full Control on site or folder	Advanced permissions settings > view permission level for user
Disable lockdown mode	Site collection admin	Site Settings > Site collection features > deactivate Limited-access user permission lockdown mode
Use SharePoint Designer	Full Control on site	Right-click subfolder > Manage Permissions > Stop Inheriting Permissions
Use PowerShell	SharePoint admin role	Run Set-SPOFolder with -UniquePermissions $true

You now have the knowledge to identify why permission inheritance does not break on a subfolder and apply the correct fix. Start by checking the parent folder’s inheritance status and your permission level. If the standard method fails, use the “Limited-access user permission lockdown mode” deactivation or PowerShell as a workaround. For ongoing management, consider using SharePoint admin center’s permission reports to audit inheritance across your site.