How are nested page permissions handled during bulk node movements in Sulu?

Permission Inheritance in Page Tree Reorganization

Sulu CMS manages content through a hierarchical page-tree structure, where permissions are often inherited or defined at specific node levels. When moving a page node—along with its entire subtree—to a different parent in the administration interface, the system must reconcile the existing permissions of the moved nodes with the permissions of the new parent node.

There is uncertainty regarding whether the system preserves the explicit permissions assigned to the moved subtree or if it forces a recalculation based on the new parent's permission set to prevent security leaks.

• Does the movement of a page node trigger a recursive update of all child permissions?
• Which mechanism ensures that inherited permissions are correctly mapped without creating orphaned access rules?