Skip to main content

πŸ“ Lesson 5.1: Sharing & Permissions via OneDrive

Everything you've learned so far lives inside one document. Now it's time to let other people in β€” cleanly, safely, and without emailing a dozen slightly-different copies back and forth. The secret is simpler than most people expect: real sharing and live co-authoring only happen when the document lives in the cloud, on OneDrive or SharePoint. Once it does, one Share button gives you fine control over who can see it, who can change it, and for how long.

πŸ“š What You'll Learn

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

  • Explain why a document must live on OneDrive or SharePoint before it can truly be shared or co-authored
  • Use the Share button to invite specific people or create a shareable link
  • Set view vs edit permissions, and adjust link settings like expiry, password, and block-download (as your plan allows)
  • Tell the honest difference between sending a copy and sharing a link, and know when each is right
  • Stop or manage access after the fact, and understand why a local .docx can't co-author

⏱️ Estimated Time: 40 minutes

🎯 Project: Save your report to OneDrive and share it with a viewer, then change that person from view-only to editor β€” all from the Share panel.

In This Lesson

Why the Cloud Comes First

Here's the single most important idea in this whole module, and it trips up almost everyone at first: a document that lives only on your computer cannot be truly shared or co-authored. If your file is sitting in a folder on your hard drive as report.docx, the only way to get it to someone else is to make a copy β€” attach it to an email, drop it in a chat, put it on a USB stick. The moment they open that copy, there are now two documents drifting apart: your version and theirs. Whoever edits what, you end up reconciling by hand, and the dreaded report_final_v3_JOHN_edits.docx is born.

Real sharing works completely differently. Instead of handing out copies, you keep one single document in the cloud and give people access to that same file. Everyone opens the identical document, everyone's changes land in one place, and there is never a question of "which version is current" β€” there's only ever one. For Word, that cloud is OneDrive (your personal Microsoft cloud storage) or SharePoint (the shared team storage in a Microsoft 365 work or school account, often surfaced through Teams). Both are the same idea: the document has a home on the internet, not just on your machine.

This is exactly why Word for the web already saves to OneDrive by default β€” when you create a document at microsoft365.com, it's cloud-native from the first keystroke, so it's ready to share immediately. In the desktop app, you often start with a local file, and the key move is to Save As it to OneDrive (or use AutoSave, which the desktop app can only turn on once the file lives in the cloud). Get the file into OneDrive first, and everything else in this lesson simply works.

