Hidden actions within the sites section of AEM - access rights -> how does it work ?

[Ruben_Thys1]

Hi all, 

I'm desperately trying to find out where in the repository the rights are defined to show or hide a button (e.g. publish, unpublish, move) within the sites section of AEM6? 
I already checked the following path : /libs/wcm/core/content/sites/jcr:content/body/content/header/items/selection/items/movepage
But I cannot see any ACL rules defined for this path. Why is this button hidden for a 'contributor' and shown for an 'administrator' (and more important, where is this defined) ? 

This question is related to the development of an own button (based on the following tutorial : https://docs.adobe.com/docs/en/aem/6-0/develop/extending/customizing-page-authoring-touch.html), where I try to show this new button only to a certain group.

Thanks for the help!

Cheers,
Ruben 

[Lokesh_Shivalingaiah]

All these should be controlled using ACLs. For a particular group, dont give any option of for the button so that it is not shown

[Ruben_Thys1]

well that's what I'm trying to find out actually, my first guess was that it is indeed working with ACLs. However it doesn't make any sense... Have a look at the following 2 repository paths : 

- /libs/wcm/core/content/sites/jcr:content/body/content/header/items/selection/items/viewproperties

- /libs/wcm/core/content/sites/jcr:content/body/content/header/items/selection/items/movepage

There is no specific ACL rule defined on both paths. Due to inheritance on both paths administrators have "jcr:all" rights, contributors "jcr:read" rights. Why is it, that a "contributor" can ONLY see "view properties" button and is not able to see the "move page" button, even when the ACL rules are exactly the same? Are these ACL rules defined somewhere else (where?)...

Thanks for the input!

[Ruben_Thys1 · Accepted solution]

I managed to fix this problem, it seems that a custom "rendering condition" is needed to manage this behaviour : https://github.com/Adobe-Marketing-Cloud/aem-admin-extension-customize-sites/blob/master/src/main/co...

Next to the rendering condition you need some properties (e.g class) on your granite/ui/components/foundation/collection/action... Pretty obscure functionality...