Within several PWA configurations in different Project Server and Project Online environments I faced a strange issue with the Track Your Work Webpart over and over again, so I thought it’s worth it to add a short post about it.by
There are two different adjusting screws to administer the project web app:
1) Within the respective instance you can change the site settings and pwa settings for a single site or site collection (if the prerequisites in Office 365 are done).
2) In the SharePoint Admin Center you can not only create and delete site collections, several PWA options in Project Online are also transferred to Office 365. Sounds a little bit like it was done in the Central Administration with an on-premise system, right? However, among other things in the SharePoint Admin Center you can change the permission mode, define quotas and control who’s able to see and edit the site collection settings in the PWA.
At first I thought it is a bug, but I was wrong with that: Since recently, 9999 PWA instances are available for each Project Online tenant. Admins will no longer start to sweat with an annoying limit of 7 PWA instances in the back. Definitely this extends possible scenarios in a lot of areas, e.g. security, trainings and testing.by