We are on Project Server 2013, February CU, Project Permissions Mode.
We just upgraded from 2010 last week and just discovered that we have an issue which we can't figure out - it may even be "expected behavior", but if it is, it's not explained very well in the literature.
In 2010, we had a PWA level SharePoint group with specific membership which we manually added to every site when it was created. We let Project do its thing when publishing/syncing the rest of the user access and all was well. However, in 2013, it appears that every time a project site synced (either through publishing or manual sync from the Connected SharePoint Sites page) themembership of that group is changed across the site collection. It removes the resources which we originally had in the group and adds a whole bunch of names which seem to match everyone who has read on whatever site was synced.
Since the function of this group is for Project Oversight, and the group is also added to an uninherited document library with restrictive permissions, you can see how we would be distressed about this - how is it even connecting that SharePoint group (manually created, not in any way connected to Project Server, or it shouldn't be, any way) and deciding who to add? Has anyone seen this? We've tried unchecking the "<label for="_enablePWASync">Enable Project Web App Sync" option in the site sync settings, and we've made sure that the group doesn't have any permissions on any sites that are created by Project Server. </label>
We have hundreds of sites which all need these custom permissions and it would be a lot of work to reconfigure these groups. Has anyone seen this before? Any help would be appreciated.
Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/