Records Management Locks a Library Unexpectedly: Root Cause and Fix

When you enable records management on a SharePoint document library, you expect items to be locked only when they are declared as records. However, some administrators find that the entire library becomes locked or that users cannot edit any file even though no records have been declared. This problem occurs because SharePoint applies a site-level lock or a library-level lock when the Records Center site template or the In-Place Records Management feature is activated incorrectly. This article explains why the lock happens and provides the exact steps to remove the lock and prevent it from recurring.

Why Records Management Locks a Library Without Declaring a Single Record

SharePoint records management uses a site-level lock to protect records from accidental deletion or modification. When you activate the In-Place Records Management feature at the site collection level, SharePoint applies a lock that restricts editing on all document libraries in that site collection. The lock is part of the Records Center site template behavior, but it can also appear on team sites and communication sites when the feature is activated.

The root cause is a setting called Record declaration availability. By default, when In-Place Records Management is activated, the record declaration policy is set to Allow manual declaration. However, if a site policy or a compliance policy is applied that forces automatic record declaration, SharePoint locks the library to prevent changes to items that might become records. Additionally, the site collection lock status in the SharePoint Admin Center can be set to Read only by a compliance administrator, which locks all libraries regardless of record declaration.

Another common cause is the Site Collection Lock feature. When a site is placed under a compliance retention policy, SharePoint automatically locks the site to prevent content modification. This lock appears as a library lock to end users, even though the library itself has no record declaration settings enabled.

The Difference Between Library Lock and Site Lock

A library lock prevents users from adding, editing, or deleting items in that specific library. A site lock prevents all write operations on the entire site collection. Records management can cause both. Understanding which lock is active is the first step in resolving the issue.

Steps to Remove the Unexpected Lock and Restore Library Access

1. Check the Site Collection Lock Status in SharePoint Admin Center
   Go to the SharePoint Admin Center. Select Active sites from the left menu. Find the site collection that contains the locked library. In the Lock status column, verify if the site is set to Read only or Locked. If it is, click the site name, then select Settings. Under Site lock status, choose Unlock and click Save. This removes the site-level lock imposed by a compliance policy.
2. Deactivate In-Place Records Management if Not Needed
   Navigate to the site collection root. Click the gear icon and select Site settings. Under Site Collection Administration, click Site collection features. Scroll down to In-Place Records Management. If the feature is active, click Deactivate. Confirm the deactivation. This removes the library lock that the feature applied to all libraries in the site collection.
3. Change Record Declaration Settings to Manual
   If you need to keep In-Place Records Management active, adjust the declaration settings. Go to the locked library. Click the gear icon and select Library settings. Under Permissions and Management, click Record declaration settings. Set Record declaration availability to Allow manual declaration of records. Uncheck Automatically declare items as records when they are added to this list if it is checked. Click OK. This prevents the library from automatically locking all items.
4. Remove Any Compliance Retention Policies That Lock the Site
   Go to the Microsoft Purview compliance portal. Select Data lifecycle management > Microsoft 365 > Retention. Find any retention policy that applies to the site collection. Edit the policy and remove the site from the policy scope. Wait up to 24 hours for the lock to be released. Alternatively, if the policy is no longer needed, delete it.

If the Lock Persists After the Main Fix

Library Still Shows Locked After Deactivating In-Place Records Management

If the library remains locked after deactivating the feature, the lock may be cached. Refresh the library page by pressing Ctrl+F5. If the lock still appears, check the site collection lock status again in the SharePoint Admin Center. A compliance policy may have re-locked the site. Verify that no other policies apply to the site.

Users Cannot Declare Records Even Though Lock Is Removed

After removing the unexpected lock, users may still see the Declare record button grayed out. This happens if the library does not have the Record declaration settings configured correctly. Go to Library settings > Record declaration settings and ensure that Allow manual declaration of records is selected. Also verify that users have at least Contribute permissions on the library.

Site Lock Status Changes Back to Read Only After a Few Hours

If the site lock status reverts to Read only after you manually unlock it, a background compliance job is re-applying the lock. This indicates that a retention policy or a data lifecycle policy is still active on the site. Go to the Microsoft Purview compliance portal and check for any policies that have the site in scope. Remove the site from all such policies. The lock should not return after the next policy evaluation cycle.

Item	Library Lock	Site Lock
Description	Prevents changes to items in one library	Prevents all write operations on the entire site
Where to check	Library settings > Record declaration settings	SharePoint Admin Center > Active sites > Lock status
Cause	In-Place Records Management feature or automatic record declaration	Compliance retention policy or manual site lock
Fix	Deactivate In-Place Records Management or change declaration to manual	Unlock site in SharePoint Admin Center or remove retention policy

You can now identify whether a library lock or a site lock is causing the unexpected behavior. Start by checking the site lock status in the SharePoint Admin Center. Then deactivate the In-Place Records Management feature if it is not required. If you must keep records management active, set record declaration to manual to prevent automatic locking. For persistent locks, verify that no compliance policies are still applied to the site. Use the Ctrl+F5 refresh to clear any cached lock state in the browser.