What happens to permissions when a file is moved to another location in the same drive?
|
Things to watch out for when copying and moving files around Collab... Show
When copying a file (copy/paste) or moving it (cut/paste) from one volume to another (e.g., from Collab to Home), the file will lose the original permissions it had before the copy/move. So, for example, if you copy a file, mystuff.txt, from Home to a directory on Collab accessible to everyone in your department, then anyone in your department will able to access the file on Collab. The same is true if you copy/paste a file within Collab, say from a directory accessible to anyone in your department to a project directory accessible to a specific group of people, some of whom are outside your department. Once copied to the project directory, the file will be accessible to the specific group. This should all be fairly intuitive. Files take on the permissions of the containing directory. There is a gotcha, though. If you move a file (drag and drop) rather than copy it, then the file retains its original permissions, but only if it is being moved within a single volume (e.g., from one part of Collab to another; not from, say, Collab to Home). Why does this matter? Because if you are reorganizing lots of files and you cut/paste or drag/drop files with special/individualized permissions from one place on Collab to another, they will retain their original permissions. Say you cut a file on John's folder on Collab that has files in it that only John and Bob can see, and you paste them into a general department-wide folder on Collab. In their new place, the department-wide folder, they will still only be visible to John and Bob. If you want the files to become visible to the entire department, copy and paste them, then if desired delete them from their original location. See Microsoft's Knowledge Base document, https://support.microsoft.com/en-us/kb/310316, which states that
Examples:
Related articlesThis article does not describe moving content to or from shared drives. For details, see Move content to a shared drive. Shared folders are different from shared drives. Moving an item from a shared folder may change who can see it and what permissions apply to the item. Consider using shared drives in your organization instead of simply sharing folders. Note: If you move folders with a lot of files or subfolders, it might take some time to move all the items to the new location. Before you beginTo move files or folders from a shared folder to My Drive:
File permissionsMoving a file or folder from a shared folder into My Drive is a move and not a copy. The moved content is no longer in the shared folder. As a result:
Example
Notifications when moving filesWhen a user moves a file from a shared folder to My Drive, they see a warning before the move takes effect. This notification helps reduce the risk of a user accidentally moving files and removing access from other users. If the user proceeds with the move, they see another message notifying them of the change, giving them a chance to undo it. Users can also track activity for files and folders in My Drive to see the history of any changes, including notices when files are moved. So, if you share a folder from My Drive and someone moves an item out of the shared folder, you can see a notice in the activity history that the file was removed. The notice also tells you who moved the file and when. What should your organization do?If your organization doesn’t have an extensive shared folder structure, you might not need to do anything. However, organizations that use shared folders extensively might:
Tip: If an item shows up in your My Drive root that previously wasn't there, read Find a file you don't think you deleted. Related topics
Was this helpful? How can we improve it? What happens when a files permissions are moved to a different location within the same drive?When you copy a protected file to a folder on the same, or a different volume, it inherits the permissions of the target directory. However, when you move a protected file to a different location on the same volume, the file retains its access permission setting as though it is an explicit permission.
What happens to the permissions of a file or folder that is moved within the same NTFS volume?You can modify how Windows Explorer handles permissions when objects are moved in the same NTFS volume. As mentioned, when an object is moved within the same volume, the object preserves its permissions by default.
Does move or copy retain permissions?When you copy a protected file to a folder on the same, or a different volume, it inherits the permissions of the target directory. However, when you move a protected file to a different location on the same volume, the file retains its access permission setting as though it is an explicit permission.
When you move a file with NTFS permissions from one folder to another folder between different NTFS volumes How is the file treated?If you move a file from one folder to another folder on the same NTFS volume, the file will retain the original NTFS permissions. If you move a file from one folder to another folder between different NTFS volumes, the file is treated as a copy and will have the same permissions as the destination folder.
|
