Hi Team, I have a requirement in my project where I need to disable 'save and close' button for some users in content page properties.

[Seema1]

Or it will be helpful if anyone can tell me where this save and close' button stored in aem.

[sanketd27011989 · Accepted solution]

Can you please check 

/libs/wcm/core/content/sites/properties

/libs/cq/gui/components/siteadmin/admin/properties/clientlibs/properties/js/properties.js

.I will add if found something more

[Seema1]

Ok, thank you for quick help.

[skumari1]

Hi @sanketd27011989 

Not get the exact location of save and close button but only got the properties.jsp file inside "libs/granite/ui/components/shell/propertiespage/propertiespage.jsp" where it is defined but even after omitting it it not got disappeared from content page.

[Jörg_Hoh]

Do you want to that these users should not be able to update page properties? If that's the case you can achieve this with proper permissions on the page itself (only read permissions).

[Seema1]

Hi @Jörg_Hoh 

We have one reviewer group and for this group we want to hide the save and close' button in page properties. That means that group members can open the page properties, see the details but can not save the changes as "save and close" will be either invisible aur not responsive for them.

[Jörg_Hoh]

This is the default behavior if you don't have write access on that page, but only read permissions.

[skumari1]

Hi @Jörg_Hoh 

The requirement is to create a custom group having "deny access for save and close button from properties tab" which should be placed in group.yml file like below:-

Can we achieve the requirement like this?

[Jörg_Hoh]

The question is if the users must not have write access to page properties but to the components on the page, or if the whole page should be write protected.

Should they be able to move/delete pages?

In any case you should look into https://github.com/Netcentric/accesscontroltool/blob/develop/docs/AdvancedFeatures.md and the Oak documentation (https://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html, search for the "rep:glob" examples).

[Siva_Sogalapalli]

As @Jörg_Hoh replied, you can simply achieve through user admin console in AEM. 

Eg: 

1. Go to the user admin console http://localhost:4502/useradmin 

2. Select the user & just enable read access

Please refer below for more info: 

https://experienceleague.adobe.com/docs/experience-manager-64/administering/security/security.html?l... 

[ShaileshBassi]

Hi @Seema1 As John suggested, you should achieve it via the permissions.

As if there is any change in the specified OOTB clientlibs in the upcoming Service Pack or in the next AEM version, then it will be a bottleneck.
Plus some of the overlay are not allowed in AEMaaCS.

So if the above use case is not met by the permission, in that case create your own clientLibs and get it loaded  via the category "cq.siteadmin.admin.properties" and you can perform hide/show.

Thanks

[Seema1]

Hi @ShaileshBassi 

I have suggested the above method to my team and waiting for their reply.

Will reply back in some time.

Thanks for the all comments.