I feel that acl*access-policy-approvers should be some acl* project. Members of that group can verify signatures in Legalpad. Sorry if my assumption is wrong. I can't remember if I've reported this in the past either (I run some searches and I could not find).
I suggest that the project be renamed to acl*access-policy, type policy, membership restricted to the members of that group.
Okay I've found the link: Z308#6476 but I never filled a report for that. It's now done :)
Sorry if I didn't catch it right. So I see there's a Policy-Admins group with various acl* subprojects. Maybe what we can do for this task is to create a subproject for that policy-admins group such as acl*confidentiality_agreement_legalpad (or a best suited name) and have them being the only ones to manage and see signatures of the Legalpad documents relating to CU/OS permissions?
Thanks @mmodell - I'm just a bit confused about policies and spaces. We just need to make sure the people of that group are the only ones able to see those signatures. Will this be achieved with this? I'd however wait for James 'ok' before proceeding though. Thanks.
As a side note, maybe we can do this same operation with L23. It does seem that there's no project for managing who can have access to that?
Nothing related to Spaces or Policy-Admins. This should just be acl*access-policy-approvers.
Linking is now possible. All that remains is to edit the project image and we're all set!