☁️ Lesson 4.3: SharePoint & Shared Libraries, and Security Best Practices

Whose File Is It? Personal vs Shared

Here's a question that quietly decides where content should live, and most people never ask it: whose file is this, really? Some files are genuinely yours — your tax return, your personal photos, a draft only you touch. Others only feel like yours because they happen to sit in your OneDrive, but they actually belong to a team — the department's shared budget, the project's assets, the family's photo archive. That distinction, "mine vs ours," is the whole point of this lesson's first half.

Why does it matter? Because personal OneDrive is tied to you. On a work/school account especially, your OneDrive is your space — and if you leave the company, change roles, or your account is closed, everything living only in your personal OneDrive is at risk of going with you. Imagine the team's crucial spreadsheet lived in one person's OneDrive, shared out to everyone. It works fine — until that person leaves, their account is deactivated, and suddenly the file nobody else "owned" is locked away or gone. This is the single most common storage mistake organizations make.

The answer is to match ownership to reality. Content that belongs to you lives in your OneDrive. Content that belongs to a team should live somewhere the team owns — a place that doesn't disappear when one person does. On Microsoft 365 work/school accounts, that place is a SharePoint shared library. Getting this right isn't bureaucracy; it's the difference between team content that survives and team content that's one resignation away from being lost.

SharePoint & Shared Libraries

SharePoint is Microsoft's platform for team and organization content, and it comes with work/school Microsoft 365 accounts — it's not part of a personal Microsoft account. Where OneDrive is your cloud home base, SharePoint provides shared libraries (also called document libraries) that belong to a site — a space set up for a team, a department, or a project. The files in a shared library are owned by the organization, and managed through membership in the site, not by one individual's personal permissions.

The good news is that a shared library feels almost exactly like OneDrive to use. It shows files and folders, you upload and create the same way, you can open Word/Excel/PowerPoint files right there, and it appears in the same web experience and the same sync client. The difference is underneath: instead of "these are my files that I've shared with you," a shared library says "these are our files, and you have access because you're a member of this team." Add a new colleague to the team and they get the whole library automatically; remove them and access is gone — no per-file sharing to manage.

Teams-Connected Libraries

If your organization uses Microsoft Teams, you've already been using SharePoint without realizing it. Every Team has a Files tab in each channel — and that Files tab is a folder in a SharePoint shared library behind the scenes. When you drag a file into a Teams channel or save something from a Teams meeting, it lands in that Team's shared library, owned by the organization, available to every member of the Team. Teams is the friendly front door; SharePoint is the filing cabinet behind it.

This connection is worth internalizing because it demystifies a lot. "Where did that file I posted in Teams go?" — into the Team's SharePoint library. "Why can everyone in the channel see it?" — because they're all members of the Team, and membership grants library access. "Is it safe if I leave?" — yes, because the Team (the organization) owns it, not you. Teams, SharePoint, and OneDrive aren't three separate storage systems; they're three doors into the same Microsoft 365 storage, differing mainly in who owns what's behind the door.

When to Use Which

So you've got a file in your hands and a decision to make. The question is always the same — whose file is it? — and the answer routes you to the right home. Here's the decision, in the form you'll actually use it.

Read the diagram as a habit, not a flowchart to memorize. Personal, only-yours content stays in your OneDrive — shared out to a few named people when needed, with least privilege. Team or organizational content, on a work/school account, belongs in a shared library so it's owned by the team and survives anyone leaving. And on a personal account, the equivalent of a shared library is simply a dedicated shared folder in your OneDrive — one you set up on purpose for the group, kept separate from your private areas (which is exactly why the clean folder structure from Module 2 matters here).

The failure mode to avoid is the "accidental shared library" — team content that lives in one person's OneDrive and gets shared around because it was convenient in the moment. It works right up until that person leaves, and then it doesn't. If you catch yourself sharing the same OneDrive folder with the same group over and over, that's a signal: on work/school, this content wants a shared library; on personal, it at least wants a clearly labeled shared folder that everyone understands is the shared space.

Security Best Practices

This is the section that ties all of Module 4 together — the durable habits that keep your cloud safe long after you've forgotten the exact menus. None of these is complicated. Together they're the difference between a cloud you can trust and one that quietly leaks.

1. Share with least privilege

The heartbeat of the whole module: give the smallest access that does the job. Prefer People you choose over "Anyone with the link." Prefer Can view over Can edit. Ask "who genuinely needs this, and what do they genuinely need to do?" — and answer narrowly. Every extra bit of access you grant is a bit of risk you take on for no benefit.

2. Review access regularly

Because a link can travel and shares don't clean themselves up, schedule a periodic look at what you've shared. Open OneDrive's Shared view and spot-check important items in Manage access. Quarterly is plenty for most people. Retire anything that's outlived its purpose — the share you set up for a two-week project shouldn't still be live two years later.

3. Watch "anyone with the link" the hardest

