π Lesson 6.1: Sharing & Permissions
This is the module where Google Slides quietly pulls ahead of almost every other presentation tool: sharing. In this lesson you'll learn to hand your deck to exactly the right people, at exactly the right level of access β a viewer who can only look, a commenter who can leave comments and suggested wording, an editor who can build alongside you β and to do it deliberately, so a link never travels further than you meant. By the end you'll have shared your running deck the smart way and inspected precisely who can see it.
π What You'll Learn
By the end of this lesson, you will be able to:
- Open the Share dialog and share a deck with specific people by email
- Explain the difference between named sharing and "anyone with the link", and when each is appropriate
- Choose the right role β Viewer, Commenter, or Editor β for each person
- Change or remove someone's access, restrict link settings, and understand ownership transfer and expiry
- Share thoughtfully around sensitive information, and know when to present to a group versus collaborate with them
β±οΈ Estimated Time: 40 minutes
π― Project: Share your running deck appropriately β send a Commenter link to a friend or classmate β and then open the access list to confirm exactly who can see it and at what level.
In This Lesson
π€ Why Sharing Is the Whole Point
Back in Lesson 1.1 we said the thing Google Slides does better than almost anything else is collaboration β many people, one live deck, no emailed copies. That promise is cashed in right here. A deck sitting in your Drive that nobody else can open is just a private document. The moment you share it, it becomes a shared source of truth: a pitch a whole team polishes together, a class project everyone contributes a slide to, a report your manager comments on before the big meeting.
But "sharing" is not one action β it's a small set of deliberate decisions. Who gets in? Named people, or anyone who holds the link? What can each of them do β just look, comment, or edit freely? And for how long? Getting these right is the difference between smooth collaboration and an awkward "wait, who edited my title slide?" (or worse, a confidential deck reaching someone it shouldn't).
The good news: the mental model is simple and it maps onto the same idea we've used all course. Sharing is just choosing who Γ what they can do. Nail those two axes and everything else β link settings, ownership, expiry β is a refinement.
π§ Mindset
Think of your deck like your house. A Viewer can look through the window. A Commenter can stand in the doorway and leave a note on the table. An Editor has a key and can rearrange the furniture. You wouldn't hand a house key to a stranger, and you don't have to hand out editor access to let someone see your slides. Sharing well means giving each person the least access that lets them do their job β a habit that keeps your work safe without slowing anyone down.
π The Share Button & Two Ways to Share
Open any deck and you'll find a prominent Share button in the top-right corner (it may show as a person-with-a-plus icon on a narrow screen). Click it and the Share dialog opens. This one dialog is the control center for everything in this lesson. It has two distinct halves, and understanding the split is the key to sharing confidently.
1) Share with specific people (by email)
At the top of the dialog is a box that says something like "Add people and groups." Type a person's email address (or a name from your contacts / Workspace directory), choose their role from the dropdown, and send. This is named sharing: only that specific Google account gets access, they sign in to prove it's them, and you can see and manage each person individually. This is the safest, most precise way to share β you know exactly who is in.
2) General access β "Anyone with the link"
Lower in the dialog is the General access section. By default a new deck is Restricted: only the named people above can open it. Switch it to Anyone with the link and the deck becomes reachable by anyone who has the URL β no sign-in required. You then set what those link-holders can do (Viewer, Commenter, or Editor). Copy the link and paste it anywhere, and it just works. This is wonderfully convenient β and exactly where you must be deliberate, because a link can be forwarded, pasted into a chat, or screenshotted.
π‘ Named vs link, in one line
Named sharing = a guest list. Only people you invited, each signed in, each manageable. Link sharing = a door that anyone holding the key can open. Fast to hand out, but the key can be copied. Use named sharing for anything you care about; use link sharing for things you're happy for a wider, less-controlled group to see.
β οΈ Important Note: If you're using Slides through a work or school Google Workspace account, your organization's admin may limit link sharing β for example, restricting "anyone with the link" to people inside your organization only, or blocking external sharing entirely. That's a feature, not a bug: it stops confidential decks leaking outside the company. If an option is grayed out, that's usually why.
π The Three Roles: Viewer, Commenter, Editor
Whichever way you share, you assign a role that decides what the person can do. There are three, and they form a simple ladder from least to most power. Choosing the right rung is the single most important sharing decision you make.
| Role | Can do | Cannot do | Reach for it when⦠|
|---|---|---|---|
| π Viewer | Open and read the deck, present it, download a copy | Change anything, add comments, or see others' comments | You want people to see the finished deck but not touch it β an audience, a client review, a public share |
| π¬ Commenter | Everything a Viewer can, plus add comments (including suggested wording), reply, and @-mention | Edit the slides themselves β move, delete, or retype content | You want feedback without risking your layout β reviewers, a manager, a friend giving notes |
| βοΈ Editor | Everything, plus add/delete/reorder slides, edit content, change the theme, and (usually) share the deck onward | Delete the file outright or (unless made owner) transfer ownership | You're genuinely building together β a co-presenter, a project teammate, a designer |
Here's the habit worth burning in β it's the through-line of this whole module: comment, don't overwrite. When someone's job is to give feedback, make them a Commenter, not an Editor. Comments sit beside the deck as a conversation you can accept, discuss, or dismiss; they never silently change your slides. An editor who "helpfully" retypes your title has overwritten your work with no discussion. Default people to the lowest role that lets them help, and promote only when real co-building begins.
look Β· present Β· download"] A --> C["π¬ Commenter
everything a Viewer can
+ comment Β· reply Β· @-mention"] A --> D["βοΈ Editor
everything a Commenter can
+ edit Β· reorder Β· restyle Β· reshare"] B --> E["π‘οΈ Rule of thumb:
give the LEAST access
that lets them help"] C --> E D --> E
β Pro Tip
Roles stack like a staircase: every Commenter can do everything a Viewer can, and every Editor can do everything a Commenter can. So the question is never "which powers does this person need?" but simply "how high on the staircase do they need to stand?" Ask that and the right role is obvious.
π§ Managing Access: Changing, Removing & Restricting
Sharing isn't a one-time act β access is something you tend over the life of a deck. Reopen the Share dialog any time and you'll see the current list of everyone who has access, each with their role beside them. From here you can adjust things as the project changes.
Changing someone's role
Next to each person is a role dropdown. Promote a reviewer from Commenter to Editor once real co-building starts, or demote an Editor back to Viewer once their work is done. Changes take effect immediately β the next time they open the deck, their access reflects the new role.
Removing access
To revoke someone entirely, open that same dropdown and choose Remove access. They lose the ability to open the deck at once. This is your clean "the collaboration is over" button β use it when a project wraps, when someone leaves the team, or the moment you realize a deck was shared too widely.
Restricting the link
If you turned on "Anyone with the link," you can dial it back at any time by switching General access back to Restricted β instantly, the link stops working for everyone except the named people on your list. You can also lower the link's role (say, from Editor to Viewer) without turning it off. And on the Viewer/Commenter side there's often a setting to prevent viewers and commenters from downloading, printing, or copying the deck β useful for a deck you want seen but not saved offline.
β οΈ Watch Out
Restricting a link does not un-send what people already have. Anyone who downloaded a copy, screenshotted a slide, or made their own copy while access was open still has that. Revoking access closes the door going forward; it can't reach back and erase copies already made. That's exactly why the earlier advice matters: be deliberate before you share sensitive material, not just after.
π Ownership, Expiry & Advanced Controls
Two more controls round out the picture. You won't need them every day, but knowing they exist saves you a real headache someday.
Transferring ownership
Every deck has exactly one owner β by default, the person who created it. The owner has powers no one else does: deleting the file for good, and transferring ownership itself. To hand a deck off β you're leaving a team, or a colleague is now the true keeper of the master pitch β make them an Editor first, then use the role menu's Transfer ownership option. Google sends them an ownership request; only once they accept do they hold the keys, and you become a regular Editor. It's a deliberate, two-sided step precisely because it's a big one.
Expiring access (Google Workspace)
On Google Workspace accounts, you can set an expiration date on a person's access β perfect for a contractor, a temporary reviewer, or an external partner who only needs the deck for a defined window. Come the date, their access simply switches off, no cleanup required. This is a paid-tier convenience; on a free personal account you achieve the same thing manually with the "Remove access" button when the time comes.
π‘ Free vs paid, honestly
Everything core in this lesson β named sharing, link sharing, all three roles, changing and removing access, ownership transfer β works on a free personal Google account. A few finer-grained controls (timed expiry, and some organization-wide sharing restrictions) live in Google Workspace business and education editions. Features and availability shift over time, so check Google's current sharing page rather than trusting any fixed list.
π€ Present To vs Collaborate With β and Sharing Safely
A subtle but freeing idea: you don't have to share a deck to show it to people. There are two very different situations, and matching your sharing to the situation prevents most mistakes.
Presenting to a group
If you're standing in front of a room, or screen-sharing on a video call, your audience simply watches β you're driving. They need no access to the file at all. If you also want to send the deck afterward "for reference," share it as Viewer (or export a PDF). Nobody needs edit rights to sit in the audience.
Collaborating with a group
If several people are genuinely building the deck β the team pitch, the group project β that's where you share as Editor and lean into real-time co-editing (the whole of next lesson). Even then, reviewers who only give notes stay Commenters. Editing is for builders; commenting is for advisers.
β οΈ Honest security notes
- A link can travel. "Anyone with the link" means anyone it's ever forwarded to. Treat such a link as semi-public.
- Be deliberate. Default to named sharing and the lowest useful role. Widen access on purpose, never by accident.
- Sensitive info doesn't belong in a widely shared deck. Passwords, unreleased financials, personal data, anything confidential β either keep it in a Restricted, named-only deck or leave it out entirely.
- Check the list before a big send. Ten seconds in the Share dialog confirming who has access and at what level is the cheapest insurance there is.
- Publishing to the web is fully public (covered in Lesson 5.3 and again in 6.3) β a different, more open thing than link sharing.
β Pro Tip
When in doubt, share narrow and widen later. It's trivial to promote a Viewer to Editor when they turn out to need it, but you can never fully un-share a link that's already gone out. Under-sharing is a two-second fix; over-sharing can be permanent.
π― Project: Share the Deck & Inspect Access
Time to put your running deck in someone else's hands β safely and deliberately. You'll send a Commenter link to a friend or classmate (so they can give feedback without touching your slides), then open the access list to confirm exactly who's in and at what level. This is the "comment, don't overwrite" principle in action, and it sets up next lesson's live collaboration beautifully.
ποΈ Share your deck as a Commenter
Objective: Give one trusted person Commenter access to your running deck, then audit the access list.
Instructions (about 12 minutes):
- (1 min) Open your running deck and click the Share button in the top-right corner.
- (3 min) In "Add people and groups," type the email address of a friend, classmate, or a second account of your own. Set their role to Commenter using the dropdown. Add a short note like "Would love your feedback on slide 3!" and send.
- (2 min) Alternatively (or additionally), set General access to "Anyone with the link" and lower its role to Commenter, then copy the link and share it directly with your person. Notice how this is more convenient but less controlled than naming them.
- (3 min) Reopen the Share dialog and read the access list: who has access, and what role each holds. Confirm your reviewer is a Commenter and not an Editor β that's the whole point.
- (2 min) Practice the management controls: change your reviewer's role once (e.g. to Viewer and back to Commenter), and locate the Remove access option so you know where the "off switch" lives. Leave them as Commenter when done.
- (1 min) Ask your person to leave one comment on a slide so you can see it arrive β a preview of Lesson 6.2.
π‘ Hint β a quick sharing checklist to run in your head
Before I click Send / Copy link, I asked:
WHO gets in?
- [ ] Specific person by email (named) ... or
- [ ] Anyone with the link (semi-public)
WHAT can they do?
- [ ] Viewer (look only)
- [x] Commenter (feedback, no editing) <- for reviewers
- [ ] Editor (build alongside me)
Is there anything SENSITIVE on these slides?
- [ ] No -> safe to share
- [ ] Yes -> keep it Restricted / named-only, or remove it
After sharing: reopen Share and read the access list.
No second person handy? Use a second Google account of your own (a different Gmail) as the "reviewer." Everything works identically, and you get to see both sides of the exchange.
β Project Completion Checklist
- You opened the Share dialog and shared your running deck with at least one person
- That person's role is Commenter β not Editor β so they can comment but not overwrite
- You reopened the dialog and read the access list, confirming who has access and at what level
- You located both the role dropdown and the "Remove access" control
- You paused to check nothing sensitive was exposed by the way you shared
π― Quick Quiz
Question 1: You want a colleague to give feedback on your deck but you're worried they might accidentally change your carefully arranged layout. Which role should you give them?
Question 2: You set a deck to "Anyone with the link," then later switch it back to "Restricted." What's the honest limitation of that revocation?
π§ Best Practices for Sharing
β Do's
- Default to named sharing. A guest list you can see and manage beats a link you can't recall.
- Give the lowest useful role. Viewer for audiences, Commenter for reviewers, Editor only for co-builders.
- Audit the access list before a big send. Ten seconds confirming who's in is the cheapest insurance there is.
β Don'ts
- Don't make reviewers Editors. Feedback belongs in comments, not silent overwrites β comment, don't overwrite.
- Don't treat "anyone with the link" as private. A link can be forwarded anywhere; assume it's semi-public.
- Don't put truly sensitive info in a widely shared deck. Keep it Restricted and named-only, or leave it out.
π‘ Pro Tips
- Share narrow, widen later β under-sharing is a two-second fix; over-sharing can be permanent.
- Add a friendly note when you share by email; it turns a cold notification into an invitation.
π Learning Journal
Keep a learning journal as you work through this course β a separate document, a note, or even a slide at the end of the deck 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 decks
- Your progress and feelings about learning this β including where your confidence grew
βοΈ This lesson's prompt: Think of a real deck you've shared (or been shared on) in the past. Was the access level right β or did someone have more power over it than they needed? Now that you know the Viewer / Commenter / Editor ladder, how will you share your running deck differently, and who would you trust with each role? Note any moment where "share narrow, widen later" would have saved you a headache.
π Lesson Summary
π Key Takeaways
- The Share button is the control center: it lets you share with specific people by email (a managed guest list) or via "anyone with the link" (fast but semi-public).
- Access is who Γ what they can do. The three roles form a ladder: Viewer (look), Commenter (look + comment), Editor (look + comment + edit and reshare).
- Comment, don't overwrite: give reviewers Commenter access so feedback sits beside the deck instead of silently changing it. Reserve Editor for genuine co-builders.
- You can change or remove access, restrict the link, transfer ownership, and (on Workspace) set expiry β but revoking a link can't undo copies already made, so be deliberate before sharing sensitive info.
π What You've Accomplished
Your running deck is no longer a private artifact β it's shared, deliberately, with the right person at the right level. You understand the two ways to share, the three roles and when to use each, how to manage and revoke access, and the honest security realities of a link that can travel. You've inspected your own access list and practiced the "share narrow, widen later" habit. That's a genuinely professional skill.
β Common Questions at This Stage
Does the person I share with need a Google account?
For named sharing and for editing or commenting, yes β they sign in to prove who they are, which is what makes the access manageable. For a plain "anyone with the link" Viewer share, they can often just open it in a browser without signing in. If in doubt, sharing with a Gmail address is always the smoothest path.
If I make someone an Editor, can they share my deck with other people?
Usually yes β Editors can typically invite others and change sharing settings. That's another reason to reserve Editor for people you genuinely trust to co-own the deck's reach. If you want to prevent it, there's often an option (under advanced settings) to stop editors from changing access and adding people; availability depends on your account type.
What's the difference between sharing a link and "publishing to the web"?
Sharing a link still lives inside Slides' permission system β you control the role and can revoke it. Publishing to the web creates a fully public, standalone page anyone can view (and it can be embedded elsewhere), outside the normal share list. It's more open and a different tool for a different job β we cover it in Lesson 5.3 and again in the embedding lesson (6.3).
π Looking Ahead
In the next lesson β Lesson 6.2: Comments & Real-Time Co-Editing β we bring that shared deck to life. You'll learn to add comments on slides and objects, @-mention teammates to assign work, resolve and revisit comment threads, and experience the real-time magic of multiple people building one live deck together β colored cursors and all. It's the thing Slides does best, and now that your deck is shared, you're perfectly set up for it.
β Before the Next Lesson
- Confirm your running deck is shared with at least one person as a Commenter
- Have that person (or a second account of yours) ready to comment next lesson
- Write your Learning Journal entry for this lesson
π Additional Resources
- Share files from Google Drive (Google Support)
- Choose who to share with & how they can use your file (Google Support)
- slides.google.com β open the app
π Encouragement for the Journey
You just crossed the line from making decks to sharing them β the moment a presentation stops being a solo craft and becomes a team sport. And you did it the careful way, giving each person exactly the access they need and no more. That thoughtfulness is what separates confident collaborators from people who dread the "who changed my slide?" moment. Next up: the joy of watching a deck come alive with other people in it. π