📁 Lesson 7.2: Project — A Shared Team / Family Drive

A tidy personal Drive is calm. A well-run shared space is transformative — it ends the emailed-attachment chaos for a whole group of people at once. In this project you'll build a shared team or family space that others actually use: the right container, a clear structure, people invited with the right roles, simple norms, a "Start Here" guide, and a security check so nothing leaks. This is Module 4, made real.

📚 What You'll Learn

By the end of this lesson, you will be able to:

Choose between a shared folder and a shared drive for your group
Design a clear shared structure that newcomers understand instantly
Invite people with the right roles — Viewer, Commenter, Editor — on purpose
Set simple shared norms so the space stays usable over time
Write a "Start Here" doc that orients anyone who opens the space
Run a security review to make sure nothing is accidentally public

⏱️ Estimated Time: 60 minutes

🎯 Project: Create a shared team or family space, invite at least one person with an appropriate role, add a "Start Here" guide, and run a quick security review confirming nothing is shared more widely than you intend.

In This Lesson

🗂️ Shared Folder vs Shared Drive

Before you invite anyone, you make one choice: what kind of container will hold the shared space. There are two, and picking the right one saves a lot of confusion later.

A shared folder (available to everyone)

A shared folder is an ordinary folder in your My Drive that you share with other people. It's the right choice for the vast majority of families, small groups, and casual teams — it works on any free Google account, it's simple, and everything you learned about structure applies directly. The one thing to know: a shared folder is owned by you (the person who created it). Its contents live in your Drive, and if your account went away, the folder would go with it.

A shared drive (Google Workspace only)

A shared drive (formerly called Team Drives) is a separate space owned by the organization rather than any one person. Files added to it belong to the team, so when someone leaves, their files stay put. This is excellent for businesses and long-lived teams — but it's a Google Workspace feature, available on certain business and education editions, not on free personal accounts. Availability and which editions include it change over time, so check Google's current Workspace pages rather than assuming.

💡 Which should you use?

For a family photo collection, a club, a volunteer group, or a small project with friends — a shared folder is almost always the right call, and it's what this lesson builds. If you're on a Workspace account at work or school and the files should outlive any one person's account, ask whether a shared drive is available to you. The skills are the same either way; only the ownership model differs.

🧭 A Structure People Understand Instantly

A personal Drive only has to make sense to you. A shared space has to make sense to people who weren't there when you built it — which is a higher bar. The goal is a structure so obvious that a newcomer knows where to put a file and where to find one without asking.

Three principles make that happen:

Name folders by what goes in them, plainly. "Meeting Notes," "Photos," "Budgets," "Forms" — not clever names only you understand. Obvious beats elegant in a shared space.
Stay shallow. Every extra level of nesting is a place someone can get lost. Aim for one or two levels; a newcomer should see the whole shape at a glance.
Put a "Start Here" doc right at the top. The very first thing anyone sees should tell them what this space is and how to use it. (We build that doc later in this lesson.)

Here's the shape of a shared space, with the people and their roles shown alongside the structure — notice how the container holds both a clear folder tree and a set of members, each with a deliberate level of access:

