logo
search
Permission & Access Issues

How to Ensure Consistent Read-Only Permissions on a SharePoint Site

Bushra ParveenBushra Parveen Sep 27, 2026 870 views

Question details

The user needs to enforce strict read-only access across a SharePoint site to prevent users from accidentally editing or deleting content.

How to Ensure Consistent Read-Only Permissions in SharePoint
Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Managing site-wide access and auditing sharing links for document libraries.
Observed behavior
Users who are assigned read-only access are still able to edit or delete files due to unique folder permissions or active edit-level sharing links.
Before you start

Ensure you have Site Owner or SharePoint Administrator privileges before making changes. It is recommended to notify your team before modifying access levels to prevent sudden workflow disruptions.

Solution 1Recommended

Remove Unique Permissions from Libraries and Folders

Eliminate permission breaks to ensure that all folders and files inherit the site-wide read-only settings.

Permissions normally inherit throughout the site, but document libraries or specific folders with unique permissions can cause inconsistent access. Removing these unique permissions forces the library to follow the parent site's rules.

1
Open Library Settings

Navigate to the document library in SharePoint, click the Settings gear icon in the top right corner, and select 'Library settings'.

2
Access Permissions

Click on 'More library settings', then select 'Permissions for this document library' under the Permissions and Management category.

3
Delete Unique Permissions

Look for a yellow banner stating 'This library has unique permissions.' If present, click 'Delete unique permissions' in the top ribbon.

4
Confirm Inheritance

Confirm the prompt. The library will now inherit the parent site's permissions, ensuring users only have Read access.

Remove Unique Permissions from Libraries and Folders
Inheritance Restored: Restoring inheritance guarantees that any user restricted to View access at the site level cannot edit files within this specific library.
Free Microsoft Office alternative

Secure Document Sharing with WPS Office

If managing SharePoint permissions feels overly complex, consider using WPS Office for your document collaboration needs. It offers a free, lightweight, and user-friendly alternative to Microsoft Office. With intuitive cloud storage and straightforward sharing controls, you can easily restrict documents to view-only access, ensuring your files are safe from accidental edits.

  1. 1. Open WPS Office: Launch WPS Office on your desktop or access WPS Cloud via your web browser.
  2. 2. Upload the Document: Save or upload your standard Office files directly to your WPS Cloud space.
  3. 3. Generate a Read-Only Link: Click 'Share', select 'Anyone with the link', and set the permission dropdown to 'View Only' before copying the link for your team.
Completely free and lightweight office suiteHigh compatibility with Microsoft Word, Excel, and PowerPoint formatsSimplified file sharing with clear View-only link generationFamiliar user interface for seamless migration from Microsoft Office
microsoft office alternative - wps office

Frequently Asked Questions

Why can users edit files even when they are in a Read-only SharePoint group?

This usually happens when a specific document library, folder, or file has unique permissions that override the site's default inheritance. It can also occur if an edit-level sharing link was previously generated and shared with those users.

Do copied browser URLs create new permissions in SharePoint?

No. Simply copying a URL from your browser's address bar does not grant new access or create a sharing link with separate permissions. Only using the built-in 'Share' option generates unique permission links.

Can inherited permissions come from site templates?

Yes, some document libraries may inherit default permissions from the templates used to create them or from parent sites. You can review and modify these by checking the library's specific permission settings.