Why Do File Permissions Change When You Cut and Paste?

April 26, 2025 5 answers
Asked by silt-deposit
I recently had a frustrating experience with file permissions at work. Our main Active Directory (AD) manager is on vacation, and I was handling a ticket from a customer service rep who couldn't access a specific file in a folder where they otherwise had full modify rights. No matter what we tried, they couldn't open it. After some back and forth, I got advice from a former AD admin who explained that when you cut and paste a file, the permissions move with the file, while a copy/paste operation applies inherited permissions from the destination folder. This meant I had to refresh the permissions at the folder level to resolve the issue. So, I'm left wonderingโ€”why does it work this way?

Answers

pattern_repeat
This can vary depending on whether youโ€™re moving files across different drives. If youโ€™re moving from one volume to another, the system treats it like a copy and delete, which means the new file will inherit the target folderโ€™s permissions rather than keeping the old ones.
Reply to this answer
!select a category
When you move a file on the same volume, it's a true moveโ€”meaning all original attributes like permissions stay the same. But if you copy the file, itโ€™s treated as a new object that gets the inherited permissions from the target location.
Reply to this answer
Corker
This is a classic example of how Windows handles file operations. The important takeaway is that if permissions matter, it's often safer to copy the file and delete the original, or use tools like RoboCopy that let you manage ACLs more effectively.
Reply to this answer
cursor.blink
I learned during my training years ago that with NTFS permissions, the rule is "Copy Inherit, Move Retain." So moving within the same volume keeps the permissions, but crossing volumes means you start fresh with the target folderโ€™s ACL.
Reply to this answer
After-the-buzzer
Cutting and pasting keeps the original permissions intact, while copying creates a new file that inherits permissions from the destination folder. It's like a shortcut for moving files without changing their access rights if you're staying within the same volume.
Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions