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

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

  • October 16, 2015
  • 4 replies
  • 3773 views

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.
    Best answer by brucelef

    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

    4 replies

    B
    Adobe Employee
    brucelefAdobe Employee
    Adobe Employee
    October 16, 2015

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

    A
    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   ??

    hdwu
    hdwu
    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/*?

    B
    Adobe Employee
    brucelefAdobe EmployeeAccepted solution
    Adobe 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

      Terms & ConditionsAccessibility statement

      Loading footer...