none
Project Server default groups when we create new project site RRS feed

  • Question

  • Hi,

    When we create new project site in project server 2013 in site settings page some default groups are already present with some default permissions and some default members.

    Interesting thing is that the members of these group are same when ever we create a new site.

    Can you please help me understand, what these groups are, how they get created and how they are having some default members. Where are these members coming from.

    Our project server is having project server permission mode.

    Thanks,

    Bhawna.

    Tuesday, March 25, 2014 9:13 AM

Answers

  • This is actually not related to the issue in my test environment as stated in my previous reply, but my troubleshooting helped me understand your issue better.  There is probably a permission setting for your team members group that gives them "View Project Site" access for all projects (using a category).

    We our 2010 server set up this way in order to add read access to all resources on all project sites, then contribute access was added when they are assigned to tasks in a project. 

    Check your categories and permissions and see if it's set up that way - the team members group added to a category which gives "View Project Site" permission to all (or most) sites.  This is different in 2013 and gives contribute (Team Member) access to all the users instead of Read Access like it does in 2010. 

    I hope this helps!


    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Monday, December 1, 2014 7:49 PM

All replies

  • Hi Bhawna,

    Here is an excellent MPUG article that should answer your question:

    Http://www.mpug.com/articles/managing-project-web-app-site-permissions-project-online-project-server-2013/

    In case you still have some concerns about project server 2013 sites permissions in project server permission mode, feel free to ask.

    Hope this helps.


    Guillaume Rouyre - MBA, MCP, MCTS

    Tuesday, March 25, 2014 9:35 AM
    Moderator
  • Thanks Guillaume for your reply.

    Actually what I am not able to figure out is we are having more than 30 project server groups. Even many default groups are also there. But why only 3 of them always get added in site permissions when a new site is created.

    I understood that we can add or remove members to these groups. But by default how its taking its members?

    Thanks,

    Bhawna.

    Tuesday, March 25, 2014 11:04 AM
  • I briefly searched the MSTechNet but was not able to find a succinct article on this point for 2013, if someone has that, can they pls share. However, if you read most of the articles under this area, you get the idea. http://technet.microsoft.com/en-us/library/fp161361(v=office.15).aspx

     

    From 2010 this applies and is still "similar" http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx

     

    In 2013, for every Project Site (connected SharePoint site as it is now called in 2013), 2 Site specific SharePoint security groups are created: "SiteProjectName Project Managers (Project Web App Synchronized)" & "SiteProjectName Team Members (Project Web App Synchronized)".  And Web Administrators (Project Web App Synchronized) is also created.

    In addition, the default SharePoint groups for: Site Members, Site Owners, Site Visitors are present but remain empty.

    Project Server controls the creation of these groups and the membership. The membership is a "formula" that goes something like this: If the user is the Project Owner then put them in the PM group. If the user is a PWA Administrator, then put them in the Administrators group. If the user is a team member on the project, then put them in the Team Members group. There are other factors like RBS that are used in the formula.

     

    Reading the descriptions of the groups reveals that for Project Managers = Users who have Published this project or who have Save Project Permission in PWA.  For Team Members = Users who have assignments in this project in PWA.  I believe these are the old 2010 descriptions and actually Team Members = anyone who is part of the Build Team even if no assignments.

     

    Further complicating matters is that if you are a site collection admin, you will see all the groups, for PWA and for all the project site (b/c you are actually seeing the site collection groups).  But only the ones mentioned above apply specifically to this project site.

     

    Hope this sheds some light on the topic,


    Thanks, Eric S. Pcubed

    • Proposed as answer by ErockP3 Thursday, July 10, 2014 9:45 PM
    Tuesday, March 25, 2014 3:38 PM
  • Thanks Eric, that was really a great help. Just one query. If I am not adding any resource on project then also the members of these groups remain same. And every time a new site is created, it has same members.

    Could you please help me understand, if no resources or team is added then how the membership is defined.

    Thanks,

    Bhawna

    Tuesday, March 25, 2014 4:33 PM
  • I am experiencing the a similar issue in my test environment.  We have two PWA instances - one that has migrated data from 2010 and one that is completely clean.  In the "clean" environment, the (Project Web App Synchronized) groups work correctly - the only resources added to the Team Members group are the ones on the project team.  On the site with the migrated data, however, we have part of the issue you're experiencing - when we synchronize a Project Site (from the "Connected SharePoint Sites" page, it adds all three of those groups (with the project site name in front of the rest) with exactly the same membership for the Team Members as exists at the top PWA level. 

    However, when we publish a project from the client, those groups are not being added at all.  I thought this might have to do with Groups and Category permissions or Manager User Sync Settings under Security in PWA Settings, but I have ensured that the settings are all identical in both PWA instances.

    If we cannot have Project Server control the Project Members in the Project SharePoint sites automatically when you publish (and have it be correct) it's a bit of a deal breaker for us and we may never upgrade!

    Did you ever find an answer to this?  Thanks!

     

    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Tuesday, October 28, 2014 9:25 PM
  • Bhawna,

    Did you migrate data from Project Server 2010 to 2013?  I have tried toggling back and forth from SharePoint Permissions Mode and back to Project Server Permissions mode in the hopes that this would correct the issue.

    It has resulted in fixing the problem when you sync from the "Connected SharePoint Sites" page for us, so you might try that.

    We're still not seeing those Project Server Synchronized groups get created when we publish projects from the client however.

    Please let me know if you try that with any results. I'm also very curious to know if you migrated or if this is a new installation.

    Thanks!


    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Thursday, October 30, 2014 4:10 PM
  • Oh, and one aside - if you do toggle from SP to PS mode, it will delete your custom groups and you will have to set them up again.  With as many as 30, I figure a heads up is in order.

    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Thursday, October 30, 2014 4:13 PM
  • This is actually not related to the issue in my test environment as stated in my previous reply, but my troubleshooting helped me understand your issue better.  There is probably a permission setting for your team members group that gives them "View Project Site" access for all projects (using a category).

    We our 2010 server set up this way in order to add read access to all resources on all project sites, then contribute access was added when they are assigned to tasks in a project. 

    Check your categories and permissions and see if it's set up that way - the team members group added to a category which gives "View Project Site" permission to all (or most) sites.  This is different in 2013 and gives contribute (Team Member) access to all the users instead of Read Access like it does in 2010. 

    I hope this helps!


    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Monday, December 1, 2014 7:49 PM