Data Organization for Teams

I published a new article about data organization for teams. It is available in the AppSheet help docs. Check it out!

The article describes how to use a Google Shared Drive or an O365 SharePoint site to store data for your team. Using a shared data location can be helpful to ensure longevity beyond a single user’s cloud account. It also makes transferring apps between owners a breeze.

The article focuses on using a single shared drive for the whole team. The same process could be applied to use multiple shared drives as well.


Hi @Derek, in the reference article for setting the SharedDrives, the terminology to use is still TeamDrive.

Where the root folder path as per the help article is:


Last week, I have just connected my team to the SharedDrives using the above “TeamDrive” as connection name and it was working fine.

However, I wonder if this connection using TeamDrive as the connection name would be depreciated in the future and what will be the impact to the connected Apps?


Hi @Heru,

That is a great question to raise. On May 31, 2019, the “Team Drives” feature of Google Drive was renamed to “shared drives.”

Backwards compatibility is always a priority when making updates to the platform. If the AppSheet terminology is updated in the future, the change will be made in a way to ensure existing root folder path definitions continue to work as expected.


@Derek, Last year when the name was changed from TeamDrive to SharedDrives, the functionality is the same, except for any excel files linked to other excel files and any links pointing address using a TeamDrive name - we have to change it manually to get the links back to functions.

Now, reading your response, I am happy since it clarifies my concern.


1 Like

Hi @Derek, an update today as one of my new member team being set-up for the SharedDrives was having difficulties to connect to the drives using the root folder path similar to below with [TeamDrive]:

/[TeamDrive ]MyTeamDrive/appsheetdata

Until he report back and I just blindly test with a new connection root folder path with SharedDrives as the name, see below:

Unfortunately, it works.

So I imagine that the next time connection to be made to SharedDrives shall use this new [SharedDrives] as folder root path naming, at least, that’s what I will tell my team to do.

1 Like

Hi Heru,

Thanks for posting. I’m surprised that using [SharedDrives] worked as that is not a supported keyword.

The supported process is described in this article. The syntax is:

  • [TeamDrive] is a keyword and should be copied as is.
  • “MyTeamDrive” is the name of the Shared Drive. It should be replaced with the name of your shared drive.
  • “appsheetdata” is the name of a folder inside the Shared Drive. It should be replaced with the name of your target folder.

I would recommend looking for other areas where there could be an issue. Possible areas to check are the name of the Shared Drive and your team mate’s permissions on the Shared Drive.

1 Like

There might be an issue, but I have to recheck and get back to you later.
When tries to use the syntax /[TeamDrive] as below:

He got a new folder with [TeamDrive] in his MyDrive:

People that already connected last week still can access the TeamDrive designated for AppSheet, only new people could not.

And I was reporting too early yesterday, actually [SharedDrive] did not work, and just producing a new folder like this in his MyDrive:

I will try to create a dummy account and report back to you.

He was able to connect to TeamDrive, with steps as follow: After remove appsheet access on their google account, logout from appsheet, clearing cache, log-in back again to AppSheet, make sure default folder changed, and try to copy one app.


Hi Heru,

I’m glad your team mate got the connection to a Shared Drive working!