Permission based parsys for Junior/Senior content authors | Community
Skip to main content
Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity Advisor
Community Advisor
May 3, 2016
Solved

Permission based parsys for Junior/Senior content authors

  • May 3, 2016
  • 4 replies
  • 1055 views

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

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Lokesh_Shivalingaiah

    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.

    4 replies

    Lokesh_Shivalingaiah
    Lokesh_ShivalingaiahAccepted solution
    Level 10
    May 3, 2016

    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.

    smacdonald2008
    smacdonald2008
    Level 10
    May 3, 2016

    I agree with Lokesh, this is not standard funtionality.

    Peter_Puzanovs
    Community Advisor
    Peter_PuzanovsCommunity AdvisorAuthor
    Community Advisor
    May 3, 2016

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

    Regards,

    Peter

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    May 3, 2016

    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

      Terms & ConditionsAccessibility statement

      Loading footer...