graph LR A["πŸ“„ Local file
only on your PC"] -->|"copy it out"| B["πŸ“Ž Attachments
versions drift apart"] A -->|"Save As to OneDrive"| C["☁️ One cloud document"] C --> D["πŸ”— Share link or invite people"] D --> E["πŸ‘₯ Everyone edits the SAME file"]

🧠 Mindset

Think of the cloud document as the single source of truth. You're not giving people a photocopy; you're giving them a key to the same room. That mental shift β€” from "send a file" to "grant access to the file" β€” is what makes comments, track changes, co-authoring, and version history (the next two lessons) all possible. Get comfortable with it here and the rest of the module falls into place.

The Share Button β€” Your Two Choices

Once your document is on OneDrive or SharePoint, you'll see a Share button in the top-right corner β€” in both Word for the web and the desktop app. Click it and the Share panel opens. Everything about who can get in and what they can do lives here. There are really just two ways to share, and understanding the difference is most of the battle.

1. Invite specific people

Type in email addresses (or names, in a work/school account that knows your directory), optionally add a short message, and Word sends each person their own invitation. This is the tighter, more secure option: only the people you named can open the document, and β€” in a work or school account β€” they usually have to sign in as themselves to get in. You always know exactly who has access, and you can give different people different permissions.

2. Create a shareable link

Instead of naming people, you generate a link you can paste anywhere β€” an email, a chat message, a document. Anyone the link is set to allow can click it and open the file. Links are convenient (great for a group, a mailing list, or "just send me the link") but you're trusting whoever ends up holding the link, so you'll want to set its scope carefully β€” which is what the link settings, covered next, are for.

⚠️ Who can a link reach?

When you make a link, Word asks who it should work for. The exact choices depend on your account and your organization's policies, but you'll typically see options like Anyone with the link (no sign-in needed β€” most open, use with care), People in your organization (anyone signed in to your work/school tenant), and People you choose (only named people, even though it's a link). Personal free Microsoft accounts and managed work accounts expose different sets of these, and admins can switch some off entirely β€” so treat the list you see as the truth, and pick the narrowest option that still gets the job done.

Permissions & Link Settings

For either sharing method you choose what people can do, and for links you can layer on extra controls. The two permission levels you'll use constantly are simple:

Permission What they can do Use it when…
Can edit Open, read, type, format, comment, and co-author live in the same document You want collaborators to actually work in the document with you
Can view (read-only) Open and read the document, but not change it; usually can still add comments (plan-dependent) You want people to see the finished thing without being able to alter it

Choose Can view when you're sharing something to be read β€” a finished report, a policy, a reference β€” and Can edit when you genuinely want people writing alongside you. A good habit is to start narrow: share as a viewer, and promote someone to editor only when they actually need to change things. That's exactly what this lesson's project has you practice.

Depending on your account and version, the permission list may also include a middle option such as Can review β€” people can suggest edits (which arrive as tracked changes, next lesson) and comment, but can't change the text directly. At the time of writing its availability varies, so if you see it, treat it as a handy in-between; if you don't, Can view and Can edit cover everything this course needs.

Extra link settings (plan-dependent)

When you create a link, the settings gear on the Share panel may offer additional controls. Which of these you get depends heavily on your plan and your organization's policies β€” several are only available on paid Microsoft 365 work/school plans, and some are disabled by admins β€” so treat this table as "things you might see," not a guaranteed menu:

Setting What it does Availability
Expiration date The link automatically stops working after a date you set Common on work/school plans; often not on free personal accounts
Password The recipient must type a password you set before the link opens Typically paid/business plans; not universally available
Block download Viewers can read online but can't save a local copy of the file Generally a paid/enterprise feature on view-only links
Set/allow editing Toggles whether the link grants edit or view rights Widely available on both link types

πŸ’· Honest note on the fancy controls

Expiry, password, and block-download are genuinely useful, but they are not guaranteed on every account. If you're on a free personal Microsoft account, don't be surprised if you only see the basic view/edit choice and no password or expiry. These richer controls are mostly a Microsoft 365 business perk, and even then your admin may have turned some off. Microsoft also changes what's included over time, so check the settings your own Share panel actually shows rather than assuming a feature is there β€” and never rely on "block download" as real security; a viewer can always screenshot.

Share a Link vs Send a Copy

Right next to sharing, the Share menu (and File > Share) usually offers Send a copy β€” and it's worth being crystal clear about the difference, because choosing wrong is the number-one cause of version chaos.

Sharing a link keeps one document. Everyone you share with opens the same cloud file; edits and comments all land in that single place. This is what you want for collaboration β€” writing together, gathering feedback, keeping everyone current.

Sending a copy β€” for example File > Share > Send a copy, or attaching the file, or exporting a PDF β€” hands the recipient a separate, frozen file. Their changes never come back to your original. This is the right choice when you specifically want a snapshot: emailing a finished PDF to someone outside your organization, submitting a fixed deliverable, or handing over a document you don't want anyone editing further. Word will often offer to send it as a Word document or as a PDF right from that menu.

πŸ’‘ A simple rule of thumb

Ask yourself one question: "Do I want their changes to come back to me?" If yes, share a link to the cloud document so you all work in one place. If no β€” you just want them to have a fixed final version β€” send a copy (often as a PDF). Collaboration = link. Delivery = copy.

⚠️ The honest limit: a local .docx doesn't co-author

This is the flip side of "the cloud comes first." If you email someone a .docx attachment, or they open a file that lives only on their own machine, there is no live co-authoring, no shared comments, and no shared version history β€” because there's no single cloud document to gather it all. Each person edits their own copy in isolation. Everything powerful in this module (co-authoring in 5.2, version history in 5.3) requires the file to actually live on OneDrive or SharePoint. If collaboration feels broken, the first thing to check is almost always: is this the cloud file, or a local copy?

Managing & Stopping Access

Sharing isn't a one-way door. You can always go back and see exactly who has access and change your mind. Open the Share button again and look for Manage access (in the desktop app, depending on your version, it's in the Share dialog's menu or under File > Info > Manage Access; on the web it's in the Share panel's menu). From there you can:

  • See everyone who has access β€” named people and any active links, and what each one can do.
  • Change a person's permission β€” flip someone from Can view to Can edit or back, without re-sharing from scratch. (This is your project below.)
  • Remove a person β€” revoke one individual's access entirely.
  • Delete or disable a link β€” the moment you delete a share link, it stops working for everyone who had it. This is the fastest way to "un-share" something.
  • Stop sharing β€” pull the document back to just you.

Because it lives in one place, revoking access is instant and complete β€” something you simply can't do once you've emailed a copy out into the world. That control is one of the quiet superpowers of cloud sharing: a shared link can be un-shared, but an emailed attachment is gone forever.

graph TD A["Open Share button"] --> B{"Share how?"} B -->|"Specific people"| C["Invite by email
tighter, sign-in often required"] B -->|"Link"| D["Anyone with the link
convenient, set scope carefully"] C --> E["Set view or edit"] D --> E E --> F["Manage access later
change, remove, or stop"]

πŸ”’ A quick security habit

Every few projects, open Manage access on your important documents and skim who's still in. People change roles, projects end, and stale "Anyone with the link" links quietly linger. Deleting an old link or removing someone who no longer needs access takes ten seconds and is a genuinely professional habit.

Word Sharing vs Google Docs

If you've used Google Docs, this whole lesson will feel familiar β€” and that's the point. The concepts transfer almost directly. The honest headline difference is one of defaults and history: Google Docs was cloud-native from day one, so a Google Doc always already lives in the cloud and is instantly shareable; there's no "is this a local file?" question to ask. Word grew up as a desktop app first and added cloud collaboration later, so with Word you sometimes have to make sure the file is on OneDrive before the good stuff works.

Sharing concept Microsoft Word (OneDrive/SharePoint) Google Docs (Google Drive)
Where the file lives OneDrive or SharePoint β€” web files are cloud by default; desktop files may need "Save As" to cloud Google Drive β€” always in the cloud, always shareable
Share by Share button β€” specific people or a link Share button β€” specific people or a link
Permission levels Can view / Can edit (comment access on view is plan-dependent) Viewer / Commenter / Editor
Link controls Expiry, password, block-download β€” mostly paid business plans Expiry and copy/download limits on paid Workspace plans
The gotcha A local .docx can't co-author β€” get it into the cloud first Rarely an issue β€” everything is cloud by default

Neither is "better" β€” they're built on the same idea. Google's edge is that it removes the "make sure it's in the cloud" step because there was never any other kind of file. Word's edge is depth: the same document you collaborate on has all of Word's serious layout and reference power behind it. The reassuring truth is that once your Word document is on OneDrive, the sharing experience is genuinely on par β€” and your instincts from either app carry straight over to the other.

🎯 Project: Share Your Report

Time to do the real thing. You'll take your working report, make sure it lives on OneDrive, share it with someone as a viewer, and then promote that person to editor from the manage-access view. This exact sequence β€” start narrow, open up when needed β€” is how careful people share documents at work every day.

πŸ‹οΈ Save to OneDrive, share as viewer, then promote to editor

Objective: Get your report into the cloud and practice both permission levels and the manage-access flow.

Instructions (about 10 minutes):

  1. (2 min) Make sure your report is on OneDrive. In Word for the web it already is. In the desktop app, use File > Save As > OneDrive and give it a clear name. Confirm you can see it saving to the cloud (the title bar or AutoSave toggle will show it).
  2. (2 min) Click Share in the top-right. Choose specific people and enter a real email address you can check (a friend's, a second account of yours, or a colleague's).
  3. (2 min) Set the permission to Can view before sending. Add a short message like "Take a look β€” read-only for now" and send the invite.
  4. (2 min) Reopen Share and go to Manage access. Find the person you invited and confirm they're listed as a viewer.
  5. (2 min) Change that person from Can view to Can edit. Notice they now appear as an editor β€” you just promoted them without re-sharing.
πŸ’‘ Hint β€” what the Share panel is asking you
SHARE PANEL β€” reading it left to right

1) Who?         -> "specific people"  (type an email)
                    or "get a link"    (paste anywhere)

2) What can they do?
                    Can view  = read only  (start here)
                    Can edit  = write / co-author

3) (Maybe) link settings gear:
                    expiry / password / block-download
                    -> only if your plan shows them

