Skip to content
Tutorials Center
My learning

Topics

Lesson 24 of 36 ยท Collaboration and Sharing

Sharing Pages and Permissions

Learn how to share Notion pages with people and the public, the five access levels, how permissions inherit down the page tree, and how to avoid leaks.

Sharing is where mistakes get expensive: a private plan sent to the wrong person, or a client who can edit your internal notes. Notion's sharing model is simple once you see its two main ideas: each page has an access level per person, and access flows downward from parent pages to their children.

The Notion app is not available on this site. The steps below describe the real menus, and the stand-ins are runnable JavaScript models that explain the logic. Menu names can shift between versions.

Sharing a page

Open a page and click Share (top right). From the dialog you can:

  • Invite people, groups or guests by name or email and choose their access level.
  • Share to web to publish the page on a public link.
  • Copy a link, whose behavior depends on who can open it.

The access levels

Level What the person can do
Full access Everything, including changing sharing
Can edit Edit the page and content, in databases also add rows
Can edit content Edit content but not structure such as database properties (databases only)
Can comment Read and add comments
Can view Read only

Anyone you invite gets exactly one of these on that page. Choose the lowest level that lets them do their job: reviewers need comment, not edit.

Inheritance

Pages live in a tree. If you give someone access to a parent, they get the same access to every child page unless the child is restricted. This explains two behaviors:

  • Sharing a teamspace or top-level page shares everything beneath it.
  • A child page can have extra people added, or can be restricted so that it breaks from the parent's list (the Share dialog shows when a page inherits).

Before you add a guest to a page, look at what is below it. A "Client" page that contains your internal budget database shares that database too, unless you move or restrict it.

Stand-in: resolve effective access

The code is not Notion. It models a page tree where each page can inherit or override permissions, and finds one person's effective access.

JS Stand-in: inherited permissions

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The restricted page does not inherit, so the team loses access while HR keeps it.

Sharing to the web

Share to web publishes a read-only page that anyone with the link can see. Options include:

  • Allow editing or allow comments for visitors (use carefully).
  • Allow duplicate as template, so visitors can copy it to their own workspace.
  • Search engine indexing, which is off by default. Turn it on only for pages meant to be found.

Published pages show the page and its sub-pages, so check what lives beneath. Unpublish from the same dialog; the link stops working.

Pasting a page link into a chat only helps if the reader has access. If they do not, they get an access request screen, and the page owner is notified. When you share, Notion can notify the invited person by email or in their inbox.

Good habits

  1. Review access quarterly. Open Share on top-level pages and remove people who left a project.
  2. Prefer groups to long lists of names.
  3. Use comment access for reviewers so they cannot change the content.
  4. Keep private and public pages apart. Put public content under one parent.
  5. Duplicate before sharing a template, so internal notes are not exposed.

Stand-in: audit a share list

A tiny script that flags risky shares: anyone with edit rights who is a guest.

JS Stand-in: flag risky shares

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. A reviewer should leave feedback but not change the text. Which level fits?

    Can comment lets someone read and add comments without editing the page.
  2. 2. What happens to access on child pages by default?

    Access flows down the page tree unless a child is restricted.
  3. 3. Which setting should you leave off unless you want a public page to appear in search results?

    Search engine indexing is off by default and only needed for pages meant to be found publicly.

Summary

  • Each person gets one access level per page: full access, can edit, can edit content, can comment or can view.
  • Permissions inherit down the page tree; restricted pages break the chain.
  • Share to web publishes a read-only public link with optional extras.
  • Check what is under a page before you share it, and review shares regularly.

Next: Comments, Mentions and Reminders