When you share a page in Notion, you may notice that subpages inside it become accessible to the same people without you granting access individually. This happens because Notion uses a permission inheritance model where a child page automatically adopts the sharing settings of its parent page. Understanding this inheritance rule is essential for controlling who can view or edit specific content inside your workspace. This article explains how parent page permissions flow to children, how to override inheritance for specific subpages, and what limitations exist.
Key Takeaways: Controlling Access in Nested Notion Pages
- Share menu on a parent page: All child pages inherit the same guest or group access by default
- Override inheritance via a child page’s Share menu: Grants unique permissions that replace rather than add to the parent’s settings
- Private pages inside a shared parent: Require manual removal of inherited guests by setting the child to “Private”
How Notion Permission Inheritance Works
Notion organizes content in a tree structure. Every page can contain subpages, databases, and inline blocks. When you share a top-level page with a guest or a group, Notion automatically propagates that access to all pages nested inside it. This propagation is called permission inheritance.
The inheritance rule applies to both guests and members. If you add a guest to a parent page, that guest can see every child page unless you explicitly change the child page’s sharing settings. The same logic applies when you share a page with a group via a workspace link.
Permissions flow downward only. Changing a child page’s sharing does not affect the parent or sibling pages. Also, inheritance does not apply to database items inside a database view. Only pages inherit permissions from their direct parent.
What Gets Inherited
When a parent page is shared, the following settings are passed to each child page:
- Guest access (full access or can comment)
- Group access via workspace link
- Public sharing status (if the parent is published to the web)
The child page does not inherit the ability to be shared again by the guest. Guests cannot share pages with other people unless the parent page explicitly allows it.
What Does Not Get Inherited
Not all permissions flow down. The following remain independent on each page:
- Page-level comments and discussion threads
- Database view filters and sorts
- Lock status (lock page prevents editing but does not affect children)
Locking a parent page does not lock its children. Each page must be locked individually.
Steps to Override Permission Inheritance on a Child Page
If you need a subpage to have different access than its parent, you must break the inheritance manually. Follow these steps to give a child page unique permissions.
- Open the child page
Navigate to the subpage whose permissions you want to change. Make sure you are viewing that page, not the parent. - Click Share in the top-right corner
The Share menu opens showing the current inherited guests and groups. Inherited entries are labeled with a note that they come from the parent page. - Click the three-dot menu next to an inherited guest
A dropdown appears with options: Remove, Change access level, or Make private. - Select Remove to revoke that guest’s access on this child page
The guest is removed from this page only. They still have access to the parent and any other child pages that still inherit. - Alternatively, click Make private
This removes all inherited guests and groups from this page. Only workspace members with full access can see it. The page becomes hidden from any guest who had access through the parent.
After you override inheritance, the child page displays a small lock icon in the sidebar. This icon indicates that the page has custom permissions that differ from its parent.
If Notion Permission Inheritance Does Not Work as Expected
Guest can still see a child page after I removed them
If you removed a guest from a child page but they can still access it, check whether the parent page is shared with that guest again. Inheritance is recalculated each time the parent page’s share settings change. If the parent is re-shared, the child page inherits again and overrides your removal. To prevent this, make the child page private instead of just removing the guest.
Private page still appears in search for guests
When you set a child page to private, it becomes hidden from guests. However, if the guest had previously bookmarked the page URL, the link may still work for a short time due to caching. Notion typically updates the access within a few minutes. To be safe, also remove the page from any shared parent page that the guest can access.
Child page shows “No access” for workspace members
If a workspace member cannot see a child page that is inside a shared parent, check whether the child page has been set to private. A private page is visible only to workspace members who have full access permissions. Members with “Can edit” or “Can comment” access to the parent do not automatically see a private child page. They must be added individually to the child page’s share list.
Database items inside a page do not inherit
If you share a page that contains a database, the database itself inherits the parent’s permissions. However, individual database items (rows or cards) do not inherit separate permissions. Each item inherits the database’s sharing settings. To give a specific database item different access, you must convert it to a full page by clicking “Open as page” and then changing its share settings.
Parent Page vs Child Page Permission Behavior Compared
| Behavior | Parent Page | Child Page |
|---|---|---|
| Default sharing scope | Set manually via Share menu | Inherits from parent automatically |
| Override capability | N/A | Can remove inherited guests or make private |
| Visibility after override | Unchanged | Shows lock icon in sidebar |
| Effect on siblings | None | Does not affect sibling pages |
| Guest re-inheritance | If parent is re-shared, children inherit again | Override is lost unless page is made private |
Understanding this table helps you plan your page hierarchy before sharing. If you need a subpage to remain hidden from guests, make it private as soon as you create it. Do not rely on removing guests later, because a parent page reshare will undo that change.
You can now control exactly who sees each subpage by using the Share menu and the Make private option. For sensitive content, create a dedicated top-level page instead of nesting it inside a shared parent. Use the lock icon indicator to quickly identify pages with custom permissions in your sidebar.