OOTB access control policies

[JosephCugini]

As many have suggested I am currently looking at the out-of-the-box
access control policies installed with Intralink 9.1 and moving them
from the Product/Library context to the PDM Domain. I will then delete
the policies at the Product/Library level and make a template. When new
Product/Library's are created I'll use the template and inherit the
desired policies from the parent domain. So far easy enough....



As I go through this exercise I see policies in the Product context that
are associated to hidden roles. Any good reason why these roles are
hidden out of the box but rules are written against them?



I also see a rule written for the Product Manager, against WtObject, for
all states, full control. Isn't that a bit gracious? I'm taking that
to mean they can do what they want to any object, at any time. I would
think this use case would be reserved for administrators only.

[HugoHermans]

I don't have the rule for the "Product Manager - WTObject - All States -
Full Control" anymore, so I must have removed it. There were similar
rules for guests and members I've removed. I also cleaned duplicate
rules. Quiet a job, going step by step, and I think I could/should go
further in this direction.

Met vriendelijke groeten, Hugo.

NV Michel Van de Wiele
Carpet and Velvet weaving machines
M. Vandewielestraat 7
8510 Marke, Belgium