TO PROMOTE SOMEONE LATER:
   Share  ->  Manage access  ->  find the person
          ->  change "Can view" to "Can edit"

No editor email handy? Use a second Microsoft account of your own, or just note the exact clicks β€” the goal is to find the view/edit control and the manage-access screen, not to spam anyone.

βœ… Project Completion Checklist

  • Your report is confirmed to be saved on OneDrive (not just a local file)
  • You shared it with at least one specific person
  • You set that person to Can view first
  • You found Manage access and located the person there
  • You changed them from viewer to editor

🎯 Quick Quiz

Question 1: Why must a Word document live on OneDrive or SharePoint before you can truly co-author it?

Question 2: You want a colleague to read your report but not change it, and you'd like to promote them to editor later if needed. What's the best approach?

Best Practices for Sharing

βœ… Do's

  • Put it in the cloud first. Save to OneDrive or SharePoint before you try to share β€” it's the step that makes everything else work.
  • Share the narrowest access that works. Start with "Can view" or "specific people," and open up only when you truly need to.
  • Share links for collaboration, copies for delivery. Ask "do I want their changes back?" β€” yes means link, no means send a copy (often a PDF).
  • Revisit Manage access. Prune stale links and people who no longer need in.

❌ Don'ts

  • Don't email .docx attachments for teamwork. That spawns drifting copies and kills co-authoring, comments, and version history.
  • Don't default to "Anyone with the link" edit access. It's the most open setting β€” use it only when you genuinely mean it.
  • Don't treat "block download" as real security. A determined viewer can screenshot; it's a nudge, not a lock.
  • Don't assume you have expiry or password. They're plan-dependent β€” check what your Share panel actually offers.

