Hello,
I am trying to set up permissions schema for our project. One of the requirements is to create a super aurhors group that can do all content changes on selected content branch.
I have one problem while setting this up - I would like super authors to see Quick Publish as well as Manage Publication buttons for pages.
Authors have replicate rights for the content so the Quick Publish is visible but the Manage Publication is still hidden.
Do you know what path I need grant access to to show Manage Publication button ?
I tried etc/workflows but it does not work.
AEM: 6.5.9
Thanks for your help:)
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
As always the answer was right there, it should be /etc/workflow instead /etc/workflows
This ACL entry fixed the issue:
- path: /etc/workflow permission: allow actions: read
I guess something has changed since 2017 in terms of the path (see related question here)
Hi @bartek_887
You can add "workflow-users" group and it will enable the "Manage Publication" button for users.
Thanks!
Unfortunately this would add to much access to the user
login in aem instance with admin cred. or privileges then open the useradmin.
In useradmin's search wizard search for "/libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication"
and see the permission. most probably your read permission will be missing on the path for that user or group.
see the below image
Hope this will help.
Umesh Thakur
My user have full access to libs and apps so it also have access the the /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication.
Unfortunately I do not see this path in the /useradmin panel, all I see is:
First search for the user or goup then double click on the user or group then click on the permissions tab now you will have search box on the right corner there search the path and see.
As always the answer was right there, it should be /etc/workflow instead /etc/workflows
This ACL entry fixed the issue:
- path: /etc/workflow permission: allow actions: read
I guess something has changed since 2017 in terms of the path (see related question here)
Views
Likes
Replies
Views
Likes
Replies