how to apply permission on design mode of sidekick in CQ5? | Community
Skip to main content
Anonymous
October 16, 2015
Solved

how to apply permission on design mode of sidekick in CQ5?

users then wouldn’t be able to see the  “design” button

 [img]xyz.jpg[/img]

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    brucelefAccepted solution
    Employee
    October 16, 2015

    To enable the design button, grant the user (or group) "Modify" permission to /etc/designs/<designName>. This can be done as an administrator via the useradmin [0].

    [0] http://localhost:4502/useradmin

    View reply

    4 replies

    brucelefAccepted solution
    Employee
    October 16, 2015

    To enable the design button, grant the user (or group) "Modify" permission to /etc/designs/<designName>. This can be done as an administrator via the useradmin [0].

    [0] http://localhost:4502/useradmin

    Translate
      hdwu
      hdwu
      New Participant
      October 16, 2015

      Can you provide more detail around specifically which node under etc/designs needs to have 'Modify' applied?

      I think I want a particular group of users to have access to Design mode via the Sidekick so they can add and hide components from a particular template. But I don't understand what else they will have access to if they get 'Modify' for ALL of etc/designs/. I don't see an obvious <design name> under etc/designs that seems appropriate?

      What else will they have access to if they get 'Modify' for etc/designs/*?

      Translate
      Anonymous
      October 16, 2015

      Thank you for your reply :)

      I also want to hide "design" [img]2.jpg[/img]  button from the sidekick. How can i restrict the visibility of Design button for the particular user/group   ??

      Translate
      brucelef
      Employee
      October 16, 2015

      To hide the design button simply "deny" (uncheck) the modify permission for the particular user or group.

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...