Hide Manage publication from sites console, hide Request publication and Request unpublication from Page information tab in | Community
Skip to main content
T
tejaswi_aem
Level 2
August 25, 2025
Solved

Hide Manage publication from sites console, hide Request publication and Request unpublication from Page information tab in

  • August 25, 2025
  • 2 replies
  • 1870 views

I'm using AEMasCloud, I have a specific group for authors(xyz-authors) where I have added workflow users to its group, Now, for its members, when they select a page I want to hide Manage publication option from sites console, also, hide Request publication and Request unpublication options from Page information tab. I have tried the below code. 

"set ACL for xyz-author \n deny crx:replicate on /content/xyz \nend",
"set ACL for xyz-author \n deny jcr:read on /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication \nend"

It is not working.  

Best answer by arunpatidar

Hi @tejaswi_aem 

You are doing right, just try with different syntax

set ACL on /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication deny jcr:read for xyz-author end

2 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
August 25, 2025

Hi @tejaswi_aem,

You’ll need to add a clientlib under apps that injects JS in the sites console and page editor context menus, checks if the current user is in xyz-authors, and then hides those actions.

1. Create clientlib - Path:/apps/yourproject/clientlibs/authoring/hide-publicationcq:ClientLibraryFolder with:

categories = ["cq.authoring.page"]
dependencies = ["cq.authoring.siteadmin.admin"]

2. Add JS logiclike  hide-publication.js:

3. Include clientlib

Add this clientlib to author by overlaying /libs/cq/gui/components/authoring/editors/clientlibs/core with:

<yourproject
    jcr:primaryType="nt:unstructured"
    categories="[cq.authoring.page]"
    dependencies="[cq.authoring.siteadmin.admin]"
    embed="[yourproject.clientlibs.authoring.hide-publication]"/>

 

Santosh Sai
    arunpatidar
    Community Advisor
    arunpatidarCommunity AdvisorAccepted solution
    Community Advisor
    August 26, 2025

    Hi @tejaswi_aem 

    You are doing right, just try with different syntax

    set ACL on /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication deny jcr:read for xyz-author end
    Arun Patidar
      Terms & ConditionsAccessibility statement

      Loading footer...