Lock components move from a page

Hello @giovannafe 

Out-Of-The-Box :
> AEM does not offer a built-in permission to only allow/deny the reordering (move) of components.
> Move, add, and delete permissions are typically bundled through JCR privileges like jcr:write.
> You can lock critical components in the "Structure" section of an Editable Template to prevent regular authors from moving them.
> Only template editors (admins or trusted users) can unlock/move these.
> Authors can add/move components in the "Initial Content" (unlocked) section, unless the template is locked.

You can attempt advanced ACLs with rep:glob patterns for more selective restrictions, but these control general write/remove rights - not strictly "move".

Blocking just the "move" UI capability for some users would require custom code.

Hello @giovannafe ,

This kind of granular control (restricting the ability to reorder/move components within a page while allowing other editing actions) isn’t available through standard AEM permissions like read, modify, create, or delete.

However, you can achieve this requirement through Custom Page/Component Policy Control:

• Define a policy at the template level (via Editable Templates) to lock the layout container or specific components for certain groups.

• You can make layout containers non-editable or disable drag-and-drop functionality for specific user groups by overlaying /libs/wcm/foundation/components/responsivegrid and customizing the cq:editConfig or cq:dropTargets behavior.