☁️ Lesson 7.2: Project — A Shared Team / Family Library

Why a Shared Library Needs a Plan

A private OneDrive only has to make sense to you. A shared one has to make sense to a whole group — and that changes everything. The moment other people can add, move, rename, and delete files, small differences in habits become chaos: three folders that mean the same thing, a file nobody can find because someone renamed it, a document deleted by accident, or worst of all, a sensitive file exposed because a link was set to "anyone with the link." A shared library succeeds or fails on its plan, not its files.

The good news is that you already have every skill you need. Module 2 taught structure; Module 4 taught sharing, roles, and the security-conscious mindset; Lesson 4.3 introduced SharePoint shared libraries. This project simply combines them into a space that's genuinely usable by more than one person and genuinely safe. The four ideas that carry the whole thing are: pick the right kind of shared space, structure it so people know where things go, invite specific people at the right roles, and review access over time.

Step 1 — Shared Folder vs SharePoint Library

Before you create anything, decide which kind of shared space fits — and this comes straight back to the account distinction we've returned to all course. On a personal Microsoft account, you share a folder that lives in your own OneDrive. On a work or school account, you usually have a better option for groups: a SharePoint shared library (often reached through a Teams team, whose Files tab is a SharePoint library).

The practical rule: a family or a couple of friends is perfectly served by a shared folder in your personal OneDrive — simple and free. A team, class, or department that will outlast any one member is far better in a SharePoint/Teams library, because the files belong to the group rather than being trapped in one person's account. If you don't have a work/school account, don't worry — a shared folder does everything this project needs, and every idea transfers.

Step 2 — Create & Structure the Library

Now build the space and give it a structure people can navigate without asking. On a personal account, create a top-level folder in onedrive.com with New > Folder — name it clearly, like Family Library or Team Files. On a work/school account, create or open a Team (or SharePoint site) and work in its Files tab. Either way, the structure principles are identical, and they're the same ones from Module 2: a few clear areas at the top, obvious names, and depth only where it's needed.

For a shared space, one extra discipline matters more than in a private one: name folders the way the group thinks, not the way you personally would. "Kids School," "Bills," "Photos," "Vacation Planning" for a family; "Projects," "Meeting Notes," "Templates," "Admin" for a team. When the folder names match how people already talk about the work, nobody has to guess.

Add one small file that pays for itself many times over: a short README or Start Here document at the top of the library. A single Word doc that says what each folder is for, where new things should go, and who owns the library removes almost every "where does this go?" question before it's asked. You'll build a richer version of this idea in the next lesson's project hub; here, keep it to a few lines.

Step 3 — Invite the Right People at the Right Roles

This is the step where careless sharing does its damage, so we do it deliberately. From Module 4 you know the golden rule: prefer Specific people (labeled People you choose in some versions — the label varies — or named members) over a broad link, and give each person the lowest role that lets them do their job. Most people in a shared library only need Can view; give Can edit only to those who genuinely add or change files.

On a personal account, open the folder's Share dialog, choose People you choose (not "Anyone with the link"), type the specific email addresses, and set the role — Can view or Can edit — before sending. On a work/school account, add people as members of the Team or grant them access to the SharePoint library, again choosing the right permission level. The pattern is the same everywhere: named people, minimum necessary role.

Step 4 — Set Expectations & Governance

Technology sets who can do things; expectations set what people actually do. A shared library stays healthy when everyone agrees on a few simple habits. You don't need a policy document — a couple of lines in your README and a quick message to the group covers it. Governance for a family or small team is really just shared courtesy written down.

Three expectations prevent most problems:

• Where things go. New files go into a folder, not the top level. If someone isn't sure, the README says where — or they ask the owner.
• How things are named. A light convention (describe the content, dates as YYYY-MM-DD) keeps a shared folder from turning into a wall of Scan_0471.pdf.
• Don't delete what isn't yours. With Can edit comes the power to delete; agree that people only remove their own files, and remember the recycle bin can recover accidents.

