By default, this feature is enabled and synchronizes members of Project Server security groups with the corresponding SharePoint groups. In the newer versions, the selection of Project Server Permissions mode enables a feature called вЂњProject Web App SyncвЂќ.

The difference is that in 2010 the administrator could change the permission level for the Project Managers group, and the permissions would not change subsequently.

In Project Server 2010, the default permissions for Project Managers allowed powerful editing rights to the PWA site, just as in Project Online/Project Server 2013. PWA Permissions Changes for Project Online and Project Server 2013 The objective is to ensure that all PWA users, with the exception of PWA administrators, have no design permissions to the PWA site. This technique is applicable to both Project Online and on-premise Project Server 2013. This article describes a technique for implementing these security settings for the case where Project Server Permissions mode is deployed. In our experience, most organizations do not want to grant these rights to any users who are not application administrators. By default, members of the Project Managers group have powerful permissions to customize the PWA site. In the example above, a very creative project manager decided to вЂњChange the lookвЂќ of PWA, not realizing that this change impacted all users. When you open PWA, everything is pink! It wasnвЂ™t like this yesterday, so what happened? Imagine that you arrive at work and decide to connect to your Project Web App (PWA) to check the status of your projects.

Microsoft project online delete project