Skip to main content

๐Ÿ“ Lesson 4.1: Sharing โ€” Link vs Specific People, and the Roles

This is where Drive stops being a private filing cabinet and becomes a way to work with other people. Sharing is Drive's superpower โ€” and its sharpest edge. In this lesson you'll learn the two ways to give access (invite specific people, or hand out a link), the three roles (Viewer, Commenter, Editor) and exactly what each can do, and the one habit that keeps you safe forever: share on purpose, not by reflex.

๐Ÿ“š What You'll Learn

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

  • Open the Share dialog and read what it's telling you at a glance
  • Choose between the two access models โ€” specific people vs anyone with the link โ€” and know the risk of each
  • Explain exactly what a Viewer, a Commenter, and an Editor can and can't do
  • Understand how sharing a folder differs from sharing a single file โ€” access flows down
  • Use notify-by-email, and check who currently has access to any file
  • Adopt the mindset "share on purpose, not by reflex"

โฑ๏ธ Estimated Time: 40 minutes

๐ŸŽฏ Project: Share one real file with a specific person as a Commenter, inspect the access list to confirm exactly who can reach it, and reason through what "anyone with the link" would have exposed instead.

In This Lesson

๐Ÿ”— Why Sharing Is Drive's Superpower โ€” and Its Sharpest Edge

Remember the "report_v2_FINAL.docx" nightmare from Lesson 1.1 โ€” the file emailed back and forth until nobody knew which copy was real? Sharing is how Drive kills that problem for good. Instead of mailing copies, you give people access to the one real file. Everyone works on the same thing, changes appear live, and there's a single source of truth. That's the Share stage of our Store โ†’ Organize โ†’ Find โ†’ Share โ†’ Sync model, and it's what turns Drive from a private cabinet into a shared home base.

But the same power that lets you hand a folder to your whole team in two clicks also lets you accidentally expose a document to the entire internet in two clicks. Sharing isn't dangerous because it's complicated โ€” it's risky precisely because it's easy. A link is convenient. Convenient things get used on reflex. And a link set to "anyone with the link" can be forwarded, pasted into a chat, or indexed in ways you never intended.

So we're going to treat sharing with the respect it deserves. Not fear โ€” respect. By the end of this module you'll share confidently and precisely, giving exactly the right people exactly the right level of access, and nothing more. That single discipline is the difference between Drive feeling safe and Drive feeling scary.

๐Ÿง  Mindset

The whole of good sharing fits in one sentence: share on purpose, not by reflex. Before you click Share, you'll ask two tiny questions โ€” who exactly needs this, and what should they be able to do with it? That's it. Two questions, every time, and you'll never over-share by accident. This lesson gives you the vocabulary to answer them precisely: people vs link, and Viewer vs Commenter vs Editor.

๐ŸชŸ The Share Dialog: Reading What It's Telling You

Every share starts the same way. Select a file or folder, then either click the Share button (often a person-with-a-plus icon near the top right), right-click and choose Share, or use the Share option in the file's menu. Up pops the Share dialog โ€” the single most important window in all of Drive to understand well. It has two clearly separated halves:

  • "People with access" (the top) โ€” a box where you type email addresses to invite specific people, and a list of everyone who already has access, each with their role. The owner is marked here too.
  • "General access" (the bottom) โ€” a single dropdown that controls the link. It's usually set to Restricted ("only people added can open") or Anyone with the link. This one dropdown is the difference between private and public.

There's also a Copy link button, and โ€” for many files โ€” a small gear/settings icon with extra options we'll cover in the next lesson. The mental split to hold onto is simple: the top half is about named people; the bottom half is about the link. Almost every sharing mistake comes from ignoring the bottom half โ€” so we'll always read it.

๐Ÿ’ก Read the dialog top to bottom, every time

Build a two-second habit: whenever the Share dialog opens, glance at General access first. If it says "Restricted," only the named people in the list above can open the file โ€” good. If it says "Anyone with the link," anyone who gets that link can open it, invited or not. That one line tells you whether you're sharing with a few people or with the world. Reading it becomes automatic fast.

