It would be really nice, if I could have the ACLs of a version 1 entity to be automatically copied to a version 2 entity during a lifecycle state change.  In the situation where we want unique security per Item, or per Folder.    What I specifically need is this: I want to place PDFs, DXFs, MS Word Docs, and CAD Files into separate Items, then group the items into a single master item.  Then I want to release that Item so the non-engineering staff can see the Item and its contents on the Thin Client, while the engineering staff, can manage secure version control in-house.  However, I want the CAD files sub-Item to be denied to the viewers, for viewing and downloading.   What I have tried is this: I created my own extension to add the custom ACL to deny the viewers permission to the newly created CAD Files-Item in the item master, and the CAD Files-Folder in the project explorer.  This works until any lifecycle change is made, so I attempted to remove the lifecycle security roles from the system.  Since a new Item Revision is created, the ACLs are not added at all, or copied from the previous, and now all the CAD files are visible thru the Item on the thin client, and can even be downloaded.   Options that can be done to help: Vault can copy ACLs from child to parent if Role based security is removed. Vault Thin client, can verify folder security and apply it to any file within an Item attachement, whereby denying visibility of attachements, because they are in a secured folder (that has read only = deny). Vault can allow ACLs to blend with Role based security, then copy the ACLs to each new item.  Then I can have the best of all security, a role based security for engineers, and a customizable ACL based security for Viewers per entity or folder (at least). Please help.   Jamie V. Johnson Show More