In Google's GSuite, users who have the "Content manager" permission on a shared drive are, according to the access level stated directly at the point permissions are granted, allowed to "add, edit, move and delete files".

Yet none of our users who have "Content manager" permission on two shared drives are able to move the content from one shared drive to the other despite the fact that they have both move and delete permissions, which would seem to cover all the bases here! The message they get is "You don't have permission to move files out of ".

If the user has "Manager" permission in the source shared drive, then they can move the content out of that drive. But according to the permissions themselves, this gives them the added ability to "Manage content, members, and settings". In our organization we have certain users that need to be able to move content between share drives, but we do not want them to b e able to change members and settings on the drives!

What are we doing wrong here? How can Content managers move files between shared drives without also being able to manage users?

4 Answers 4


For the moment this is how Google Team Drives is setup. Every Team Drive folder is really a folder for one specific team and about one specific subject. That's why Google restricted moving content between drives for content managers.

Imagine you have Team Drive A with colleagues from team A. And then you have Team Drive B with colleagues from team B. Then there's created a new Team Drive folder for a specific project, here there are colleagues from team A and team B. They only work together on this specific project. You wouldn't want those people to have the rights to move contents from folders A or B to this C folder.

However I understand your question. I guess Google is still developing on this subject, as there are only 3 user roles in Team Drives for now. So I guess we just have to wait for more options on this.


At the time of writing this, the english version of this article from Google Drive Help reads that you need Content Manager access to the source drive. However, the french version of the article reads that you need Administrator access to the source drive (translated):

For a member of the team to move files from a shared drive to another :

  • He or she must be an administrator of the source Shared Drive Drive.
  • He or she must have at minimum the Contributor permission on the target Shared Drive.

But in my case, the Administrator permission was also needed on the target drive.

This table from this article might be more accurate:

Important part of the article

Some setting in our organization might be partly responsible for this but I couldn't find anything. In any case, this is confusing...


There is an organizational setting in G Suite that allow content managers to move files between drives. The instructions are here:


In brief:

  1. Log into Google Admin
  2. Go to Apps > G Suite > Settings for Drive and Docs > Migration Settings
  3. Check the box labeled "Allow users to migrate files to shared drives"

To move a file, a content manager must have edit access to the file and also be a member of the destination drive.

  • According to this: support.google.com/a/answer/7374057?hl=en to move a file you need Manager access in the shared drive you are moving from (I guess this is due to the implied changes in the access rights of the file you are moving),
    – joanpau
    Nov 20, 2020 at 9:30

This is dumb or I'm missing something.

People with content management role on Shared Drive A and Shared Drive B can download and delete from A and upload to B.

With GoogleDriveFileStream : cut n' paste

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.