graph TD SF["📂 Family Drive
(shared folder)"] --> SH["📄 START HERE
read me first"] SF --> PH["🖼️ Photos"] SF --> DOCS["📝 Documents"] SF --> BUD["💰 Budgets"] SF --> ARC["🗄️ Archive"] SF -.->|"members"| M["👥 People & roles"] M --> ED["Mom, Dad
Editor — add & edit"] M --> CO["Grandpa
Commenter — suggest"] M --> VW["Cousins
Viewer — read only"]

The structure and the roles are two halves of the same design: the folders decide where things go, and the roles decide who can do what. Get both right and the space runs itself.

👥 Inviting People with the Right Roles

Sharing is the moment Drive becomes powerful — and the moment it becomes risky. The single most important habit is to share on purpose, not by reflex: add specific people, and give each one the least access they need to do their part. That's not stinginess; it's how you keep a shared space safe and calm.

When you share a folder (right-click → Share, or the Share button), you add people by email and choose a role for each. Three roles cover almost everything:

Role	What they can do	Give it to…
Viewer	Open and read; cannot change anything	People who just need to see it — relatives, an audience, reference-only members
Commenter	Read and leave comments/suggestions; cannot edit the file itself	Reviewers and advisers — they weigh in without changing the content
Editor	Add, edit, move, and (often) delete or re-share	The active core — the people actually building and maintaining the space

Grant a folder's access and everything inside it inherits that access — so think at the folder level. Most shared spaces have a small handful of Editors (the people who keep it running) and a larger circle of Viewers or Commenters. When in doubt, start people lower and raise them if they genuinely need more; it's easier and safer than walking access back later.

⚠️ Watch Out

Editors can usually re-share, move, and delete — that's a lot of trust. Reserve Editor for people who truly co-own the space, and keep the Editor circle small. Also be deliberate about link sharing: a link set to "anyone with the link" can be forwarded anywhere and is the most common way files leak. Prefer inviting specific people by email, and treat "anyone with the link" as something you choose consciously, never a default.

📋 Norms: The Unwritten Rules, Written Down

A shared space isn't just a technical setup — it's a small society, and every society needs a few agreed habits. When those habits are written down, the space stays usable for months. When they're left unspoken, entropy wins: files pile up in the wrong places, things get renamed unpredictably, and one well-meaning person accidentally moves everyone else's files.

You only need a handful of norms, and they're mostly common sense made explicit:

Naming. One shared convention (the same date-first, consistent-words idea from your personal system) so everyone's files sort and search the same way.
Where things go. A one-line note on what belongs in each folder, so "where do I put this?" answers itself.
Don't move other people's files. The golden rule of shared spaces. In a shared folder, moving a file can pull it out of everyone's view — so the norm is: add your own, and don't reorganize others' without asking.
Add, don't overwrite. When in doubt, create a new file rather than replacing someone's — version history has your back, but courtesy keeps the peace.

✅ Pro Tip

Norms only work if people can find them, so they live in the "Start Here" doc you're about to write — not in your head, and not in a one-time message that scrolls away. A shared space with three clear written norms beats one with a dozen rules nobody remembers. Keep it short enough that people actually read it.

📄 The "Start Here" Doc

The most useful file in any shared space is a single Google Doc named START HERE (or "Read Me First"), sitting right at the top level so it's the first thing anyone sees. It's the welcome mat and the map in one — the difference between a space people understand and a space people email you questions about.

A good Start Here doc is short and answers the questions a newcomer actually has:

What is this space? One or two sentences — "This is the Rivera family Drive: photos, important documents, and budgets we all share."
What's in each folder? A quick list mapping folder names to what belongs in them.
The norms. Your three or four agreed habits (naming, where things go, don't move others' files).
Who to ask. The name of the person who owns/runs the space, so questions have a home.

Because it's a Google Doc, it lives in the shared folder automatically, everyone with access can read it, and you can update it anytime — a living guide, not a printed rulebook. Pin it in people's minds by mentioning it when you invite them: "I've shared the Family Drive with you — open START HERE first."

🧠 Why this matters

A Start Here doc scales your effort. Instead of explaining the space to each person one by one, you explain it once, in writing, where everyone can re-read it. It's the same instinct behind good documentation everywhere: the five minutes you spend writing it saves hours of "wait, where does this go?" down the line — and it makes the space feel welcoming instead of confusing.

🔒 The Security Review

Careless sharing is the single biggest risk in all of Drive, and a shared space is exactly where it tends to happen. Before you call the space "done," spend two minutes on a deliberate security review. It's quick, it's reassuring, and it catches the mistakes that matter most.

Run through this short checklist:

Check the folder's link setting. Open Share and look at "General access." Unless you truly want the public to see this, it should say Restricted (only invited people) — not Anyone with the link. This is the number-one thing to verify.
Review the people list. Is everyone on the list someone who should be? Remove anyone left over from a test or an old invite.
Check the roles. Is anyone an Editor who only needs to be a Viewer? Dial access down to what each person actually needs.
Watch for sensitive files. Passwords, financial details, ID documents — think twice before those live in a space shared with a wide group, even a trusted one.

⚠️ The link-sharing trap

"Anyone with the link" feels convenient — but that link can be forwarded, posted, or found, and it doesn't ask who's opening it. Once a link is out, you can't un-send it; you can only change the setting going forward. For anything remotely private, share with specific people by email instead. We go deeper on security and privacy in Lesson 8.2, but this quick review is the habit that prevents most real accidents.

✅ Pro Tip

Make the security review a recurring habit, not a one-time event. Every few months, glance at who has access to your shared spaces and trim anyone who's moved on. Access has a way of quietly accumulating; a periodic tidy keeps a shared space both useful and safe.

🎯 Project: Build Your Shared Space

Now you'll build a real shared team or family space. Pick something genuine — a family photo folder, a club or volunteer group, a small project with friends — so the space outlives this exercise. Open drive.google.com and work through the steps in order.

🏋️ Create a shared space others actually use

Objective: A working shared space — the right container, a clear structure, at least one person invited with an appropriate role, a "Start Here" guide, and a completed security review.

Instructions (about 45 minutes):

(4 min) Decide your container: a shared folder (works on any account — the usual choice) or, if you're on Workspace and it fits, a shared drive. Create it and give it a clear name.
(8 min) Build a shallow, obvious structure — a handful of plainly named folders (for example Photos, Documents, Budgets, Archive). One or two levels deep, no more.
(10 min) Create a START HERE Google Doc at the top level. Fill in: what the space is, what's in each folder, your 3–4 norms, and who to ask.
(8 min) Invite at least one person by email and choose their role deliberately — Viewer, Commenter, or Editor — based on what they actually need to do.
(5 min) Move a few real files into the right folders so the space isn't empty when people arrive.
(6 min) Run the security review: confirm general access is Restricted (not "anyone with the link"), check every person and role, and make sure no sensitive files are over-shared.
(4 min) Send a short welcome message pointing people to the START HERE doc first.

💡 Hint — a starter "Start Here" outline

START HERE — [Name] Shared Drive

What this is
- A shared space for [photos / documents / a project]. Everyone
  invited can [read / comment / edit] as noted below.

What's in each folder
- Photos     : event and family photos, named YYYY-MM - Event
- Documents  : shared paperwork and notes
- Budgets    : the running budget (Editors only, please)
- Archive    : finished / old items, kept but out of the way

Our norms (please follow these)
1. Name files date-first: 2026-09-15 - Description
2. Add your own files; don't move or rename other people's
3. When unsure where something goes, drop it in Documents and ask

Who runs this
- [Your name] set this up — message me with any questions.

Keep it short and friendly. A guide people actually read beats a thorough one they skip.

✅ Project Completion Checklist

You created a shared container (shared folder, or a shared drive if on Workspace) with a clear name
The structure is shallow and every folder name is plainly self-explanatory
A START HERE doc sits at the top level and covers purpose, folders, norms, and who to ask
At least one person is invited, each with a deliberately chosen role (Viewer / Commenter / Editor)
A few real files are filed in the right folders
The security review is done: general access is Restricted, roles are right, nothing sensitive is over-shared
You sent a welcome pointing people to START HERE first

🎯 Quick Quiz

Question 1: You want a reviewer to leave feedback on shared files without being able to change the content. Which role fits best?

Question 2: During your security review, what's the number-one thing to verify on a shared folder?

Best Practices for Shared Spaces

✅ Do's

Invite specific people by email. Deliberate access beats a link anyone can forward.
Give the least access that works. Start people as Viewers or Commenters; promote to Editor only when they truly need it.
Write a Start Here doc. Explain the space once, in writing, so you don't explain it a dozen times.

❌ Don'ts

Don't default to "anyone with the link." It's the most common way files leak; choose it consciously or not at all.
Don't hand out Editor freely. Editors can move, delete, and re-share — keep that circle small.
Don't build a deep maze. Newcomers get lost in nesting; stay one or two levels deep.

💡 Pro Tips

Review who has access every few months and trim anyone who's moved on — access quietly accumulates.
Set the folder's access at the top level; everything inside inherits it, so you rarely manage files one by one.

📓 Learning Journal

Keep a learning journal as you work through this course — a separate document, a note, or a Google Doc right in the Drive you're organizing. After each lesson, take a few minutes to write down:

Key concepts you learned
Techniques that clicked for you
Questions or confusion points to revisit
Ideas you want to try in your own Drive
Your progress and feelings about learning this — including where your confidence grew

✍️ This lesson's prompt: Who did you share your space with, and how did you decide each person's role? Did you catch anything in the security review that surprised you? How does it feel to replace a habit of emailing files around with one shared, always-current space? Note one shared space in your life — at home, work, or in a group — that would run more smoothly if you set it up this way.

📝 Lesson Summary

🎓 Key Takeaways

Choose your container first: a shared folder (any account, owned by you) for most groups, or a shared drive (Workspace only, owned by the organization) when files should outlive any one person.
A shared structure must be shallow and plainly named so newcomers know where things go without asking.
Invite specific people by email and give each the right role — Viewer, Commenter, or Editor — granting the least access that does the job.
A written set of norms and a top-level Start Here doc keep the space usable, and a quick security review (general access = Restricted) prevents most accidental leaks.

🎉 What You've Accomplished

You built a real shared space that other people can actually use well — the right container, a structure newcomers understand, people invited with deliberate roles, written norms, a welcoming Start Here doc, and a security review that confirms nothing leaks. You turned your solo organizing skills into shared ones, which is the skill that makes Drive genuinely powerful for families and teams.

❓ Common Questions at This Stage

Do I need a shared drive, or is a shared folder enough?

For almost every family, club, or small group, a shared folder is plenty — it works on free accounts and does everything you need. A shared drive matters mainly for organizations where files must belong to the team rather than a person (so they stay when someone leaves). Shared drives are a Google Workspace feature on certain editions; check Google's current Workspace pages for what's included, since availability changes.

What happens if I use "anyone with the link"?

Anyone who has that link — including anyone it gets forwarded to — can open the file at the level you set, without signing in or being invited. It's convenient for truly public things, but it's also the most common way files leak, because you can't control where a link travels. For anything private, share with specific people by email instead. Lesson 8.2 covers this in depth.

Can I change someone's role or remove them later?

Yes, anytime. Open Share, find the person, and change their role or remove them — the change takes effect immediately. That's exactly why it's safe to start people with lower access and raise it only if they need more. Reviewing and trimming access periodically is a healthy habit for any shared space.

🔭 Looking Ahead

In the next lesson — Lesson 7.3: Project — A Project Hub Tying Docs, Sheets & Slides Together — you'll bring the whole Workspace into one place. You'll build a single project hub folder holding a Doc, a Sheet, and a Slides deck, plus a linked "index" Doc that ties them together — the moment Drive stops being storage and becomes the command center for real work.

✅ Before the Next Lesson

Finish your shared space, invite at least one person, and confirm the security review is clean
Make sure your START HERE doc is written and sitting at the top level
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

You just did the thing that ends emailed-attachment chaos for a whole group at once — a shared space, set up with intention and shared safely. That's a genuinely valuable skill, at home and at work. One hub to go: let's tie Docs, Sheets, and Slides together. 📁