🔐 Lesson 6.1: Sharing, Permissions & Guests

Everything in Notion is private to you until you decide otherwise — and then you get a surprising amount of control over who can do what. In this lesson you'll learn the four access levels, the crucial difference between a guest and a member, how to publish a page to the open web, and — honestly — exactly where the free plan stops and a bill begins.

📚 What You'll Learn

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

Invite someone to a specific page and choose the right access level (Full access, Can edit, Can comment, Can view)
Explain the difference between a guest and a member, and why it affects your bill
Publish a page to the web as a read-only link and control search-engine indexing
Predict how permissions inherit down your page tree — and avoid oversharing
Judge which sharing features are free and which need a paid plan

⏱️ Estimated Time: 50 minutes

🎯 Project: Share one page with "Can comment," publish another as a public link, then review exactly who has access to each.

In This Lesson

🔒 Private by Default

Here is the most reassuring fact in this whole module: nothing you make in Notion is visible to anyone else until you deliberately share it. Your pages sit in your Private section, seen only by you. Sharing is always an action you take, never a default you have to switch off.

Think of your workspace like your home. Every page is a room. By default all the doors are locked and you hold the only key. Sharing is deciding to hand someone a key — and Notion lets you choose whether that key lets them rearrange the furniture, leave sticky notes, or just look around. You can also prop the front door open to the whole street (publishing to the web). Every one of those is a separate, reversible decision.

You share at the level of a page. Click Share in the top-right of any page and a dialog opens with two tabs — one for inviting specific people, and one for creating a public web link. We'll take them one at a time.

🧠 Mindset

Permissions can feel intimidating — the fear of accidentally showing the wrong person the wrong thing. Breathe. You cannot leak a page by learning about sharing; reading this lesson changes nothing in your workspace. And every share is undone with one click. We're going to make the invisible rules visible so you feel in control, not anxious. That's the whole goal.

🎚️ The Four Access Levels

When you invite a person (or an email address) to a page, you pick one of four access levels. They form a simple ladder from "can do anything" down to "can only look."

Access level	Can they read?	Comment?	Edit content?	Share & manage access?
Full access	✅	✅	✅	✅ — can invite others & change permissions
Can edit	✅	✅	✅	❌
Can comment	✅	✅	❌	❌
Can view	✅	❌	❌	❌

Here's what the Share dialog looks like when you're setting someone's level:

🔎 Add people, emails, groups…

👤 Sam Rivera Can comment ▾

👤 you@example.com Full access ▾

🌐 Share to web Off ▾

🔗 Copy link

Clicking a person's level pill opens the dropdown with all four options — plus Remove to revoke access entirely.

✅ Pro Tip — pick the lowest level that works

A good instinct: grant the least access that still lets someone do their job. Sharing a plan for feedback? Can comment lets them react without accidentally rewriting your text. Only give Full access to people you truly want re-sharing the page and managing who else gets in.

👥 Guests vs. Members (and Your Bill)

This is the single most misunderstood part of Notion sharing, and it's where "free" quietly becomes "paid." The people you share with fall into two categories.

Guests

A guest is someone you invite to specific pages. They can see and work on only the pages you shared with them — nothing else in your workspace. A friend you share one trip-planning page with, or a client you share one project page with, is a guest. On the Free plan you can have up to 10 guests across your workspace.

Members

