Permission & Access Issues

How to Restrict Renaming SharePoint Folders While Allowing Content Edits

Kushani Nimanthika Oct 20, 2026 868 views

Question details

The user needs to prevent users from renaming or moving top-level folders in SharePoint Online while still allowing them to edit, add, and delete the files and subfolders inside them.

How to Restrict Renaming SharePoint Folders While Allowing Content Edits

Product: SharePoint Online
Device & OS: not provided
Scenario: Managing user permissions for client folders within a SharePoint document library to ensure top-level folder structures remain intact.
Observed behavior: Standard SharePoint folder permissions do not natively support this dual requirement, as granting Read access protects the folder structure but simultaneously blocks edits to its internal contents.

Before you start

Ensure you have Site Owner or Full Control permissions in the SharePoint site to modify folder settings and break permission inheritance.

Solution 1Recommended

Break Permission Inheritance and Assign Unique Permissions

Manually break inheritance so you can set the top-level folder to Read-only while granting Edit access specifically to its internal contents.

In SharePoint, files and subfolders inherit permissions from their parent folder by default. To apply different rules to the parent folder and its contents, you must stop inheriting permissions and configure them individually.

Access top-level folder permissions

Navigate to your SharePoint document library, hover over the top-level client folder, click the ellipsis (...), and select 'Manage Access'.

Stop inheriting permissions

Click on 'Advanced' in the Manage Access panel, then click 'Stop Inheriting Permissions' in the top ribbon.

Set top-level folder to Read

Select the relevant users or groups, click 'Edit User Permissions', check the 'Read' permission level, and uncheck 'Edit'. Click OK.

Grant Edit access to contents

Open the top-level folder, select the internal files or subfolders, and repeat the 'Manage Access' > 'Advanced' > 'Stop Inheriting Permissions' process. Then, grant the users 'Edit' permissions for these specific items.

Break Permission Inheritance and Assign Unique Permissions

Testing Required: Always test the permission structure with a standard user account to ensure they can edit documents without being able to rename the parent folder.

Solution 2

Automate Unique Permissions Using PnP PowerShell

For libraries with numerous client folders, use a custom PnP PowerShell script to automate the process of breaking inheritance and applying permissions.

Free Microsoft Office alternative

Experience a Seamless Office Alternative with WPS Office

While SharePoint and Microsoft Office enterprise setups can require complex permission configurations, WPS Office offers a highly compatible, lightweight, and completely free alternative for your daily document creation and editing needs.

1. Download WPS Office: Visit the official WPS Office website and download the free installer for your operating system.
2. Install the application: Run the installer and follow the quick on-screen instructions to set up WPS Office on your device.
3. Open and edit your files: Launch WPS Office and directly open your existing Microsoft Office formats (.docx, .xlsx, .pptx) to start editing immediately.

Fully compatible with Microsoft Word, Excel, and PowerPoint formatsLightweight application that runs smoothly on almost any deviceFamiliar and intuitive user interface for a seamless migrationBuilt-in PDF editing and cloud sharing capabilities

microsoft office alternative - wps office

Frequently Asked Questions

Why does granting Read access to a SharePoint folder block editing its files?

In SharePoint, permission inheritance is enabled by default. This means all files and subfolders inherit the exact permissions of their parent folder. If the parent folder is set to Read-only, everything inside it also becomes Read-only unless you manually break that inheritance.

Is there a limit to how many unique permissions I can set in a SharePoint library?

Yes, Microsoft supports up to 50,000 unique permissions per list or library, but it is highly recommended to keep it below 5,000. Exceeding this soft limit can severely degrade the performance of the library and slow down user access.

Can I use SharePoint groups to manage these unique folder permissions?

Absolutely. It is a best practice to assign unique folder and file permissions to SharePoint groups rather than individual users. This drastically simplifies future permission management, as you only need to add or remove users from the group.

Document & File Issues