A Google Drive move can alter access even when the file’s contents and link remain the same. Direct permissions, inherited folder permissions, and shared-drive restrictions are different sources. Trace which source changed before trying to restore collaboration.
Compare the old and new locations
Record the file link and use details or activity to identify the destination. Ask the owner which parent folder or shared drive contained it before the move. Confirm the affected collaborator’s account and required role.
Someone may have relied entirely on the old parent’s sharing. Their name need not have appeared as a direct file permission. Moving the item can remove that inherited route or introduce a different audience at the destination.
Inspect the destination’s rules
Open Share on the file and destination folder. Check direct access, groups, General access, and any limited-access boundary. When content moves into a shared drive, organization ownership and drive-level restrictions also matter.
Google’s shared-drive guide explains that direct file permissions and inherited parent permissions are treated differently during moves. A direct entry can remain while a stricter shared-drive restriction prevents its use. Do not assume that a listed address proves effective access.
Repair the intended boundary
Have the owner or manager restore the necessary narrow permission, choose an approved destination, or provide an appropriate shortcut. Avoid repeatedly moving the file back and forth while diagnosing the problem. Verify the original link under the affected account after the correction, and check that the destination has not exposed the file to unrelated members. Document the change so future reorganizations account for the same permission dependency.
References
- Share and manage access to files and folders in Google Drive
- Learn about limited access to files and folders in Google Drive
- How file access works in shared drives
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.