Groups field not allowing Template to be applied

[User175049]

On sys_template, the groups field is no longer allowing the listed Group(s) access to view/apply the template.  I tested the user field, and it works as expected.  I tried creating a new template as well as modifying current ones, and both times the groups field did not provide the ability to apply the template.  Any current template that already had a group(s) listed still allows access to the template. However, if you add another group, the newly add group will not work. Since the user field does grant permissions, I compared the ACLs and noticed groups has a read and write ACL whereas the user only has a write Access Control. I modified the groups ACL to mimic the user and this still did not allow group to apply the template.   This appears to be a recent issue. although, I cannot find an exact time the change occurred.  Does anyone else have this problem? If so, how do you allow groups the ability to apply a template, without making the template Global? 

~m

[Oliver Stammler · Accepted solution]

Hey @User175049,

first of all: I just tested this on an out of the box standard PDI and the functionality itself works just fine.
I therefore assume that somebody has made some changes to your instance which are causing this issue to appear now. Based on this I would also suggest to revert your changes back to the out of the box standard. 

So let's think together about possible causes:

Groups can only apply templates when the individual users have read access to the sys_template table. So if they can't read the tables, they can't apply them. This should be the sys_id of the ootb ACL which checks for the groups "8f66f7f1c0a80165015fb84a5081ef10". On my tokyo instance it looks like this:

Best regards

Oli