On a work/school or Microsoft 365 account, you also get governance controls that personal accounts don't: link expiry dates, passwords on links, and limits like Can view-only or "block download" for sensitive files (all covered in Lesson 4.2). If you're sharing something time-limited — a document only relevant this month — an expiry date means the access cleans itself up. These are excellent tools; just remember they're mostly business-account features, so hedge whether you'll see them.

Step 5 — Review Access & Avoid the Traps

Sharing isn't "set and forget." People come and go, projects end, and links you created months ago may still be live. The habit that keeps a shared library safe over time is a periodic access review — a two-minute check of who can reach what.

On the web, open the folder or file and choose Manage access to see everyone who currently has access and every active link. On a Team or SharePoint library, check the members list and any sharing links. Look for three things: people who no longer need access (remove them), links set to "anyone" that should be specific people (fix them), and anyone with Can edit who only needs Can view (downgrade them). Removing access is instant and reversible — you can always re-invite someone.

Do these five steps — choose the right kind of space, structure it, invite specific people at the right roles, set expectations, and review access — and you have a shared library that's genuinely useful and genuinely safe. It's the same care you gave your private files in the last lesson, pointed at the people you trust.

🎯 Project: Your Shared Library

Time to build one for real. Pick a genuine use — a family document folder, a shared photo space, a small team or club library — and set it up correctly end to end. If you don't have anyone to share with right now, you can simulate it: invite a second email address you own, or a friend who'll help you test, and remove them afterward. The point is to practice the safe sharing flow with a real invite.

Shared Library — safe setup checklist

CHOOSE
- [ ] Personal shared folder  OR  work/school SharePoint-Teams library
- [ ] Real use decided: ...

CREATE + STRUCTURE
- [ ] Library folder created and clearly named
- [ ] 3-5 top-level folders, named the way the group thinks
- [ ] README / "Start Here" doc at the top

INVITE (the safe way)
- [ ] Used "Specific people", NOT "anyone with the link"
- [ ] Each person got the lowest role they need
- [ ] Most people: Can view    Contributors: Can edit

GOVERN
- [ ] README lists where things go + naming + "don't delete others' files"
- [ ] (Work/365) considered expiry / password for sensitive links

REVIEW
- [ ] Opened Manage access and confirmed who can reach it
- [ ] No stray "anyone" links; no over-broad Can edit

Best Practices for Shared Libraries

✅ Do's

• Structure before you invite. Shape an empty space; don't reorganize one people are already using.
• Name folders the way the group thinks. Matching how people talk removes "where does this go?" questions.
• Invite specific people at the lowest role. Most need Can view; give Can edit only to real contributors.
• Write a short README. A few lines on where things go and who owns it prevents most confusion.

❌ Don'ts

• Don't use "anyone with the link" for anything that isn't genuinely public. It's the top way files leak.
• Don't over-grant Can edit. Editors can delete and rename; be deliberate about who gets it.
• Don't set and forget. Access that outlives its purpose is a quiet risk — review it periodically.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built a shared library the safe way — chosen for your account and group, structured so people know where things go, shared with specific people at the right roles, and set up to be reviewed rather than forgotten. This is the security-conscious sharing from Module 4 turned into a real, working space, and it's a skill that protects you and everyone you collaborate with.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 7.3: Project — A Project Hub Tying Word, Excel & PowerPoint Together — you'll bring the whole Microsoft 365 story into one place. You'll build a single project hub folder holding a Word brief, an Excel tracker, a PowerPoint deck, and an index that links them all, shared with your team and kept in sync by autosave and co-authoring. It's the capstone-warmup: proof that OneDrive makes a multi-app project feel like one coherent thing.

✅ Before the Next Lesson

• Finish creating and safely sharing your library, and confirm access in Manage access
• Remove any simulated or test access you set up
• Think of a small real project that would benefit from a shared hub of files
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• OneDrive Help & Learning (Microsoft Support)
• Share OneDrive files & folders — Microsoft Support
• SharePoint & shared libraries on microsoft.com