As the screenshot shows a background we could say that the folders are included in a "Shared Drive" (formerly "Team Drive"), also the link include in the question refers to a learning article about Team Drives.
Unfortunately, at this time it's not possible to share folders included in a Shared Drive but you could add the users you want to share the folder ...
The biggest differentiation to consider is who is the “owner” of the folder/files.
If all shared data should still be accessible after you leave your organization, use a Team Drive. If you use My Drive, and you forget to transfer ownership of your documents before you leave, all your documents (even the shared ones) might be deleted when you leave the ...
From experience, if you have a large number of people editing a shared folder in My Drive, chances are a small percentage of them will be so unaccustomed to using Google Drive that they will accidentally remove resources. This is annoying to rectify (but can be done by finding the items in the Activity pane on the right).
Shared drives enable the manager to ...
The icon on the Google Drive left panel for the Team Drive unit named "Team Drive" shows a key. That could means that it doesn't belong the organization of the account being used to access Google Drive or that that the administrator has not allowed users to create Team Drives.
In order to be able to delete that unit
The unit should be empty
The user ...
This kind of announces are made on https://gsuiteupdates.googleblog.com/
It's worth to note that the Team Drive announcement made on March 2017, was updated to announce the inclusion of G Suite for Nonprofits, but there is no mention of the G Suite (basic).
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 ...
Got it! I tried this from RayB, and it helped: https://webapps.stackexchange.com/a/140932
went to my test channel
posted the Google Doc link
chose "delete file from Slack" from its menu
reposted the link
Voilà! it posted with the new title and thumbnail
How can Team Drive permissions be changed en mass?
Use the Google Drive API. For this you could create an app by using programming languages that are able to work with REST APIs or to use the Google Drive Advanced Service of Google Apps Script.
After having to talked to Google support, and run my own tests - Yes, anybody can permanently and unrecoverably delete any and all information they have write access to in Google Drive in a matter of seconds (obviously, save for any other backups you have manually set up).
Seems like a massive security failure to me, but oh well. We have resolved to ...
I tried the related script and it worked correctly for me.
I looks to me that the problem is an error message from the web browsers rather than one coming from the Google Apps Script engine. It could be due to a network connection related issue like something between your web browsers and Google servers is blocking the HTML generated by Google Apps Script.
Google Drive allow to share files with specific people by adding their email address or by adding the email address of a Google Group.
If you have a G-Suite account, another alternative could be to use Google Team Drive. This could be possible if Team Drive is enabled for your organization and if Google Drive for your organization is configured to allow to ...
The cause of the problem is on the "layer 8", meaning this is caused by the users. In order to find how exactly this happened you will have to look at the activity of the folders to figured out who created them, then checkout which front-ends and apps they are using with Google Drive and how they are being used.
One possible scenario is that someone created ...
We could share files and folders with Google accounts and Google Groups, there is no way to "share a file with a folder" but you could move files owned by you. If the files are owned by other people from the same Organization they should move them.
If the files are owned by people from a third-party organization, AFAIK it's not possible to transfer the ...
Use the advanced search and select Location > Team Drives > Specific Team Drive
Go to https://drive.google.com using your G Suite account
Click on the dropdown button at the right of the Google Drive's search box.
Click on the button next to Location, click on Team Drives, then on the name of the team drive that you want ...
First off, you need to have certain "superadmin" role permissions to be able to do that.
You need the "Move any file or folder into shared drives" role added
to your account. https://support.google.com/a/answer/7374057
However, even with those roles in place, you may encounter the dreaded "Folders can't be moved into shared drives yet" error.
It turns ...
We had a very similar issue. What worked for us was to use the Linux based command-line tool drive.
Add your non-GSuite folder as shared folder to your Team Drive. This is needed so that drive can copy files remote-to-remote. Otherwise, Google Docs / Sheets / Draw / Impress files could not be preserved as they are but would have to be exported ...
Create a group
Add all the organization users to that group
Add the group as a member of the corresponding Team Drive
Add all users to a group
Share files with Team Drives
Manage your Team Drive users and activity