๐Ÿ‘ฅ Two Models: Specific People vs Anyone With the Link

There are exactly two ways to give access, and understanding the difference is the heart of safe sharing.

Model 1 โ€” Specific people (invite by email)

You type a person's email address into the "People with access" box, pick their role, and (optionally) send them a note. Now only that person can open the file, and only when signed in to the Google account that matches that email. If they forward the link to someone else, that someone else still can't get in โ€” they're not on the list. This is the precise, safe, on-purpose way to share, and it should be your default for anything that isn't meant for the whole world.

Model 2 โ€” Anyone with the link (general access)

You change the "General access" dropdown to Anyone with the link and pick a role. Now the file is open to anyone who has the link โ€” no sign-in, no invitation, no list. Whoever holds the link holds the access. That's genuinely useful for truly public things (a flyer, a public sign-up form, a resource you want spread widely). It's also exactly how private files leak: links get forwarded, pasted into group chats, or shared onward, and the file travels further than you ever meant.

โš ๏ธ "Anyone with the link" is a public door, not a secret one

People often assume a long, random-looking link is "basically private because nobody could guess it." Treat that assumption as false. A link is not a password โ€” it can be forwarded, copied, screenshotted, or pasted anywhere in seconds, and from then on you don't control who has it. Use "anyone with the link" only for things you would genuinely be fine seeing shared publicly. For anything personal, financial, or sensitive, use specific people instead.

