Hide Delete button for pages under specific path using repoinit script

Hi @newbie34,

Instead of trying to deny access to the global button definition, can you deny the permission to delete the page nodes themselves under /content/A. AEM uses JCR permissions to determine what buttons to show - if the user cannot delete the page node, the "Delete" button won't show for that page.

RepoInit Example: Deny jcr:remove Node under /content/A

# Create a service user or use existing group (eg. `content-editors`)
create service user content-editor-restricted

# Deny delete (jcr:removeNode) under /content/A
deny jcr:removeNode, jcr:removeChildNodes on /content/A restriction(rep:glob, "*")

# Allow delete under /content/B (optional if inherited from parent)
allow jcr:removeNode, jcr:removeChildNodes on /content/B restriction(rep:glob, "*")

Optionally you attach this to a group - If you're assigning this to a group, use:

create group content-editors
add user content-editor-restricted to group content-editors

# Now assign permissions to group
deny jcr:removeNode, jcr:removeChildNodes on /content/A restriction(rep:glob, "*") for group content-editors

Hi @newbie34 ,

To hide the "Delete Page" button only for pages under /content/A without affecting other pages or component editing, use the following RepoInit rule: deny jcr:read on /libs/wcm/core/content/sites/jcr:content/actions/selection/deletepage restriction(rep:glob, "/content/A/*"). This tells AEM to hide the delete button only when a page under /content/A is selected in the Sites console. It won’t impact /content/B or the ability to edit/delete components. If someone asks why it's still showing or not working, make sure the rule is applied to the correct user group, the glob path is accurate, and there are no conflicting allow permissions elsewhere.

Thanks!