Product team and Org level ACL's

[WayneBeck]

We have created a new product team template to correct some permission issues. We set the ACL's at the Org level. Until we get all items moved into these new products we created a ACL that gave them the same permissions as they currently do. This does not seem to work. We then went into the ACL's for the new product and created the same permission set. This then worked. We then removed this ACL at the product level and the Org one worked correctly. It appears theinheritance from the Org is not working at first. But we can jar it loose. We tried removing the user and the group from cache this did not fix the issue. We are seeing this for all the new ACL's we have setup. Is there a cache that can be deleted to force a reevaluation of the ACL's?

[MikeLockwood]

Don't have to move items into new product contexts (very laborious).
Can instead modify the ACL's in the existing products. Worth it to do this carefully on rehosted system first and prove out all changes, then carefully make those changes to production.

Using Manage Security for documents / change requests at various states is very helpful - in fact, it's worth it to create test data at all states just for this purpose.