I am slowly pulling out what little hair I have left….
We opt to create connected sharepoint collaboration sites for all of our projects on project server 2013. And we have decided to open up the SharePoint sites to users outside of the normal project server users.
We figured that the project owner or an admin would simply share out the SharePoint collab site to each extended project team member without allocating a license to use project server. This has worked – but only to a degree. The user can see the SharePoint site and can collaborate and upload and edit documents. However, as soon as they click on the ‘Tasks’ item within the quick launch menu within the SharePoint site (not project server) they get a ‘not shared’ / ‘no access’ style message.
We have checked that they are in the site’s ‘members / collaborate’ group and I can even go to the task list and check the access and they are on the list – it’s almost as if the security of the actual task list is being ignored perhaps there is a webpart that has a separate default security that is overriding the site based security.
OK funny, nice hair…:-) That’s an interesting behavior and not what I’ve experienced. Are you using SharePoint or Project Server permissions mode? I assume from your comments that these are enterprise projects (not SharePoint task list projects). Do the permissions change if you then add them as a resource? Can they see the Project Summary web part on the home page? Now I originally assumed this was a Project Server on-premise install, but is it Project Online?
I hate to say this but (for on-premise) anyone who has direct access to any Project Server data (including a site that’s synchronized) then they require a CAL. It’s no longer only active users in Project Server. Off the top of my head I don’t know specifics for Project Online but I assume the same basic requirements.
Let me know what you think. I’d love to help and learn at the same time.