Fix Notion ‘Cannot Move Page’ Error Due to Permission Cascade Block

When you try to move a page in Notion, you may see the error message “Cannot move page” and the operation fails. This error often occurs when the page inherits restrictive permissions from a parent database or workspace group, creating a permission cascade that blocks relocation. This article explains why the permission cascade causes the move to fail and provides a step-by-step fix to resolve it. You will also learn about related permission errors and how to avoid them.

Why the Permission Cascade Blocks Moving a Page

Notion uses a permission inheritance model. When you move a page, Notion checks whether the destination location allows the page to be placed there. The permission cascade means that a parent page, database, or workspace group can apply restrictions that flow down to all child pages. If the parent has a setting that prevents pages from being moved, every page under it inherits that restriction.

The most common causes include:

• The page belongs to a database where the “Lock Database” option is enabled. This locks all pages inside the database, preventing them from being moved out.
• The page is inside a workspace group that has content permissions set to “Can view” or “Can edit” but not “Can move.”
• The page is nested under a parent page that is shared with a guest or external collaborator with limited permissions.

When you try to move the page, Notion checks the permission chain from the page up to the workspace root. If any link in the chain blocks the move, the error appears.

Permission Cascade vs. Individual Page Permissions

Individual page permissions override inherited permissions only if they grant more access. They cannot remove a restriction set by the parent. For example, setting a child page to “Full access” does not bypass a parent database lock. The cascade is one-way: restrictions flow down and cannot be overridden by child page settings.

Steps to Fix the Cannot Move Page Error

Follow these steps in order. After each step, try moving the page again. Stop when the move succeeds.

1. Check if the page is inside a locked database
   Open the database that contains the page. Click the three-dot menu at the top right of the database view. Look for the Lock Database option. If it shows a checkmark, the database is locked. Click Lock Database to unlock it. Then try moving the page.
2. Remove the page from the database first
   If the page is a database item, you cannot move it directly out of the database while the database is locked. After unlocking the database, right-click the page row and select Move to. Choose a location outside the database. This removes the page from the database and makes it a standalone page.
3. Check workspace group permissions
   Go to Settings & Members in the left sidebar. Click Groups. Find the group that owns or has access to the page. Click the group name. Under Content Permissions, verify that the permission level is set to Can edit or Can move. If it is set to Can view, change it to Can edit. Save the change.
4. Move the page to a location with matching permissions
   Sometimes the destination location has stricter permissions than the source. Try moving the page to a different location, such as a private page or a page where you have full access. If the move succeeds, the destination was the problem.
5. Duplicate the page as a workaround
   If you cannot resolve the permission cascade, duplicate the page. Right-click the page in the sidebar and select Duplicate. The duplicate is not linked to the original permissions. Move the duplicate to the desired location. Delete the original page after confirming the duplicate is correct.

If Notion Still Shows the Error After the Main Fix

If the error persists, the permission cascade may involve multiple layers. Check these additional scenarios.

Parent page is shared with a guest with limited permissions

A guest who has access to a parent page may block moving child pages. Open the parent page. Click Share at the top right. Remove any guest who has only Can view or Can comment access. Then try moving the child page.

Workspace owner or admin restrictions

Some workspaces have admin policies that restrict page moves for certain groups. Contact your workspace owner or admin. Ask them to check Settings & Members > Workspace Settings > Page Permissions. If the option Restrict page moves is enabled, ask them to disable it for your group.

Page is inside a template button or synced block

Pages created from template buttons or inside synced blocks inherit special permissions. Remove the page from the synced block by right-clicking it and selecting Unsync. Then try moving the page.

Notion Page Move Error Causes Compared

Cause	How to Identify	How to Fix
Locked database	Database three-dot menu shows checkmark on Lock Database	Unlock the database via the three-dot menu
Workspace group content permission set to Can view	Settings & Members > Groups > group > Content Permissions shows Can view	Change to Can edit and save
Parent page shared with guest	Parent page Share menu shows a guest with Can view or Can comment	Remove the guest from the parent page share list
Page inside synced block	Right-click page shows Unsync option	Click Unsync, then move the page
Workspace admin restriction	Settings & Members > Workspace Settings > Restrict page moves is enabled	Ask workspace owner to disable the restriction

You can now identify and resolve the “Cannot move page” error caused by a permission cascade in Notion. Start by checking whether the page is inside a locked database or a workspace group with restrictive content permissions. For a quick workaround, duplicate the page and move the duplicate to bypass the permission block. To prevent future errors, review the permission settings of parent databases and groups before nesting pages under them.