📽️ Lesson 6.1: Sharing & Permissions

Why Sharing Starts with the Cloud

For most of this course your deck has lived in one place and belonged to one person: you. That's fine while you're building. But a presentation almost never stays private forever — a colleague reviews it, a manager signs off on it, a teammate adds their section, an audience watches it on their own screens. The moment more than one person needs to touch a deck, you face a choice about how you let them in. Make that choice well and collaboration feels effortless. Make it carelessly and you either lock people out or, worse, leak something you meant to keep close.

The old way of "sharing" a deck was to email the file as an attachment. Everyone has done it, and everyone has felt its pain. Within a day there are five copies floating around — Pitch_final.pptx, Pitch_final_v2.pptx, Pitch_final_REALLY_final.pptx — and nobody knows which is current. Two people edit different copies and their changes can never be merged. That isn't collaboration; it's chaos with extra steps.

The modern way is to keep one deck in the cloud and give people access to that. There is a single source of truth. Reviewers comment on the real thing. Co-authors edit the same slides at the same time. And you decide, per person or per link, exactly what each of them is allowed to do. This is the model PowerPoint uses today, and it's the model Google Slides pioneered and made feel natural years ago — credit where it's due. PowerPoint has closed that gap: through the web app and Microsoft 365, backed by OneDrive, live sharing and co-authoring now work genuinely well. But all of it rests on one prerequisite: the deck has to live in the cloud first.

Save to OneDrive — the Prerequisite

OneDrive is Microsoft's cloud storage, and it comes free with any Microsoft account. When your deck lives on OneDrive rather than only on your hard drive, three things become possible that simply cannot happen with a local file: it autosaves as you work, it keeps a version history you can roll back to (that's Lesson 6.3), and — the reason we're here — it can be shared and co-authored live. Every collaboration feature in this module depends on this one step. A deck sitting on your desktop can only be emailed as a copy; a deck on OneDrive can be genuinely shared.

If you're on PowerPoint for the web

Good news: you're already there. When you create a deck at microsoft365.com or office.com, it's born on OneDrive automatically and autosaves from the first keystroke. You'll see the file name in the top bar and an AutoSave or Saved indicator. There's nothing extra to do — the web app has no concept of a deck that isn't in the cloud. This is one of the quiet advantages of working on the web: the sharing story "just works" because the storage story already did.

If you're on the desktop app

A desktop deck often starts life on your local drive, so you save it up to the cloud deliberately. Use File > Save As (or File > Save a Copy) and choose OneDrive as the location rather than This PC. Once the deck is on OneDrive, flip the AutoSave toggle in the very top-left corner to On. From that moment your changes stream to the cloud continuously, and the Share button lights up with its full set of options. If AutoSave is grayed out, that's the tell-tale sign your deck is still local — save it to OneDrive and the toggle comes alive.

The Share Button: Invite vs Get a Link

With the deck on OneDrive, find the Share button — top-right in both the web app and the desktop app. Clicking it opens the sharing panel, and this is the control center for everything in this lesson. The panel offers two fundamentally different ways to let people in, and understanding the difference is most of the battle.

Invite specific people (share by email)

Type one or more email addresses into the "Add people" box, optionally add a short message, and send. Each person receives an email with a link that is tied to them. This is the tighter, safer option: access is granted to named individuals, you can see exactly who has it, and — depending on your settings — a recipient may need to sign in to prove they're really that person. Reach for invite-by-email whenever the audience is known and the content is even slightly sensitive. It's the default you should prefer.

Get a link (copy-and-paste sharing)

The other option is Copy link: PowerPoint generates a single URL you can paste anywhere — a chat message, a document, a calendar invite, an email you write yourself. This is wonderfully convenient when you need many people to reach the deck quickly, or when you don't have everyone's email address. But convenience cuts both ways: a link is a key, and anyone who ends up with that key can use it to the extent its permissions allow. Forwarded, screenshotted, pasted into the wrong channel — a link travels further and faster than you expect. Use it deliberately, and use the narrowest scope that still gets the job done.

The two methods aren't rivals — they're for different situations. Invite-by-email for a defined group and anything confidential; get-a-link for broad, low-stakes distribution where friction would slow everyone down. A useful instinct: the more sensitive the deck, the more you lean toward named invites over open links.

Permission Levels & Link Scope

Whichever way you let people in, two independent dials control what happens next: the permission level (what a person may do) and, for links, the scope (which people the link works for). Keep them separate in your mind — mixing them up is where sharing accidents come from.

Permission level — what they can do

