Hi @Anilkumar9!Would you mind sharing the error/exception including stack traces from the error.log file for this issues? This would help with further analysis and support.

Any user can allow another user to impersonate him. This is not tied to special permissions. As mentioned in my initial response, the user will then be added to the list in the rep:impersonators property of the user node. The admin user is a very special case and has broad permissions in AEM that ar...

Hi @aem_noob!The impersonation feature should be used sparsely and is not recommended for day-to-day business tasks like the ones you are mentioning. It seems that you are trying to solve a sub-optimal business process with a technical workaround. I highly recommend to reconsider the solution approa...

This entry:org.apache.sling.api.request.TooManyCallsExceptionof the stack trace indicates that there are too many internal calls during resource resolutions. There are two common root causes for this:Many components (including nested sub-components) on a page. @EstebanBustamante and @Sudheer_Sundala...

That's right. AEM does not store each and every page edit in a way to allow for comparison. It does track page edits (who edited a page at what time) but not in-depth content level comparison is only possible between different versions or between a version and the current state of the page. Versions...

Hi @Mahedi_Sabuj!The direct answer to your question has correctly been provided by @aanchal-sikka. There is no easy, direct way to provide read-only access to the system console (Apache Felix web console) OOTB.However, depending on your setup and use case, there might be other options to satisfy you...

Hi @serhiiko!Sling Content Distribution is certainly one way to get content from one AEM instance to another. @Saravanan_Dharmaraj already outlined good starting points for SCD if you are already clear that this is the optimal approach to solve your business requirements. Depending on your use case,...

Hi @aem_noob!As @Sudheer_Sundalam has correctly stated, impersonation is handled on a per-user level and it is not possible to grant impersonation to groups. Impersonators are stored as "rep:impersonators" property (type: String[]) on the user node. You did observer that the "admin" user is able to ...

What exact functionality are you missing from the timeline feature? What is your requirement here?Please provide additional details that will allow us to support with your query.

This does certainly explain the behavior.Good job to identify the issue! In general, the described behavior is not expected and the position of components should not be altered by roll outs.