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?
Best Answer
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.