Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Permission based parsys for Junior/Senior content authors

Avatar

Community Advisor

Hello,

Have an interesting requirement:

As a Senior content author I should be able to ADD/REMOVE/RE-Order and modify content of components in parsys.

As a Junior content author I should be able only to modify content in components, NOT ADD/REMOVE/Re-Order components in parsys.

This should work both in Classic and Touch UI.

Believe this would be a customization of OOTB parsys component.

Has anyone done this in the past ?

Could you kindly suggest how to best implement this customization both for Classic and Touch UI?

 

Regards,

Peter

1 Accepted Solution

Avatar

Correct answer by
Level 10

I would say thats a crazy requirement !! why would they want to do. I dont think its worth an effort. Rather give the clear instructions and educate the role for the Junior Content authors and kind of govern the changes done by the Junior content authors using workflow.

View solution in original post

4 Replies

Avatar

Correct answer by
Level 10

I would say thats a crazy requirement !! why would they want to do. I dont think its worth an effort. Rather give the clear instructions and educate the role for the Junior Content authors and kind of govern the changes done by the Junior content authors using workflow.

Avatar

Level 10

I agree with Lokesh, this is not standard funtionality.

Avatar

Community Advisor

Thank you for your answers Lokesh/Scott will kindly ask to re-validate requirements.

Regards,

Peter

Avatar

Employee Advisor

Hi,

while this sounds a bit crazy (as bsloki already stated) I think that this is a totally valid requirement. Junior people shouldn't get overwhelmed by the options the systems offers (especially if they don't know how to reverse any change they accidently did). Training can help, especially you mention the undo operation then.

On the other hand this is quite hard to implement, as the ootb parsys don't offer any chance to limit these operations. Implementing it in both classic and touch UI requires changes on both sides in the javascript, and this won't be easy.

Jörg