Fix Notion Page Permission Override Not Applying to New Sub-Pages

You have set a custom permission override on a parent Notion page, but newly created sub-pages inside it ignore that override and inherit the workspace default sharing settings instead. This happens because Notion treats permission overrides as locked properties that do not cascade automatically to child pages unless you explicitly enable inheritance. This article explains why the override stops at the parent page and provides the exact steps to force the override onto every new sub-page.

Why a Permission Override Does Not Apply to New Sub-Pages

Notion’s permission system works on a per-page basis. When you change the sharing settings of a parent page — for example, switching from “Can edit” to “Can comment” for a specific guest — that change applies only to that exact page. Sub-pages you create later check the workspace default sharing setting first. If the workspace default is “Can edit” and the parent override is “Can comment,” the new sub-page will show “Can edit” because it has not been told to inherit the parent’s custom rule.

The root cause is a design choice: Notion treats permission overrides as explicit, not inherited. This prevents accidental propagation of restrictive permissions across hundreds of pages. However, it also means you must manually enable inheritance on the parent page if you want new sub-pages to automatically respect the override. Without that toggle, every sub-page you add will fall back to the workspace default.

How Notion Decides Which Permission Wins

Notion evaluates permissions in this order:

1. Explicit permission on the page itself (the override).
2. Inherited permission from a parent page (only if sub-page inheritance is on).
3. Workspace default sharing setting.

When you create a new sub-page, step 2 is skipped unless you have turned on the inheritance toggle on the parent. The new page then goes straight to step 3 and uses the workspace default. That is why your override appears to be ignored.

Steps to Force Permission Override Onto New Sub-Pages

Follow these steps in order. Performing them out of sequence may cause the override to reset.

1. Open the parent page that has the override
   Navigate to the page where you already set the custom permission. Click anywhere on the page to make sure it is active.
2. Open the page menu and select Permissions
   Click the three-dot menu icon in the upper-right corner of the page. From the dropdown, choose Permissions. The sharing panel opens on the right side of the window.
3. Enable sub-page inheritance
   In the Permissions panel, scroll down to the section labeled Allow sub-page inheritance. Toggle the switch to the on position. A confirmation message appears: “This will apply the current page’s permissions to all sub-pages.” Click Apply.
4. Verify the override on an existing sub-page
   Click on any existing sub-page inside the parent. Open its Permissions panel. You should see a note that says “Inherited from parent” next to the override rule. If you do not see this, repeat step 3 and ensure you clicked Apply.
5. Create a new sub-page to confirm future inheritance
   Add a new page inside the parent by clicking the + icon next to the parent’s name in the sidebar. Open the new page’s Permissions panel. The override from the parent should now appear automatically without any manual change.
6. Lock the parent page to protect the override
   Return to the parent page menu. Choose Lock page from the dropdown. A locked page prevents anyone from accidentally changing its permissions, which would break the inheritance chain for sub-pages.

If You Need to Apply the Override to Many Existing Sub-Pages

The inheritance toggle affects only pages created after it is turned on — it does not retroactively change existing sub-pages. To update dozens of existing sub-pages at once:

1. Open the parent page and enable sub-page inheritance as described above.
2. Select all existing sub-pages in the sidebar by holding Ctrl and clicking each one.
3. Right-click the selection and choose Move to. Move them into a temporary folder, then move them back to the original parent. This forces Notion to re-evaluate their permissions against the parent’s override.

If the Override Still Does Not Apply to New Sub-Pages

Even after enabling inheritance, some users report that new sub-pages still show the workspace default. Below are the most common reasons and their fixes.

Workspace Default Sharing Is Set to a More Restrictive Rule

If the workspace default is “No access” and your override is “Can view,” the default may override the inheritance because Notion blocks access before evaluating the override. Go to Settings & Members > Settings > Workspace > Sharing. Set the default to “Can edit” or “Can view” so it does not conflict with your override.

Sub-Page Inheritance Was Disabled After Creating the Parent Override

The toggle for sub-page inheritance resets if you change the parent page’s permissions again. After any permission change on the parent, re-check the Allow sub-page inheritance toggle. It may have turned off silently.

Guest or Group Permission Override Is Not Supported for Sub-Pages

Notion does not allow sub-page inheritance for permissions granted to individual guests or groups. Only the “Everyone” permission setting can be inherited. If your override is for a specific guest, you must manually add that guest to each new sub-page. There is no workaround for this limitation.

Permission Override vs Workspace Default vs Page Lock: Key Differences

Item	Permission Override	Workspace Default	Page Lock
Scope	Single page only	Every new page in workspace	Prevents edits to page content and permissions
Applies to sub-pages	Only if inheritance toggle is on	Always, unless overridden	Does not affect permissions
Can be changed by any member	Only by page owner or workspace admin	Only by workspace owner	Only by page owner
Resets on permission change	Yes, inheritance toggle turns off	No	No

You can now force a permission override onto every new sub-page by enabling the Allow sub-page inheritance toggle on the parent page. After turning it on, lock the parent to preserve the setting. If you work with guest-specific overrides, remember that sub-page inheritance does not apply to them — you must add guests manually. For advanced teams, consider creating a template with the override pre-applied and inheritance enabled so every new page starts with the correct permissions.