Hello,
Maybe this is a simple thing, but we're having some troubles. What we have is Project Managers often have a document library in their Project Sites that contain files that should only be accessible by certain users, so they disable inheritance for those libraries. They end up with the PM and anyone else they choose having access to the library and the rest of the Team Members that have access to the Project Site do not even see the folder. So all is good there.
The problem is when we realize we need to modify the PWA permissions for whatever reason. For example, we realized Team Members could not view the Project Detail Page, so we modified the permissions for the Team Members group in Server Settings to add that ability. Once we hit Save, PWA resynchronizes all permissions as expected, but it also blows away permissions for any library that does not inherit permissions. That means the Project Managers can no longer see or access the folder or folders they created that were configured with custom permissions.
This makes no sense to me. Why would PWA even touch a library with custom permissions? And when it does, why would it strip permissions instead of perhaps resetting it to inherit from parent? When stuff like this happens it means I, as the sys admin, get to waste a bunch of time sitting down with each Project Manager figuring out which libraries we need to reconfigure so they can access them again.
Out of all of this, my question is:
-what's the best or correct way to configure libraries in Project Sites to use unique permissions that won't get blasted away when we modify group permissions in PWA?
And perhaps a side question, would unchecking "automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project Server. When the check box is cleared, Project Server users are never synchronized with Project Sites." from Project Site Provisioning Settings avoid this?
Thanks,
Aaron