This is the setting that causes the leaks, so it deserves special vigilance. Treat every "Anyone with the link" share as public until proven otherwise. Use it only for content you'd be fine seeing anywhere, and when you do, add an expiry (and a password, where available). Better yet, ask whether "People you choose" would work instead — it usually does, and it removes the open door entirely.

4. Be careful with sensitive information

Some things simply shouldn't be shared casually, or sometimes at all: financial records, identity documents, passwords, health information, anything covered by a workplace confidentiality rule. For these, combine controls — a narrow audience, Can view, block download, an expiry — and think twice before any wide share. The safest place for the most sensitive material is not widely shared in the first place. No control replaces good judgment about what belongs in a shared file at all.

5. Protect the account itself with MFA

All the sharing discipline in the world doesn't help if someone gets into your account, so secure the account itself. Turn on multi-factor authentication (MFA) — the "second step" beyond your password, like a code from an authenticator app or a prompt on your phone — for your Microsoft account. (On a personal Microsoft account the setting is called two-step verification; work and school accounts usually say MFA. Same idea, two names.) It's the single highest- value security step you can take, because it means a stolen password alone isn't enough to get in. Use a strong, unique password too, and be alert to phishing emails that try to trick you into signing in on a fake page. Your account is the front door to everything in your cloud; lock it well.

Google Drive Shared Drives — Honestly

If you've used Google Workspace, this whole lesson has a clean parallel, and it's worth naming so your skills transfer both ways. Google Drive draws the exact same "mine vs ours" line: My Drive is your personal space (like personal OneDrive), and Shared drives (available on some Workspace business plans) are team-owned spaces where files belong to the team, not the individual who created them — just like SharePoint shared libraries. The reasoning is identical: content that a team depends on shouldn't live in one person's My Drive, because it's at risk when that person leaves.

The honest comparison: for organizations already living in Microsoft 365, Office, and Teams, SharePoint shared libraries are the natural, deeply integrated home for team content — they're woven into Teams, the Office apps, and the Windows sync client. For organizations on Google Workspace, Shared drives play the same role and integrate tightly with Docs, Sheets, and Slides. Neither is "better" in the abstract; each is best inside its own ecosystem. And crucially, the concept transfers perfectly: once you understand "team content belongs in a team-owned space, not a personal one," you'll make the right call on either platform.

🎯 Project: Explore or Audit

This project adapts to your account, because the right hands-on work depends on which one you have. If you're on a work/school account, you'll go explore a real shared library and feel the "team-owned" difference. If you're on a personal account, you'll do something arguably more valuable: audit your existing shares and tighten anything that's over-shared — putting this whole module into practice on your real OneDrive.

For each important file or folder, ask:

WHOSE is it?
  [ ] Only mine        -> personal OneDrive (private, or share to named people)
  [ ] A team's / org's -> shared library (work/school) or a dedicated shared folder (personal)

HOW is it shared right now?  (Manage access)
  [ ] Anyone with the link?  -> can I make it "People you choose" instead?
  [ ] Can edit?              -> do they really need edit, or is view enough?
  [ ] Still needed at all?   -> if not, Stop sharing

ACCOUNT security:
  [ ] MFA turned on for my Microsoft account?
  [ ] Strong, unique password?

Best Practices for Team Content & Security

✅ Do's

• Match ownership to reality. "Mine" goes in OneDrive; "ours" goes in a shared library (or a dedicated shared folder on personal accounts).
• Keep team content out of personal OneDrive where you can — it shouldn't depend on one person's account surviving.
• Turn on MFA and use a strong, unique password for your Microsoft account.
• Review your shares on a schedule — Shared view + Manage access, quarterly.
• Work with your admin's policies on a work/school account rather than around them.

❌ Don'ts

• Don't let a team depend on files in one person's OneDrive — that's the "accidental shared library" trap.
• Don't leave "anyone with the link" shares unwatched — treat them as public.
• Don't share sensitive information casually — combine controls, or don't share it at all.
• Don't rely on a password alone for your account — add MFA on top.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've finished Module 4 with the full picture of sharing and security — not just how to open and close doors, but where content should live in the first place and how to keep your account safe. You can tell "mine" from "ours," you know that team files belong in a team-owned home, and you've done a real audit of your own sharing. That's a genuinely professional understanding of cloud safety — the kind that prevents the mishaps other people learn about the hard way.

❓ Common Questions at This Stage

🔭 Looking Ahead

With Module 4 complete, we move from sharing to sync — the final stage of our through-line. In the next lesson — Lesson 5.1: The OneDrive Sync Client & Files On-Demand — you'll meet the little cloud icon in your taskbar or menu bar, learn how the sync client keeps the same files on every device, and discover Files On-Demand: the clever feature that shows you every file without filling your hard drive, letting you choose what's online-only, locally available, or always kept on this device.

✅ Before the Next Lesson

• Complete your project (explore a shared library, or audit and tighten your shares)
• Confirm MFA is on for your Microsoft account, or note to enable it
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• OneDrive Help & Learning (Microsoft Support)
• SharePoint Help & Learning (Microsoft Support)
• Set up two-step verification for your Microsoft account