I don't think the out-of-the-box ACLs can distinguish by a sub-type. (Drawings, assemblies, family table instances, skeleton models, etc.) What you could do is write a fairly simple add-on that would analyze each model being checked in and see if it contains a family table and the target context, and then block the check-in if the criteria matches. @d_graham should be able to help...
Just as a thought. If you're using ModelCHECK as a gateway into Windchill, you could setup a ModelCHECK condition specific to the users you don't want creating family table objects. The condition can specify a check file that specifies an error on family table items [FAMILY_INFO] and specifies start model check file that includes a file name test that will always fail.
IF (USERNAME EQ baduser) config=(check/baduser_checks.mch)(start/baduser_start.mcs)(constant/mm.mcn)
FAMILY_INFO Y/N/E/W E E E E E
PRT_MODEL_NAME EQ __FFF___
ASM_MODEL_NAME EQ __XXX___
I haven't tested any of this, but in theory it should work.
Hello Darel Coterel,
I'm Charles from PTC Technical support in Europe, I'll will assist you on this request.
Can you have a look at knowledge database article CS325253 ? Unfortunately it is not possible to configure access rights for family tables.
I remain at your disposal for any questions or concerns.