📁 Lesson 4.2: Expiry, Restrictions & Ownership — Sharing Under Control

🎛️ From "Who Can Get In" to "Under Full Control"

In Lesson 4.1 you learned the two big decisions of sharing: who gets access (specific people vs a link) and what role they hold (Viewer, Commenter, Editor). That's enough to share safely. But real life has finer needs. You share a contract with a client — but only want them to see it for a week. You send a sensitive PDF for review — but don't want copies floating around. You add a collaborator as Editor — but don't want them inviting their whole team without asking. And sometimes you're handing a project off entirely, and the file needs a new owner.

These are the control dials, and they turn sharing from "on or off" into something you shape precisely. Think of Lesson 4.1 as choosing who gets a key; this lesson is about how long the key works, what the key doesn't unlock, whether the key-holder can cut copies of the key, and how to hand over the whole building. It's the same "share on purpose" mindset, now with the fine adjustments that let you say exactly what you mean.

⏳ Access Expiration Dates (Workspace)

An access expiration date makes a share end itself. You give someone access, set a date, and when that date arrives their access quietly disappears — no reminder to yourself, no cleanup, no "I really must unshare that eventually." It's perfect for time-boxed collaboration: a contractor on a three-month project, a client reviewing a proposal for two weeks, a candidate looking at materials during a hiring window.

You'll typically find it in the Share dialog: add or select a person, and near their role there's an option (often behind a small menu or the settings area) to set when their access expires. When the date passes, Drive removes them automatically. It's the tidiest possible way to say "you can see this, but not forever."

🚫 Restrictions: No Download, Print, or Copy

By default, anyone you share with — even a Viewer — can usually download, print, or copy the file. That's fine for most things, but sometimes you want people to read a document without being able to walk away with their own copy. A confidential report, a draft you don't want circulated, pricing you'll show but not hand over. For these, there's a restriction, typically found behind the gear/settings icon in the Share dialog: an option along the lines of "Viewers and commenters can see the option to download, print, and copy" — untick it, and those buttons disappear for them.

It's an excellent extra layer, and you should reach for it whenever a file is sensitive. But it's important to understand its honest limits, because over-trusting a control is its own kind of risk.

🔒 Disabling Re-Sharing by Editors

Here's the setting we flagged in the last lesson. By default, an Editor can re-share your file — they can add other people and change access, all without asking you. That's often desirable (real collaborators managing their own team), but it also means giving one person Editor can quietly widen the circle far beyond who you chose. If you want to stay the sole gatekeeper, you turn re-sharing off.

The control lives behind the same gear/settings icon in the Share dialog, usually worded like "Editors can change permissions and share." Untick it, and now only the owner can add people or change roles. Editors can still edit the content freely — they just can't hand out access. It's the classic move for "I want their help editing, but I decide who's in the room."

👑 Transferring Ownership

Every file has exactly one owner — normally whoever created it. The owner sits above every role: they can do everything an Editor can, plus delete the file for everyone, and transfer ownership to someone else. Sometimes you genuinely want to hand a file over: you're leaving a project, someone else is taking the lead on a document, or a shared resource should really belong to the person who now maintains it.

To transfer ownership, you first share the file with the new person as an Editor, then in the Share dialog change their role to Owner (sometimes shown as "Make owner" or "Transfer ownership"). They may need to accept. Once done, they control the file — including the power to remove you. So it's a deliberate, one-way-feeling step: give it real thought before you hand over the keys to the building.

🧹 Removing Access, Requests & Auditing

Removing access — and what it does to links

Removing access is the reverse of sharing, and it's just as important. In the Share dialog, open the menu next to a person and choose Remove access — they can no longer open the file, immediately. To make a link-shared file private again, set General access back to Restricted: the old link stops working for anyone who wasn't specifically invited. This is the crucial point — changing the link setting to Restricted effectively kills the old public link. Anyone who had it, saved it, or was forwarded it is now locked out. That's your "undo" for an over-share, and it works instantly.

Pending access requests

Sometimes someone opens a link they can't access and clicks Request access. You'll get an email, and can grant (choosing their role) or deny it. This is a genuinely nice safety pattern: instead of defaulting a file to public so nobody ever gets stuck, you can keep it Restricted and simply approve the specific people who ask. Treat each request like the three questions from Lesson 4.1 — do I know them, do they need it, and what's the lowest role that works?

Auditing what you've shared

Good sharing isn't just careful in the moment — it's reviewed over time. Drive gives you views to see the state of things. "Shared with me" in the left navigation shows files others have shared with you. To find what you've shared with others, use Search — search tools let you filter by owner (for example owner:me) and by people you've shared with — and open the Share dialog on important files to read their access list directly. Periodically walking through your most sensitive files and asking "does this list still make sense?" is the audit habit that keeps a Drive trustworthy for years.

🎯 Project: Tighten & Audit Your Shares

This project puts the control dials in your hands and builds the audit habit. Because some features are Workspace-only, we've written it so every account can complete a meaningful version — do the parts your account offers, and reason through the rest. Use the file you shared in Lesson 4.1's project as your working example.

My sharing audit
- Most sensitive shared files:
  1. ___ | who's on it? ___ | still correct? Y/N
  2. ___ | who's on it? ___ | still correct? Y/N
- Any file set to "Anyone with the link" that shouldn't be? ___
- Anyone with access who no longer needs it? Remove them.
- Any Editor who could re-share but shouldn't? Turn it off.
- Reminder set for time-boxed shares? ___

Fix now: set General access to Restricted where needed,
remove stale people, tighten roles to least privilege.

Best Practices for Sharing Under Control

✅ Do's

• Time-box access. Use expiry (or a calendar reminder) so shares don't outlive their purpose.
• Turn off re-sharing when membership matters. Stay the sole gatekeeper for sensitive files.
• Pair Viewer with "no download" for sensitive reference files. Look, don't take.
• Audit quarterly. Ten minutes reading access lists keeps risk from piling up.

❌ Don'ts

• Don't treat "no download" as a vault. It deters casual copying; it can't stop screenshots. Trust the person, not just the setting.
• Don't transfer ownership casually. The new owner can remove you — do it only when you truly mean to hand off.
• Don't assume every control is on your account. Some are Workspace-only; check what you actually have.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've moved from "I can share" to "I share exactly what I mean, and I can take it back." You know the control dials — expiry, restrictions, re-sharing, ownership — and, just as importantly, their honest limits and which are Workspace-only. You practiced the over-share undo and ran your first sharing audit. That combination of precise control and calm recoverability is what makes advanced sharing feel powerful instead of nerve-wracking.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 4.3: Shared Drives vs My Drive, and Security Best Practices — we zoom out to the two homes your files can live in: My Drive (files you own) and shared drives (files the team owns), when each wins, and then a proper security checklist — least privilege, public-link caution, phishing and fake-share awareness, and 2-step verification. It's the capstone of the whole sharing module.

✅ Before the Next Lesson

• Complete the project — apply at least one control and run your first sharing audit
• Set a calendar reminder for a quarterly 10-minute share review
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Share files from Google Drive (Google Support)
• Stop, limit, or change sharing (Google Support)
• Google Drive on Google Workspace — what's included