When you create a page inside a Notion teamspace, you expect the page to automatically use the teamspace’s permission settings. Instead, the page shows its own restricted permissions, and invited members cannot access it. This issue occurs because the page was created with explicit permissions that override the teamspace’s inheritance rules. This article explains why inheritance breaks and provides step-by-step fixes to restore correct permission behavior.
Key Takeaways: Restoring Teamspace Permission Inheritance
- Page > Share > Remove explicit members: Deletes manually added users so the page reverts to teamspace-level permissions.
- Teamspace settings > Page Permissions > Inherit: Ensures new pages automatically adopt the teamspace’s default access.
- Move page out and back into teamspace: Resets the page’s permission state when explicit permissions are stuck.
Why Notion Page Permissions Stop Inheriting From a Teamspace
Notion teamspaces are designed so that all pages inside them inherit the teamspace’s permission settings. When you invite a member to a teamspace, they can see every page within it unless a page has explicit permissions that contradict the teamspace. The inheritance breaks when someone manually adds a guest or member to a specific page using the Share button. That action creates an explicit permission rule on the page. Notion then treats the page as having its own permission set, and the teamspace-level access no longer applies to that page. The same problem occurs when a page is duplicated from a different location and retains its original permissions.
Explicit Permissions Override Teamspace Inheritance
Every Notion page has a permission field that can be set to Inherit or Custom. By default, a page created inside a teamspace is set to Inherit. When you add a specific person to the page via Share, Notion automatically switches the page to Custom mode. Once in Custom mode, only the people explicitly listed on the page can access it, and teamspace members who are not on that list lose access. This is the most common cause of the inheritance problem.
Page Duplication Preserves Old Permission Rules
If you duplicate a page from a private workspace or a different teamspace into your current teamspace, the duplicate keeps its original permission settings. The duplicate will not inherit the new teamspace’s permissions until you manually reset it. This often catches users off guard because the page appears inside the teamspace but behaves as a private page.
Steps to Fix Page Permissions That Do Not Inherit From Teamspace
Use the following methods to restore inheritance. Start with Method 1 because it works for most cases. If the page still does not inherit, proceed to Method 2.
Method 1: Remove Explicit Members and Reset to Inherit
- Open the page that is not inheriting permissions
Navigate to the page inside the teamspace. Click the page title or open it from the sidebar. - Click Share in the top-right corner
The Share menu shows every person or group that has explicit access to this page. If the page is in Custom mode, you will see a list of members and guests. - Remove all explicitly added members and guests
Click the three-dot menu next to each person’s name and select Remove. Do not remove the teamspace group itself if it appears. Remove only individual names that were added manually. - Verify the permission mode changes to Inherit
After removing all explicit members, the Share menu should show “Inherit from teamspace” instead of “Custom.” If it still says Custom, click the dropdown next to the page name and select Inherit. - Confirm access by opening the page as a teamspace member
Ask a teamspace member who previously could not see the page to refresh Notion and open the page. They should now have access.
Method 2: Move the Page Out and Back Into the Teamspace
- Move the page to your private workspace
Drag the page from the teamspace section in the sidebar to the Private section at the top of the sidebar. Notion will confirm the move. The page now exists outside the teamspace. - Remove any explicit permissions on the page
Open the page in your private workspace. Click Share and remove any manually added members, just as in Method 1 steps 2 and 3. - Move the page back into the teamspace
Drag the page from the Private section back into the desired teamspace. Notion will prompt you to confirm the move. Click Move. - Check that the page now says Inherit from teamspace
Open the Share menu again. The permission mode should be Inherit. If it still shows Custom, repeat Method 1 step 4 to force the change.
If Notion Still Has Permission Inheritance Issues After the Main Fix
Teamspace Members Cannot See Newly Fixed Page
If you removed explicit members and set the page to Inherit but teamspace members still cannot see it, the teamspace itself may have restricted page creation permissions. Go to the teamspace settings by clicking the teamspace name in the sidebar and selecting Settings. Under Page Permissions, make sure the option “Allow members to create and edit pages” is enabled. If it is disabled, only teamspace owners and admins can create pages that inherit permissions. Enable this option to allow all members to create inheritable pages.
Page Still Shows Custom Mode After Removing All Members
Sometimes Notion does not automatically switch the permission mode back to Inherit after you remove the last explicit member. In the Share menu, look for a dropdown labeled “Page access” or “Permissions.” Click it and select Inherit from teamspace. If the dropdown is missing, refresh the page and try again. This manual toggle forces the inheritance to apply.
Duplicated Pages Keep Old Permissions
When you duplicate a page from another workspace, the duplicate retains the original workspace’s permissions. After moving the duplicate into your teamspace, follow Method 1 to remove any explicit members. Then check the Share menu to confirm it shows Inherit. If the duplicate is a database, also check each database view’s permissions because views can have their own sharing settings. Click the view name and select View permissions to reset them.
| Item | Page in Teamspace (Inherit) | Page in Private Workspace |
|---|---|---|
| Permission mode | Inherit from teamspace | Custom (private) |
| Access for teamspace members | Automatic | None unless explicitly added |
| Effect of adding a guest | Switches to Custom, breaks inheritance | Stays Custom |
| Fix for broken inheritance | Remove explicit members, set to Inherit | Move to teamspace, then remove explicit members |
Now you can restore permission inheritance for any page inside a Notion teamspace. Start by removing explicit members from the Share menu. If that does not work, move the page out of the teamspace and back in. After fixing the page, check the teamspace’s Page Permissions setting to prevent the issue from recurring. An advanced tip: use the Share menu’s Copy link feature to send a direct link to a specific page even when inheritance is broken, but remember that the link alone does not grant access unless the recipient is listed in the page’s permissions.