Setting access rights at component level

Question

I have created a component. The business wants to restrict its use to a certain group of users.
If a user is part of that group, ONLY then the coomponent should be available in sidekick at time of page creation.
How is setting access rights at component level being achieved?

Answer 1

As Jorg stated, Group ACL settings are meant to control access at a page
level.  As he also stated is possible to control access even further, but
with additional effort and difficulty. But, nearly every client wants this
done down to the component level and on a group by group basis.  So, what
I've found, over the years that works is the following:
- Configure the available components per template type per parsys
- Further configure the available components at the group level
For the custom built components, you can remove them at the group level by
un-checking the 'read' ACL on the dialogs for the given component.  You
don't want to un-check read for the whole component because then the users
of that group experience random 'holes' in the content.  But, if you
un-check 'read' for the dialogs, then the component will not display in
Side-kick (at least on 5.4 and prior this is the case).
The only caveat to this is the OOB components.  That is where you will run
into a lot more difficulty.  Those should mostly be enabled/disabled at the
design level for the entire page/parsys.
Hope this helps.
Todd