The move command removes the file’s existing parent relationship
Source references: 3Step 3 does more than add a file to a new folder: `removeParents` removes its old parent relationship. The instructions do not require checking the file, old parent, and destination first, nor do they provide a preview or per-item confirmation.
If placeholder IDs are replaced incorrectly, real Drive files can disappear from their expected location, land in the wrong project structure, or become visible to different people through the destination folder’s sharing settings. The verification step lists destination contents but cannot automatically undo the move.
This is an active execution step, not a warning example. `removeParents` removes the specified file's old parent relationship while adding the new folder. That matches the stated purpose of moving files, so it is not out-of-scope behavior; however, an incorrect FILE_ID, FOLDER_ID, or OLD_PARENT_ID could make a file disappear from its original location, and verification occurs only afterward. The user can require a pre-change listing and item-by-item confirmation, or initially add the new parent without removing the old one.
2. Create sub-folders: `gws drive files create --json '{"name": "Documents", "mimeType": "application/vnd.google-apps.folder", "parents": ["PARENT_FOLDER_ID"]}'`3. Move existing files into folder: `gws drive files update --params '{"fileId": "FILE_ID", "addParents": "FOLDER_ID", "removeParents": "OLD_PARENT_ID"}'`4. Verify structure: `gws drive files list --params '{"q": "FOLDER_ID in parents"}' --format table`Show 2 other places
3. Move existing files into folder: `gws drive files update --params '{"fileId": "FILE_ID", "addParents": "FOLDER_ID", "removeParents": "OLD_PARENT_ID"}'`4. Verify structure: `gws drive files list --params '{"q": "FOLDER_ID in parents"}' --format table`name: recipe-organize-drive-folderdescription: "Create a Google Drive folder structure and move files into the right locations."metadata: