How to Move a File Without Carrying Broken Permissions

When you move a file from one SharePoint document library to another, the file often retains its original unique permissions. This can cause access issues where users who should see the file cannot, or users who should not have access suddenly do. The cause is that SharePoint applies permissions at the item level when a file is moved, rather than inheriting permissions from the destination library. This article explains how to move files so they inherit the permissions of the target library, preventing broken permissions from following the file.

Why File Permissions Break When Moving

SharePoint stores permissions at the item level when a file has unique permissions. Unique permissions are set when you break inheritance from the parent library or folder. When you use the Move To command in SharePoint Online, the file retains all its existing permissions, including unique ones. The destination library is ignored for permission inheritance. This means the file does not adopt the permissions of the target library. Instead, it carries its own permission set, which can conflict with the intended access controls of the new location.

The Move To operation is designed to preserve the file’s metadata and permissions for consistency. However, this behavior becomes a problem when you want the file to follow the permission rules of the destination. The only way to force the file to inherit permissions from the destination is to break the link to its original permission set. This is done by copying the file instead of moving it, then deleting the original. The copy operation creates a new file that inherits permissions from the destination library by default.

When Unique Permissions Are Created

Unique permissions are created when a user or administrator explicitly changes permissions on a file or folder. This can happen during sharing, when you give a specific person access to a file without changing the library permissions. It also happens when you use the Manage Access dialog to grant edit rights to a file. Once broken, inheritance is not automatically restored when you move the file. You must manually reset inheritance or use the copy method described below.

Steps to Move a File Without Carrying Permissions

To ensure a file inherits permissions from the destination library, you must copy the file and then delete the original. The following steps use the SharePoint Online web interface. These steps work for files in document libraries and lists.

1. Locate the file in the source library
   Open the SharePoint site that contains the file. Navigate to the document library where the file is stored. Click the file to select it but do not open it.
2. Open the file context menu
   Right-click the file or click the three dots (ellipsis) next to the file name. From the menu that appears, select Copy To.
3. Choose the destination library
   In the Copy To panel, browse to the target document library or folder. You can type the name of the library in the search box. Select the exact folder where you want the file to appear. Click Copy Here.
4. Verify the copied file has inherited permissions
   Navigate to the destination library. Right-click the copied file and select Manage Access. In the Manage Access pane, look for the text Inherited under the file name. If you see Inherited, the file is using the library permissions. If you see Unique, repeat the copy process to a different location or check if the destination itself has unique permissions.
5. Delete the original file from the source library
   Return to the source library. Right-click the original file and select Delete. Confirm the deletion. The original file is moved to the site recycle bin. The copied file remains in the destination with inherited permissions.

Alternative Method: Use File Explorer to Move

If you prefer using File Explorer, you can achieve the same result by dragging and dropping the file. However, dragging also preserves unique permissions. To avoid this, use the copy and paste method instead of drag and drop.

1. Open both libraries in File Explorer
   In SharePoint Online, click Sync on both the source and destination libraries to sync them to your computer. Open File Explorer and navigate to the synced folders.
2. Copy the file from the source folder
   Right-click the file in the source folder and select Copy. Do not drag the file.
3. Paste the file into the destination folder
   Right-click inside the destination folder and select Paste. The file is uploaded as a new version with inherited permissions.
4. Delete the original file
   Right-click the file in the source folder and select Delete. Confirm the deletion. The file now exists only in the destination with inherited permissions.

If SharePoint Still Shows Unique Permissions After Moving

Even after using the copy method, the file may still show unique permissions. This happens if the destination library itself has unique permissions at the folder level. Check the destination folder’s permission inheritance before moving the file.

Check Folder-Level Permissions on the Destination

Right-click the destination folder in SharePoint and select Manage Access. If the folder shows Unique permissions, the file will inherit those unique folder permissions, not the library defaults. To fix this, reset the folder’s inheritance to inherit from the library. Go to the folder’s settings, click Permissions, and select Delete Unique Permissions. Then copy the file again.

File Shows Broken Permissions After Using Move To

If you already used Move To and the file has broken permissions, you can reset them manually. Go to the file’s location in SharePoint. Right-click the file and select Manage Access. Click the three dots next to the file name and select Manage Direct Access. Click Advanced Permissions Settings. On the Permissions page, click Delete Unique Permissions. The file will now inherit permissions from its parent folder.

Move To vs Copy To: Key Differences for Permissions

Item	Move To	Copy To
Permissions behavior	Retains all unique permissions from the source	Creates new file that inherits from destination
Metadata preservation	Preserves all metadata and version history	Preserves metadata but loses version history
Best use case	Moving within the same permission structure	Moving to a library with different permissions
Post-move action needed	May require manual permission reset	None if destination inherits correctly

Using Copy To followed by deleting the original is the only reliable method to prevent broken permissions. Move To is faster but requires additional steps to fix inheritance. Always verify permissions after the move by checking the Manage Access pane.

Now you can move files between SharePoint libraries without carrying over broken permissions. Use the Copy To command and then delete the original file to force the file to inherit permissions from the destination. As an advanced tip, you can automate this process using a Power Automate flow that copies files and deletes the originals, ensuring consistent permission inheritance across large migrations.