Local AEMascs : "not enough rights to manage publications" issue when publish manage publication | Community
Skip to main content
K
Kamaraj_AEM
Level 2
August 6, 2024

Local AEMascs : "not enough rights to manage publications" issue when publish manage publication

  • August 6, 2024
  • 2 replies
  • 763 views

Hi Team,

In my local AEMascs (2024.7 version jar), when I am trying to publish a page using manage publication option, I am getting "not enough to manage the publications" message.

Enabled Default Agent  and admin user has all permissions. "Page Publish" option is working fine.

 

I have gone through below page,  add admin to workflow users group. But no luck.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-fix-quot-not-enough-rights-to-manage-publications-quot/td-p/389211

 

Please guide me to fix this issue. Thanks in Advance.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 6, 2024

Hi, 

Can you check if this occurs with your "admin" user, besides that, Can you check the logs and post back what you found there?

Esteban Bustamante
    K
    Kamaraj_AEMAuthor
    Level 2
    August 6, 2024

    I am using admin user only. For admin user only , it is showing the above  message.

     

    In the log I can see below error message,

    *ERROR* [[0:0:0:0:0:0:0:1]  POST /etc/workflow/instances HTTP/1.1] com.adobe.granite.workflow.console.servlet.InstancesServlet Unable to start workflow /etc/workflow/models/publish-content-tree-custom/jcr:content/model.  Model not found.
     
    Thank you for point out the right direction. 
     
    When I sync the workflow, it is started working. 
     
    Thank you again!
     
      V
      Venki105
      August 10, 2024

      Hi Kamaraj_A,

       

      If the admin user has the administrator access then workflow users group is not at all required. So if the user doesn't have the admin access then user should have access to the /var/workflow and /etc/workflow.

       

      So after adding the user into workflow users group, check the permissions tab of the user in user admin if the user has the read access or if any other user group is conflicted.

        Terms & ConditionsAccessibility statement

        Loading footer...