πŸ’‘ Pro Tips

  • Give the file a clear, meaningful name before you share β€” that name is what everyone will see and search for.
  • When in doubt about who can see something, the safest option is a link set to "People you choose" or an invite to named people.

πŸ““ Learning Journal

Keep a learning journal as you work through this course β€” a separate document, a note, or even a second Word file right beside the one you're building. 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 documents
  • Your progress and feelings about learning this β€” including where your confidence grew

✍️ This lesson's prompt: Think about the last time you collaborated on a document. Were you emailing copies back and forth, or working in one shared file? What went wrong β€” or right β€” and how would putting the document on OneDrive and sharing a link have changed it? Which link setting (view vs edit, expiry, or stop-sharing) do you most want to start using in your real work?

πŸ“ Lesson Summary

πŸŽ“ Key Takeaways

  • The cloud comes first. A document must live on OneDrive or SharePoint to be truly shared or co-authored β€” a local .docx can only be copied, and copies drift apart.
  • The Share button offers two paths: invite specific people (tighter, sign-in often required) or create a link (convenient, set its scope carefully).
  • Set Can view or Can edit; extra link controls like expiry, password, and block-download exist but are plan-dependent β€” mostly paid business plans.
  • Share a link when you want changes to come back to one document; send a copy (often a PDF) when you want a fixed, frozen deliverable.
  • Use Manage access to change permissions, remove people, or delete a link β€” and remember a local file can't co-author, which is why the cloud location matters.
  • Compared with Google Docs (cloud-native from day one), the concepts are the same; Word's only extra step is making sure the file is in the cloud first.

πŸŽ‰ What You've Accomplished

You can now take a document from "just on my computer" to "shared cleanly with exactly the right people." You understand the difference between a link and a copy, between view and edit, and you know how to pull access back when a project ends. That's the foundation the rest of this module is built on β€” because comments, track changes, live co-authoring, and version history all depend on that single cloud document you just learned to create and share.

❓ Common Questions at This Stage

Do I need to pay to share a Word document?

No β€” basic sharing works on a free Microsoft account with Word for the web and OneDrive. You get the core view/edit sharing and manage-access controls for free. The richer link settings β€” password, expiry, block-download β€” are mostly paid Microsoft 365 business features, and even then your organization's admin decides which are on. Prices and plan features change, so check Microsoft's current pages rather than assuming.

My colleague can't edit even though I shared it β€” what's wrong?

Check three things in order. First, is the file actually on OneDrive/SharePoint, or did they open a local copy? Second, did you set their permission to Can edit (not Can view)? Third, are they opening the shared link rather than an old emailed attachment? Nine times out of ten it's the first one β€” someone's editing an isolated copy instead of the cloud document.

Can I take back access after I've shared something?

Yes β€” that's one of the big advantages of link sharing. Open Share > Manage access and you can change anyone's permission, remove a person, or delete a link (which instantly stops it working for everyone). The one thing you can't claw back is a copy you emailed out β€” which is exactly why sharing a link beats sending an attachment for anything sensitive.

πŸ”­ Looking Ahead

In the next lesson β€” Lesson 5.2: Comments, Track Changes & Real-Time Co-authoring β€” we put that shared document to work. You'll learn modern threaded comments with @mentions, how Track Changes records every edit as reviewable markup, and how multiple people can write in the same document live. This is the heart of collaboration in Word.

βœ… Before the Next Lesson

  • Confirm your report is saved on OneDrive and shared with at least one person
  • Practice finding Manage access and switching a permission
  • Write your Learning Journal entry for this lesson

πŸ“š Additional Resources

🌟 Encouragement for the Journey

Sharing used to mean a mess of email attachments and "which version is this?" β€” and you just left that behind. One document, in the cloud, with exactly the access you choose. That's how professionals collaborate, and you can do it now. Next up: actually working together in that shared file. πŸ“