Google Shared Drive File Structure

displayNameGoesHere

3/22/24, 9:12 PM

We're looking at migrating from a traditional file server to Google Drive and are currently trying to figure out to replicate our current permission structure so there's as little difference between the two as possible.

On our current file share we usually have the following folder structure:

Project Folder
- Budget
- Scope of Work
- Sensitive Content
  - User Interviews
  - User Contact info

At the project folder level we'll usually let all staff who are on the project have access. But then for the subfolder "sensitive content" we'd restrict it to a smaller group of staff.
So where we currently funnel down the users who have access as you go further into the directory structure it looks like Google drive is the opposite, needing to be more restrictive at first then share more as needed. My only initial idea is to classify the data a the beginning and create multiple shared drives for the project with a classification label.

For example create the following shared drives at the start of a project: Project A (Public) Project A (Internal) Project A (Internal-Sensitive)

Is this how others have set up Google Shared drives?

0 + 0

google-drive

g-suite

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Google Shared Drive File Structure

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.