The rule of thumb is simple and worth tattooing on your brain: grant the least access that still lets the person do their job. If someone only needs to read the deck, give them Can view. If they need to leave feedback but shouldn't rewrite your slides, Can review (a Microsoft 365 refinement) is ideal where your Share panel offers it — they comment, you stay in control of the content. If it isn't offered for your deck, give Can edit with a "comment, don't change" agreement and lower it again when the review is done. (Note that Can view is read-only: a viewer can't add comments.) Reserve Can edit for the people actually co-building the deck with you. Being generous with edit access feels friendly, but every editor is someone who can accidentally delete your title slide.

Link scope — who the link works for

When you choose Get a link, a "Link settings" control lets you narrow who the link is valid for. The exact wording shifts between personal and work accounts, but the ladder is consistent, from widest to narrowest:

• Anyone with the link — no sign-in required; whoever holds the URL gets in. Maximum reach, minimum control. Fine for genuinely public content, risky for anything else. On work/school accounts an admin may disable this entirely.
• People in your organization — the link only works for signed-in members of your company or school. A sensible default at work: broad enough to be convenient, closed to outsiders.
• Specific people — the link works only for the named individuals you list, each of whom signs in to prove who they are. This is the tightest link scope and behaves much like invite-by-email.

Read the diagram as a habit, not a one-off: every time you share, you're answering two questions in sequence — who gets in (scope), then what they can do (permission). Answer them narrowly by default and widen only when there's a real reason. That single discipline prevents the large majority of oversharing mistakes.

Expiry, Passwords & Stopping Sharing

Sharing isn't a one-time act you set and forget — it's a relationship you can adjust and end. A few extra controls let you put limits on a link up front, and, just as importantly, let you take access back later.

Expiry dates and passwords (Microsoft 365)

On many Microsoft 365 plans, the link settings include two extra guards. An expiration date makes a link stop working automatically after a day you choose — perfect for "here's the deck for this week's review, and it goes dead on Friday." A password requires anyone opening the link to type a secret you set and share separately (never in the same message as the link itself). Some plans also offer block download, which lets people view the deck but not save a local copy. These are genuinely useful for sensitive material — but be honest with yourself about which plan you have: expiry, password, and block-download are 365 features and are typically absent from free personal accounts. If you don't see them, that's why. As always, we don't quote what any plan costs; check Microsoft's current pages if you need the paid tiers.

Reviewing and stopping sharing — the skill people forget

The most overlooked sharing skill isn't granting access; it's revoking it. Open Share > Manage access (in the web app, it's inside the Share panel; on desktop, the same "Manage access" link) and you'll see everyone who currently has access and at what level. From there you can:

• Change a person's level — bump someone from Can edit down to Can view once their editing is done.
• Remove a person — revoke an individual's access entirely.
• Delete a link — the moment a link is removed, it stops working for everyone who had it, no matter how far it traveled. This is your emergency brake.
• Stop sharing altogether — return the deck to private, just you.

Make it a habit to visit Manage access when a project ends. Old links and stale editors accumulate quietly, and a link you shared for a workshop last spring shouldn't still open your deck next year. Closing doors you've finished with is as much a part of good sharing as opening them.

Sharing the Live Deck vs Sending a Copy

There's a final distinction that trips people up, because both live behind the same Share button: are you sharing the living deck, or handing someone a frozen copy? They serve different purposes and it's worth being deliberate about which you mean.

Sharing the live deck

This is everything we've discussed so far: the recipient reaches your actual deck on OneDrive. They always see the current version, your edits appear for them, and — if you granted edit or review access — they can contribute back to the one true copy. This is the right choice for anything ongoing: a deck still being built, one under review, one a team owns together. There's only ever one version, and it's the real one.

Sending a copy — download and hand off

Sometimes you deliberately want to freeze a moment and hand it over with no strings attached — a final deck for someone's records, a version to attach to a formal email, a file for a system that only accepts uploads. Use File > Download (web) or File > Save a Copy / Export (desktop) to save a .pptx, or a PDF if it should be read-only and un-editable. A downloaded copy is disconnected: your later changes won't reach it, and their changes won't reach you. That's exactly the point when you want a clean handoff — but it's the wrong tool for collaboration, because you're right back in the world of "which version is current?" that OneDrive sharing exists to end.

🎯 Project: Share a View-Only Link

Time to do the thing for real — safely. You'll confirm your deck is on OneDrive, create a view-only link with the narrowest scope that makes sense, and then test it the way a recipient would. Sharing you haven't verified isn't really shared; testing it is what separates confident sharing from hoping.

Before I copy any link, I check:

WHO can get in (scope)?
- [ ] Anyone with the link        (widest — public only)
- [ ] People in my organization   (safer default at work)
- [ ] Specific people             (tightest — named + sign-in)

WHAT can they do (permission)?
- [ ] Can view      (read / present only)   <-- this project
- [ ] Can review    (comment, no edits) [365, if offered;
                     otherwise Can edit + "comments only"]
- [ ] Can edit      (full co-authoring)

Extra guards (365 only, if offered):
- [ ] Expiry date set?
- [ ] Password set (sent separately)?
- [ ] Block download?

Then, and only then: Copy link.

Best Practices for Sharing

✅ Do's

• Share the least access that does the job. Default to Can view; upgrade to review (or edit) only when there's a real need.
• Prefer named invites for anything sensitive. Invite-by-email ties access to real people you can see and remove.
• Revisit Manage access when a project ends. Delete stale links and drop editors who are done — good hygiene, not paranoia.

❌ Don'ts

• Don't reach for "Anyone with the link, Can edit" by reflex. It's the highest-risk setting; use it only when you genuinely mean "the whole world may change this."
• Don't send a password in the same message as the link. That defeats the password entirely — deliver it by a separate channel.
• Don't email copies for a deck that's still evolving. That's how five conflicting versions are born. Share the one live deck instead.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

Your deck is no longer a private file — it's a shareable, cloud-hosted presentation, and you can hand it to exactly the right people at exactly the right level of access. More importantly, you've built the safety instincts that make sharing feel calm instead of nerve-wracking: least access by default, named invites for sensitive content, and a habit of reviewing who can get in. That judgment is what turns a feature into a skill.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 6.2: Comments & Real-Time Co-Authoring — we move from granting access to actually working together inside the deck. You'll learn to leave comments and @mention people to assign feedback, to reply and resolve threads, and to co-edit the same deck live — seeing collaborators' cursors and presence in real time — with the etiquette that keeps a shared deck from turning into a mess.

✅ Before the Next Lesson

• Confirm your deck is on OneDrive and you can produce a working view-only link
• If you have a willing friend or colleague, line them up to co-edit with you next lesson — and raise their access above Can view (to Can edit, or Can review if offered), because a view-only link can't comment or edit
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• PowerPoint Help & Learning (Microsoft Support)
• OneDrive Help — sharing files & folders
• Microsoft 365 plans & current pricing