File Opens Read-Only After Moving Between Libraries: Root Cause and Fix

When you move a file from one SharePoint document library to another, the file may open as read-only in the browser. This happens even if you have edit permissions on the destination library. The root cause is a mismatch between the file’s internal permission inheritance and the new library’s permission settings. This article explains why this occurs and provides a step-by-step fix to restore full edit access.

Why Moving a File Between Libraries Causes Read-Only Mode

SharePoint document libraries store permission settings at two levels: the library level and the item level. When you move a file from Library A to Library B using the Move or Copy command, the file retains its original permission settings. If Library A had unique permissions (permissions that did not match the site’s default), those unique permissions travel with the file.

In the destination library, the file may now have a permission set that conflicts with the library’s inherited permissions. This conflict causes SharePoint to apply the most restrictive permission set, which often results in read-only access for users who otherwise have edit rights on the destination library. The file appears with a lock icon or shows ‘Read-only’ in the browser status bar.

Another contributing factor is the file’s checkout status. If the file was checked out to the user who moved it, the checkout state may transfer to the new location. In the destination library, the file remains checked out to that user, and other users see it as read-only. The same applies if the file was checked out to someone else before the move.

Steps to Restore Edit Access to a Moved File

1. Open the destination library and locate the file
   Navigate to the SharePoint site and open the document library where you moved the file. Find the file that opens as read-only. Do not double-click it yet.
2. Check the file’s checkout status
   Hover over the file name and click the check mark circle. In the details pane, look under the heading ‘Checkout.’ If the file is checked out to anyone, you will see the user’s name. If it is checked out to you, select the ellipsis (three dots) next to the file and choose ‘Discard Checkout.’ If it is checked out to another user, ask that user to check in the file or ask a site owner to force a check-in via the library settings.
3. Verify permission inheritance
   Select the file by clicking its check mark. On the command bar, click the ellipsis and choose ‘Manage access.’ In the Manage access pane, look for the message ‘This item has unique permissions.’ If you see that message, the file is not inheriting permissions from the library. This is the most common reason for read-only mode.
4. Break and re-inherit permissions
   If the file has unique permissions, you must reset them to inherit from the library. In the Manage access pane, click the link ‘Advanced permissions settings.’ This opens the Permissions page for the file. On the ribbon, click ‘Delete Unique Permissions.’ Confirm the action. The file now inherits permissions from the library. Close the Permissions page and return to the library.
5. Test the file
   Double-click the file to open it in the browser. It should now open in edit mode. If it still opens as read-only, refresh the library page and try again. If the issue persists, check if the library itself has any unique permissions at the library level that restrict editing.

If the File Still Opens Read-Only After the Main Fix

File opens read-only in the browser but not in the desktop app

This can happen when the file is marked as a ‘required’ document for a workflow or when the library has a ‘Require Check Out’ setting enabled. Go to the library settings by clicking the gear icon > Library settings. Under ‘Versioning settings,’ look for ‘Require Check Out.’ If it is set to ‘Yes,’ the file will open as read-only until you check it out. Click ‘Check Out’ from the file’s context menu, then open the file.

Multiple users report the same file as read-only

If every user sees the file as read-only, the file may have been moved from a library that had ‘Read’ permissions for all users except the owner. Check the file’s permission history by going to the file’s Permissions page (as described in step 4 above). Look for any direct permission entries that grant only ‘Read’ access. Remove those entries or change them to ‘Contribute’ or ‘Edit.’

File was moved using the ‘Copy to’ action instead of ‘Move’

When you copy a file, SharePoint creates a new item that inherits permissions from the destination library by default. However, if the source file had unique permissions and you used the ‘Copy to’ command with the ‘Keep permissions’ option, the copy inherits the source’s unique permissions. To fix this, follow the same permission reset steps in the main fix above.

Move vs Copy: Permission Behavior Comparison

Item	Move	Copy
Permission inheritance	Retains source permissions (may cause read-only)	Inherits destination library permissions by default
Checkout status	Retains checkout status from source library	Creates a new version; checkout status is not copied
Version history	Moves version history with the file	Does not copy version history
Metadata	Moves all metadata including custom columns	Copies metadata; some column types may not transfer

After moving or copying a file, always verify the file’s permissions and checkout status in the destination library. If you frequently move files between libraries, consider standardizing permission inheritance across all libraries by using site-level permission groups. This prevents unique permissions from causing read-only issues in the future.