@arunpatidar  - Thanks! It didn't exactly have the answer, but it slowed me down enough to think about the problem more! The solution may not be ideal but does seem to work for our scenarios.   Solution:   Create an editor group, give "modify" access to the desired path, then create two ACL deny rul...

Hello Friends,   What I am trying to accomplish: I am attempting to create an "Editor" access level in AEM Sites 6.5*. This level would have permission to edit text/components/content within a path they are given access but not add new components nor delete components. I've searched the internet, th...

@arunpatidar  - Thank YOU!This is a perfect starting point - all of the guides I had found were from way back in 2017 and none outlined it so thoroughly.   I'll set aside some time and give this a shot!   Regards,   Tom.

Hello @arunpatidar!   Thank you for the answer. That sounds like a reasonable approach. Do you have any recommendations for a good setup guide on implementing context-aware-configurations? It is a feature we have no used yet, and from a quick review online I didn't come across and guides which conne...

Hello All,   This may be an easy solve or an attempt to use the wrong solution, so please correct us if you know of a better way! Also, we are not using any of the advanced Experience Fragment features like building blocks or variations in this case. Our quandary: We have chosen to use an Experience...

@lukasz-m Bingo! That was the piece we were missing. Thank you so much. We were able to connect the dots and replicate the component policies from our page template into the experience fragment. Many Thanks!

All,Perhaps I am missing something very obvious, but I am stumped. I have read through the docs, numerous tutorials, and this forum, no luck.Problem: When a component is added to an Experience Fragment, we can no longer see that components style system (paint brush). The components and their style s...