Thanks, but how do you limit that to only the specific user group?

I'd like to hide the 'Tools' navigation for only a single user group.I created an overlay for /libs/cq/core/content/nav/tools under /apps/cq/core/content/nav/tools; then added a deny ACL for the navigation item like so: /apps/cq/core/content/nav/tools/rep:policy/deny. The reason for doing this is so...

We have a blog component requirement where there needs to be two sets of user groups, one that can publish blog posts and another that can author but not publish (save only). Is there a way to accomplish this via user group permissions (rep:policy)? Pls see attached image.

Does anyone have any information where/how to implement a content security policy within the AEM platform?Content Security Policy (CSP) - HTTP | MDN

Hi gauravs23​, re: #3, we have used something similar to content fragments in our project. (similar because we are still on a version prior to 6.2). We have two separate sites that both contain biographies. The biographies (text) are the same but the page layouts are different. Because we have the b...

Good point, could be one of those quirky AEM things. I can always resort to using tree activation and check "ignore modified".Thanks all for the input!

Thanks Ratna, Yes, I checked replication queue, and upon replication, it was there, then after a little while, it processed as expected.The deactivated pages appear red in both Author and Publish instances (under siteadmin), but still show up from Publish URL, as if you were viewing from the public.

Hi,Every month or so, I package the pages I have in my Production enviroment and move them down to my lower environments to keep them in sync.I typically create and build the package from Prod-Author (/content/my-project).Then upload and install in my Dev-Author instance; replicate from Dev-Author t...

Ah thanks - makes sense! :)

I appreciate the responses everyone! @edubey, how did you know that "principal.name" was available?