As a SharePoint site owner, you may need to restore permission inheritance after breaking it for specific items or libraries. The standard restore process removes all unique permissions and replaces them with the parent site’s permissions. This can accidentally remove site owners who were added directly at the item or library level. You need a way to restore inheritance while keeping critical owner accounts intact.
The root cause of losing owners is that SharePoint treats all direct permissions as unique when inheritance is broken. When you restore inheritance, SharePoint deletes all those direct permission entries, including owner accounts that were granted access only at that level. This article provides a practical checklist to restore permission inheritance without losing your designated owners.
You will learn the exact steps to identify owner accounts, back them up, restore inheritance, and then re-add the owners if needed. The checklist covers both SharePoint sites and document libraries. Follow these steps to avoid accidental lockouts and maintain proper site governance.
Key Takeaways: Restore Permission Inheritance Without Losing Owners
- Site Settings > Site Permissions > Check Permissions: Use this tool to verify which users have direct access before restoring inheritance.
- Export site permissions to Excel: Create a backup of all current permissions before making any changes.
- Restore inheritance and then re-add owners: The only safe method is to restore inheritance and immediately grant owner permissions to the correct accounts.
Why Restoring Permission Inheritance Removes Owners
SharePoint uses a permission inheritance model. By default, a site collection, site, library, or list inherits permissions from its parent. When you break inheritance, SharePoint creates a unique permission set for that item. All direct permission entries are stored only at that level.
When you restore inheritance, SharePoint deletes the unique permission set and the item reverts to using the parent’s permissions. Any user or group that had direct access only at that item level loses access. If a site owner was added directly at a subsite or library level, that owner disappears after restoration.
How SharePoint Stores Owner Permissions
Site owners are stored in the associated Microsoft 365 group or in the site’s owner group. If you break inheritance on a subsite and add a new owner directly to that subsite, that owner does not appear in the parent site’s owner list. The owner exists only in the subsite’s unique permission set. Restoring inheritance removes that entry.
Common Scenarios Where Owners Are Lost
This problem occurs most often when you break inheritance on a project subsite and add a project manager as an owner. Later, when you restructure the site hierarchy and restore inheritance, that project manager loses owner access. The same issue happens with document libraries where you break inheritance and add an external stakeholder as an owner.
Steps to Restore Inheritance While Keeping Owners
Follow these steps in order. Do not skip any step. Each step is designed to prevent accidental loss of owner access.
- Identify all users and groups with direct access
Go to the site, library, or list where inheritance is broken. Select the gear icon and choose Site Permissions. Click Advanced Permissions Settings. On the Permissions tab, review the list of users and groups. Note every entry that has Full Control or Owner level access. Write down their names or take a screenshot. - Export the current permission list
In the same Permissions page, click the gear icon and select Site Permissions. Click Advanced Permissions Settings. On the ribbon, click the Library tab or List tab. Click Export to Excel. Save the file. This gives you a complete record of all permission entries including owner accounts. - Check if owners are also in the parent site’s owner group
Navigate to the parent site. Go to Site Permissions > Advanced Permissions Settings. Look at the site owners group. Compare the members with the owners you identified in step 1. If the owner is already in the parent site’s owner group, they will retain access after inheritance is restored. If they are not in the parent group, you need to add them after restoration. - Restore permission inheritance
Return to the site, library, or list where inheritance is broken. Go to Site Permissions > Advanced Permissions Settings. On the Permissions tab, click Delete Unique Permissions. A confirmation dialog appears. Read it carefully. It warns that all unique permissions will be removed. Click OK. Inheritance is now restored. - Re-add any owners that were not in the parent group
Go to the site where inheritance was restored. Select the gear icon and choose Site Permissions. Click Add Members. Type the name of each owner you identified in step 1. Assign the Full Control permission level. Click Share. The owner now has access again. - Verify owner access after restoration
Use the Check Permissions tool. In Site Permissions, click Advanced Permissions Settings. On the ribbon, click Check Permissions. Type the owner’s name. Click Check Now. The result shows which permissions the user has. Confirm they have Full Control.
If SharePoint Still Has Issues After the Main Fix
Owner Cannot Access the Site After Restoration
If an owner cannot access the site after you restored inheritance, the owner was not added to the parent site’s owner group. Follow step 5 again. Add the owner directly to the site’s owner group. If the owner still cannot access, check if the user account is disabled or if the site is in read-only mode.
Permission Inheritance Button Is Grayed Out
The Delete Unique Permissions button is grayed out when you do not have Full Control permissions at that level. Only site owners can restore inheritance. If you cannot click the button, ask a global admin or another site owner to perform the action.
Restoring Inheritance Removed Other Important Users
If you lost access for users other than owners, use the Excel export you created in step 2 to identify who was removed. Add those users back using the same Add Members process. For large numbers of users, consider adding them to a SharePoint group instead of individually.
Parent Site Permissions Are Also Broken
If the parent site itself has broken inheritance, restoring inheritance on a child item will not fix the parent’s permissions. You must restore inheritance at the parent site first. Use the same steps but start at the site collection level.
Restoring Inheritance on a Library vs a Site: Key Differences
| Item | Restoring Inheritance on a Site | Restoring Inheritance on a Library |
|---|---|---|
| Permission scope | Affects all lists, libraries, and pages within the site | Affects only the specific library |
| Owner impact | Removes all direct owners added at the site level | Removes all direct owners added at the library level |
| Re-add owners | Add owners to the site’s owner group | Add owners to the library’s unique permissions or use the site’s owner group |
| Export method | Site Permissions > Export to Excel | Library Settings > Permissions for this document library > Export to Excel |
| Restoration button | Delete Unique Permissions in Site Permissions | Delete Unique Permissions in Library Permissions |
Use the table above to choose the correct restoration path. The steps are identical, but the navigation differs. For a library, you access permissions through Library Settings instead of Site Settings.
Now you can restore permission inheritance on any SharePoint site or library without losing owner access. Always export your current permissions first and verify which owners are already in the parent site’s group. After restoration, re-add any missing owners immediately. As an advanced tip, consider using SharePoint groups instead of individual user permissions. Groups simplify future inheritance restorations because you can add or remove group members without touching the permission structure.