A member belongs to the whole workspace and can be given broad access across teamspaces (that's the next lesson). Members are how teams work together at scale — and each member typically costs a per-seat fee on a paid plan. Adding members is a Paid concept once you go past a personal workspace.

graph TD A["🔐 Someone you share with"] --> B{"Whole workspace
or specific pages?"} B -->|"Specific pages only"| C["👤 Guest
Free plan: up to 10"] B -->|"Broad workspace access"| D["👥 Member
usually a paid per-seat"] C --> E["Sees only pages
shared with them"] D --> F["Can be added to
teamspaces & more"]

⚠️ Where the money actually is

For a solo user, sharing the occasional page with friends or clients as guests is free — up to that 10-guest ceiling. You hit a paywall when you need more than 10 guests, or when you want real members with workspace-wide access, which is per-seat on Plus, Business, or Enterprise. Guest and seat limits change over time, so confirm the current numbers at notion.com/pricing before you plan around them.

💡 A personal-first reassurance

If you're using Notion just for yourself, none of this costs anything. You'll share a page here and there, stay well under 10 guests, and never see a bill. This section matters most the day a small team or a growing client list appears — and now you'll recognize the paywall for what it is instead of being surprised by it.

🌐 Publishing to the Web

Inviting people is one way to share; the other is publishing. In the Share dialog, the Share to web toggle turns your page into a public, read-only web page with its own link. Anyone with that link can open it in a browser — no Notion account required. This is how people share portfolios, resumes, public docs, event pages, and simple sites.

When you flip Share to web on, a few options appear:

Allow editing — off by default; keep it off unless you truly want the public editing your page.
Allow comments — let visitors comment on the public page.
Allow duplicate as template — visitors can copy your page into their own workspace. This is exactly how template creators distribute their work.
Search engine indexing — whether Google and other engines can find the page. Paid plans let you control (and turn off) indexing; the free behavior is more limited, so treat any public page as potentially discoverable.

⚠️ "Public" means public

A web link isn't secret just because it's a long, random URL. If you publish a page, assume it can be found, shared onward, and cached. Never publish anything with passwords, private addresses, or personal data you wouldn't put on a billboard. When you're done, toggle Share to web back off to unpublish instantly.

🌟 Going Further (optional) — real websites with Notion Sites

A published page is great for a quick share, but if you want a genuine website — custom domain, multiple pages, navigation, nicer styling — that's Notion Sites, and it's the subject of Lesson 7.2. Full site features and custom domains generally sit on paid plans. For now, know that "publish this page" and "build a site" are two different tools; we'll graduate from one to the other soon.

🌳 Inheritance & Link Settings

Remember that pages nest inside pages. Permissions follow that tree: when you share a page, everything inside it — every sub-page — inherits the same access by default. Share a "Client Project" page with someone as Can edit, and they can edit its sub-pages too, unless you change a sub-page's permissions specifically.

graph TD A["📁 Client Project
shared: Can edit"] --> B["📄 Brief
inherits: Can edit"] A --> C["📄 Timeline
inherits: Can edit"] A --> D["📄 Private Notes
overridden: no access"] B --> E["📄 Attachments
inherits: Can edit"]

This is powerful and a little dangerous. The power: share one hub page and a whole project comes along. The danger: a private sub-page tucked under a shared parent is also shared unless you notice. Two habits keep you safe:

Share from the right level. Put things you'll share together under a page you're happy to share as a unit. Keep private material somewhere that isn't inside a shared parent.
Override when needed. Open a sub-page's own Share dialog and you can remove or tighten access just for that page, breaking the inheritance for it.

🔗 Link sharing settings

The Copy link button gives you a URL to the page. What that link does depends on the page's sharing state:

If the page is private, the link only works for people you've already invited (they still have to be signed in with the right access).
If Share to web is on, the link opens for anyone.

So a link is never a shortcut around permissions — it respects whatever access you've set. Sending someone a link to a private page they weren't invited to simply shows them a "no access" screen, which is exactly what you want.

✅ Privacy checklist before you share

Does this page have sub-pages the person shouldn't see? Move or override them.
Is Can view / Can comment enough, or do they really need to edit?
If publishing to the web — is there anything private on the page or its sub-pages?
Do you need indexing on or off? (Assume public pages are findable.)

🎯 Project: Share, Publish, Review

Time to make sharing real. You'll practice both kinds of sharing on pages you already have, then audit who can see what — the exact routine to run whenever you share something important.

🏋️ Share a page, publish a page, review access

Objective: Experience per-person sharing and web publishing first-hand, and build the habit of reviewing access.

Instructions (about 15 minutes):

(4 min) Pick a page you wouldn't mind a friend seeing. Open Share, add a friend's email (or your own second address), and set them to Can comment. Send it. If you don't have anyone to share with, just set the level and then remove them — the point is the workflow.
(4 min) On a different, harmless page (a favorite recipe, a reading list), toggle Share to web on. Copy the public link and open it in a private/incognito browser window to see what a stranger sees.
(3 min) On that public page, explore the options: try toggling Allow duplicate as template on, and look at the search-indexing setting.
(2 min) Open each page's Share dialog again and read the list of who has access. Confirm nothing is shared that you didn't intend.
(2 min) Clean up: turn Share to web back off on the public page, and remove the test person if you added one.

💡 Hint — can't find the Share button?

It's in the top-right corner of every open page, next to the ⋯ menu and the comment and update icons. On mobile, tap the ⋯ menu and choose Share. If a page is a database entry, open the entry as a full page first.

✅ Project Completion Checklist

You shared one page with a person at Can comment
You published a different page to the web and opened the public link
You explored the web options (duplicate-as-template, indexing)
You reviewed the "who has access" list on both pages
You unpublished the public page and cleaned up the test share

🎯 Quick Quiz

Question 1: You want a friend to leave feedback on your plan but not change the text. Which access level fits best?

Question 2: On the Free plan, which statement about sharing is accurate?

Best Practices for Sharing Safely

✅ Do's

Grant the lowest useful level. Start at Can view or Can comment; upgrade only when someone actually needs to edit.
Structure for sharing. Keep material you'll share together under one parent, and private material outside it.
Review access periodically. Open the Share dialog on important pages now and then and prune people who no longer need in.

❌ Don'ts

Don't assume a link is secret. A published web page can be found and forwarded.
Don't forget sub-pages inherit. Sharing a hub shares everything nested inside it by default.
Don't hand out Full access casually. That level can re-share and manage others' access.

📓 Learning Journal

Keep a learning journal — the best place is inside your own Notion. 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
Your progress and feelings about learning this

✍️ This lesson's prompt: What's one page in your workspace you'd eventually want to share or publish — and what access level would you give people? Note anything private nested under it that you'd need to protect first.

📝 Lesson Summary

🎓 Key Takeaways

Notion pages are private by default; sharing is always a deliberate action you can undo.
Four access levels: Full access, Can edit, Can comment, Can view — pick the lowest that works.
Guests see only pages shared with them (Free plan ≈ 10); members have workspace-wide access and usually cost a per-seat paid fee.
Share to web makes a public read-only page; assume public pages are findable, and use Notion Sites for real websites.
Permissions inherit down the page tree — mind your sub-pages, and override where needed.

🎉 What You've Accomplished

You've moved from "I hope I didn't share the wrong thing" to genuine command of Notion's permission model. You can invite people at exactly the right level, publish to the web on purpose, and audit access like a pro — plus you can now spot the guest and seat paywalls before they surprise you. That confidence is what makes collaboration feel safe.

❓ Common Questions at This Stage

If I share a page, can the person see the rest of my workspace?

No. A guest sees only the specific page you shared (and its sub-pages, via inheritance). The rest of your Private section stays invisible to them. Members are different — they can be given broad access — which is exactly why members generally require a paid plan.

Someone edited my page when I only wanted feedback. What happened?

They were almost certainly set to Can edit (or higher) rather than Can comment. Open the Share dialog, click their level pill, and change it to Can comment. In future, default to Can comment for anything you're just seeking feedback on.

Can I stop Google from finding a page I published?

Search-engine indexing control (turning it off) is generally a paid feature. On the Free plan, treat any published page as potentially discoverable. If a page must stay private, don't publish it at all — share it with specific people instead.

🔭 Looking Ahead

Sharing single pages is perfect for one-off collaboration. But when a whole group needs a shared home — with roles, a wiki, and team-wide spaces — you want Teamspaces & Wikis, which is exactly where we head next. (Solo learners: the next lesson is optional for you, and we'll say so up front.)

✅ Before the Next Lesson

Make sure any test page you published is unpublished again
Note whether you're using Notion solo or with others — it shapes how much of Module 6 applies to you
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

Sharing is where a private workspace becomes a way to work with people — and you just learned to do it deliberately and safely. Whether you collaborate with a team of ten or simply send a friend one tidy page, you're in control of every door. 🔐