Permissions based on usergroups using components

[kristinas125273]

Hi @all,

we have a few questions regarding permissions based on usergroups using components. Our research could not really answer the questions a way that we are sure with the possibilities given by AEM 6.2.

1. Which possibilities do we have to restrict usergroups in working with components?
2. Can we hide a component in sidekick based on usergroup?
3. Can we hide a component in sidekick based on usergroup and template?
4. Can we hide a used component from usergroup (author/publish)?
5. Can we restrict that a usergroup can edit, move or delete an already used component?
6. Can we restrict that a usergroup can use a page template?

Thanks in advance

Kristina

[Prince_Shivhare · Accepted solution]

Hey,

please check the link:

https://forums.adobe.com/thread/1097617

Check the comments:

On a JCR level this is easily possible, as you can set ACL on every node you want. And your component is also "only" a node. CQ5 itself is not designed to support component level security ootb, the smallest entity you can set ACLs on are pages. The useradmin does not support a granularity of components.So, as a recommendation: Do not try to implement component-based security. Because you will run into  problems you need to handle.

* Maintaining ACLs on components (no UI available for this ootb)

* The editmode is not built to handle write-protected components.

~ Prince

[kautuk_sahni]

Adding to what Prince has shared, please also have a look at this forum post:

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

// Component/dialog level permissions are not supported in AEM. The only way that is possible would be for some to add the permissions through the user admin.  Drill down to the nodes in the user admin and take a look, however this is officially not supported by Adobe. 

~kautuk

[kristinas125273]

Many thanks for your answers. We are first going to try it without restrictions.