graph TD A["๐Ÿ“„ A file you want to share"] --> B{"Who should reach it?"} B -->|"A few named people"| C["๐Ÿ‘ฅ Specific people
invite by email"] B -->|"Truly public / anyone"| D["๐Ÿ”— Anyone with the link"] C --> E["โœ… Only listed emails can open
forwarding the link does NOT grant access"] D --> F["โš ๏ธ Anyone holding the link can open
links forward & travel easily"] E --> G["Then pick a role:
Viewer ยท Commenter ยท Editor"] F --> G

Notice that both paths still end at the same question: what role? Choosing people-vs-link decides who can get in; the role decides what they can do once they're in. Those are two separate decisions, and good sharing means making both deliberately.

โœ… A simple rule of thumb

Default to specific people. Reach for anyone with the link only when you genuinely want something public, or when you're sharing with a big, changing group where collecting every email is impractical and the content isn't sensitive. When in doubt, name the people. It's the "share on purpose" choice.

๐ŸŽญ The Three Roles: Viewer, Commenter, Editor

Once you've decided who, you decide what they can do. Drive keeps this refreshingly simple with three roles, arranged from least to most powerful. Think of them as three levels of trust.

Role Can do Can't do Good for
๐Ÿ‘๏ธ Viewer Open, read, and (usually) download or print the file Change anything, add comments, or share it with others "Here, read this" โ€” reference docs, finished files, look-don't-touch
๐Ÿ’ฌ Commenter Everything a Viewer can, plus add comments and suggestions Edit the actual content or change sharing Feedback and review โ€” "tell me what you think, but don't rewrite it"
โœ๏ธ Editor Open, edit, add/delete content, and (by default) change sharing and add people Delete the file permanently as the owner can, or transfer ownership True collaborators who build the file with you

A few things worth burning into memory. First, Editor is powerful: by default an Editor can not only change the content but also re-share the file and add other people. That means giving someone Editor can quietly hand the keys to people you never chose โ€” which is exactly why the next lesson shows you how to switch that off. Second, Commenter is the unsung hero: for reviews and feedback it's perfect, because reviewers can say everything they want without accidentally overwriting your work. Third, the owner sits above all three โ€” the owner can do everything an Editor can plus delete the file for everyone and transfer ownership. You are the owner of files you create.

graph TD O["๐Ÿ‘‘ Owner
full control ยท delete ยท transfer ownership"] --> E["โœ๏ธ Editor
edit content + re-share by default"] E --> C["๐Ÿ’ฌ Commenter
read + comment & suggest"] C --> V["๐Ÿ‘๏ธ Viewer
read only ยท maybe download"] O -. "grants any role to others" .-> V

๐Ÿ“– Definition โ€” least privilege

Least privilege is a security idea you'll meet again in Lesson 4.3: give each person the lowest role that still lets them do their job. Someone who only needs to read? Viewer. Someone giving feedback? Commenter. Someone genuinely building the file with you? Editor. Don't hand out Editor "to be safe" โ€” that's backwards. The safe choice is the smallest role that works. It's easy to upgrade someone later; it's harder to notice you over-shared.

๐Ÿ’ก The download/print/copy nuance

By default, Viewers and Commenters can download, print, and copy the file. That's usually fine โ€” but for sensitive documents you may not want that. There's a setting to restrict it, which we cover in the next lesson. For now, just know that "Viewer" doesn't automatically mean "can't take a copy away." Sharing is a spectrum of control, and you're about to learn all the dials.

๐Ÿ—‚๏ธ Sharing a File vs Sharing a Folder

Here's a distinction that trips people up constantly, so let's make it crystal clear. You can share a single file, or you can share a whole folder โ€” and access flows downhill.

  • Share a single file โ€” only that one file is shared. The folder it lives in, and its neighbours, stay private. Precise and contained.
  • Share a folder โ€” everyone you share it with gets that same access to everything inside it: every file, and every sub-folder, and everything you add to it later. Share a folder as Editor, and your collaborator can edit every file in it, including ones you haven't created yet.

This inheritance is wonderfully convenient โ€” it's exactly how a family folder or a team project space works. Drop a new file into the shared folder and everyone already has access; no re-sharing needed. But it's also the single easiest way to over-share by accident. If you share a top-level folder like "Personal" without thinking, you may have just handed someone your tax documents, your medical PDFs, and everything you file there for years to come.

โš ๏ธ Think before you share a folder โ€” especially a big one

Sharing a folder shares everything in it, now and forever, until you change it. Before sharing any folder, ask: "Am I happy for this person to see every file I'll ever put in here?" If the answer is "only some of it," share the individual files instead, or create a dedicated shared sub-folder and only put share-safe files there. This connects straight back to Module 2: a good folder structure โ€” keeping shareable things separate from private things โ€” is what makes safe sharing effortless.

โœ… The "shared folder" pattern that works

The tidiest habit is to make a dedicated folder for a given collaboration โ€” say "Book Club" or "Q3 Project" โ€” share that folder with the group at the right role, and then simply drop files into it as they come up. Everyone stays in sync automatically, and your private files never come near it. One deliberate share, endless convenience. That's "share on purpose" applied to whole folders.

๐Ÿ” Seeing Who Has Access & Sharing on Purpose

The Share dialog isn't just for giving access โ€” it's your window into who already has it. Open it on any file and the "People with access" list shows every named person and their role, with the owner marked, and "General access" shows the link setting. If you ever wonder "wait, who can actually see this?", this is the answer, and it's always one click away. Making a habit of glancing at it is a quiet, powerful safety check.

Notify by email & the message

When you add specific people, Drive offers to notify them by email, usually with a box for a short message. Leaving notification on is polite and practical โ€” the person gets an email with a link straight to the file, so they know it exists and can find it. The message box is a great place to say what you want: "Sharing the draft โ€” could you comment on section 2 by Friday?" A shared file with no context is easy to ignore; a shared file with a clear ask gets acted on. You can also turn notification off if you're quietly organizing access and don't want to flood someone's inbox.

Sharing on purpose, in practice

Let's tie it all together into the habit this lesson is really about. Every time you share, you make three quick, deliberate decisions:

  1. Who? โ€” specific people (name the emails) or, only if truly public, anyone with the link.
  2. What can they do? โ€” Viewer, Commenter, or Editor, choosing the lowest role that works.
  3. File or folder? โ€” remembering that a folder shares everything inside it, now and later.

Three little questions, five seconds, and you've shared precisely and safely. Do it enough and it becomes automatic โ€” which is the whole goal. The people who get burned by sharing aren't careless; they just clicked "Share" without pausing on those three questions. You won't, because now you know them.

๐Ÿง  The reflex to unlearn

The dangerous habit isn't a lack of knowledge โ€” it's speed without thought: "Copy link," paste, send, done. That reflex is convenient right up until the day the link ends up somewhere you didn't expect. Replace it with a half-second pause and the three questions above. That pause is the single most valuable security habit in this whole course, and it costs you almost nothing.

๐ŸŽฏ Project: Share One File, the Right Way

Time to do it for real. You'll share one actual file with one real person as a Commenter โ€” the safe, precise, on-purpose way โ€” then inspect the access list to confirm exactly who can reach it, and reason through what the risky alternative would have exposed. Use a low-stakes file (a draft, a note, your Drive Plan from Lesson 1.1) and a person you trust โ€” a friend or family member is perfect. The point is the habit, not the file.

๐Ÿ‹๏ธ Share deliberately & inspect the access list

Objective: Perform one clean, deliberate "specific people, Commenter" share, and confirm you understand exactly who can reach the file and why "anyone with the link" would be different.

Instructions (about 15 minutes):

  1. (2 min) In drive.google.com, pick one safe, real file. Select it and open Share (the Share button, or right-click โ†’ Share).
  2. (1 min) Before typing anything, read the dialog top to bottom. Note what "General access" currently says โ€” most likely "Restricted." Good.
  3. (3 min) In "People with access," type the email of one person you trust. Set their role to Commenter (not Editor โ€” least privilege). Add a short message saying what you'd like, e.g. "Sharing this draft โ€” feel free to leave comments."
  4. (1 min) Leave notify by email on so they actually get the link, then send.
  5. (3 min) Re-open the Share dialog and inspect the access list. Confirm you see: yourself as owner, your person as Commenter, and "General access: Restricted." That combination means only the two of you can open it โ€” exactly what you intended.
  6. (3 min) Now reason (don't do it) about the alternative: if you had set "Anyone with the link" as Viewer instead, who could open the file? Write one sentence in your journal about why that would be riskier for this particular file.
  7. (2 min) Optional but great practice: change your person's role to Viewer, then back to Commenter, to feel how easy adjusting access is. You can always change or remove access later.
๐Ÿ’ก Hint โ€” what a healthy access list looks like
People with access
- You (owner)
- friend@example.com  โ†’  Commenter

General access
- Restricted โ€” Only people with access can open

What this means:
- Only you and your friend can open this file.
- If your friend forwards the link, the recipient still
  CANNOT open it (they're not on the list).
- If it said "Anyone with the link," ANYONE holding the
  link could open it โ€” invited or not.

If your access list matches the top block, you shared on purpose. That's the win โ€” precise access, no surprises, and you can see exactly who's on it.

โœ… Project Completion Checklist

  • You opened the Share dialog and read "General access" before doing anything
  • You shared with one specific person by email โ€” not a link
  • You chose Commenter (the lowest role that fits feedback), not Editor
  • You re-opened the dialog and confirmed the access list shows exactly who can reach it
  • You can explain, in a sentence, what "anyone with the link" would have exposed instead

๐ŸŽฏ Quick Quiz

Question 1: You share a file using "specific people" and your invitee forwards the link to a friend. What happens when the friend clicks it?

Question 2: A reviewer needs to give feedback on your document but shouldn't change its content. Which role fits best?

Best Practices for Sharing

โœ… Do's

  • Default to specific people. Name the emails. Reach for "anyone with the link" only when you truly want something public.
  • Pick the lowest role that works. Viewer to read, Commenter to give feedback, Editor only for real collaborators.
  • Read "General access" every time. That one line tells you whether you're sharing with a few people or the world.
  • Add a short message. Context turns a shared file from "ignored" into "acted on."

โŒ Don'ts

  • Don't treat a link like a password. Links get forwarded, pasted, and screenshotted โ€” a random-looking link is not private.
  • Don't hand out Editor "to be safe." That's backwards โ€” Editor can re-share and add people. The safe default is the smallest role.
  • Don't share a big top-level folder without thinking. A folder shares everything inside it, now and in the future.

๐Ÿ’ก Pro Tips

  • Keep a dedicated "shared" folder for a given collaboration and only put share-safe files in it. One deliberate share, endless convenience.
  • When you wonder "who can see this?", the Share dialog's access list is always one click away. Glance at it.

๐Ÿ““ 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: Think of a time you shared a file โ€” an email attachment, a link, anything. Looking back with what you now know, would you share it the same way? What's one file in your Drive right now that you might currently be over-sharing (or would want to double-check the access on)? How does "share on purpose, not by reflex" change the way you'll click Share from now on?

๐Ÿ“ Lesson Summary

๐ŸŽ“ Key Takeaways

  • Sharing turns Drive from a private cabinet into a shared home base โ€” everyone works on one real file, killing the "which version?" problem.
  • There are two access models: specific people (invite by email โ€” only listed people can open, forwarding doesn't grant access) and anyone with the link (public โ€” whoever holds the link can open it).
  • Three roles, from least to most powerful: Viewer (read), Commenter (read + comment), Editor (edit, and re-share by default). Choose the lowest role that works โ€” least privilege.
  • Sharing a folder shares everything inside it, now and in the future โ€” access flows downhill โ€” so think before sharing big folders.
  • The Share dialog also shows who currently has access. The core habit: share on purpose, not by reflex โ€” decide who, what role, and file-or-folder every time.

๐ŸŽ‰ What You've Accomplished

You now understand the single most consequential feature in Drive. You can read the Share dialog at a glance, choose between people and link deliberately, pick the right role for the right person, and reason about folder inheritance before it surprises you. You performed a real, precise share and inspected the access list to prove who can reach the file. That's not just a skill โ€” it's a safety habit that will protect you for as long as you use the cloud.

โ“ Common Questions at This Stage

If I share with "specific people," do they need a Google account?

Generally, to open a privately shared file they'll sign in with the Google account matching the email you invited โ€” and a Gmail address is a Google account. If you invite an email that isn't a Google account, Drive can sometimes offer a limited way in, but the smooth path is inviting an email tied to a Google account. For truly account-free access, "anyone with the link" avoids sign-in entirely โ€” at the cost of being public. Behaviour can also differ on a work or school Workspace account, where an admin may restrict sharing outside the organization.

Can I stop an Editor from sharing my file with other people?

Yes โ€” that's one of the controls we cover in the very next lesson. By default, Editors can add people and change sharing, which is why Editor is such a powerful, trust-heavy role. There's a setting to turn that off so only the owner manages access. If that concern is on your mind, you're thinking exactly like a careful sharer โ€” hold it for Lesson 4.2.

Is "anyone with the link" ever the right choice?

Absolutely โ€” for things you genuinely want to be public or widely spread: a public flyer, a community resource, a sign-up doc for a big open group. The rule isn't "never use it"; it's "use it on purpose." The danger is using it by reflex for something private. When the content is sensitive, choose specific people; when it's meant for the world, a link is exactly right.

๐Ÿ”ญ Looking Ahead

In the next lesson โ€” Lesson 4.2: Expiry, Restrictions & Ownership โ€” Sharing Under Control โ€” we go beyond who-and-what into the fine-grained dials: access expiration dates, stopping Viewers from downloading or copying, disabling re-sharing by Editors, transferring ownership, removing access, and auditing everything you've shared. It's sharing with the safety rails fully engaged.

โœ… Before the Next Lesson

  • Complete the project โ€” do one real "specific people, Commenter" share and inspect the access list
  • Glance at one folder you've shared in the past and confirm you're comfortable with who's on it
  • Write your Learning Journal entry for this lesson

๐Ÿ“š Additional Resources

๐ŸŒŸ Encouragement for the Journey

You just learned the skill that separates people who trust the cloud from people who fear it. Sharing isn't scary once you share on purpose โ€” and now you do. Every deliberate share you make from here builds a Drive that's both open enough to collaborate and safe enough to trust. That's a rare and valuable balance. Let's tighten the controls even further next. ๐Ÿ”—