Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Question about users and groups RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have an implementation question about Project Server, in specific the Project Sites being created. I would like to acheive the following things:

    - All AD users should have contribute access to every project site. In PWA they should have read access, but that's not required.

    - Every project site should have a associated site members group.

    - The project team members should be added to that group, so the project sites appears in their site membership subscriptions.

     

    I know the first one is acheivable and the other two probably require some coding. I noticed that in the project sites, there are groups being created like "Group Teammembers (Microsoft Project Server)" but I don't understand where the users in those groups are coming from. When I check the groups listed in the server settings, there is a group teammembers, but it doesn't contain any users. I've created a new group linked to an Active Directory group and set the correct rights for it. The correct users are selected, but the group doesn't show up in the groups on the project site and so the members don't have any rights. How can I push out the new group to existing project sites and make sure every user has at least read access to all of the sites?

    MCTS Web Application Development, SharePoint enthousiast.
    Wednesday, July 20, 2011 12:43 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    J,

    Project Server will overwrite permissions every time you do a project publish. This is controlled by some settings in Server Settings -> Project Site Provisioning Settings. You can disable automatic site permissions sync by removing the check box in section Project Site Permission.

    That's the way how project server is controlling permissions.

    To grant a contribute rights, user has to be in a team members group (read to have assignments in that project) or as Sunil mentioned to give them permissions "Contribute to Project WEb Access" but in this case users will be able to modify content in PWA and not just sites - which I would not recommend.

    To implement this functionality i would still consider event handler after publish or after check-in that will update project site permissions for specific users or to all users.

    Please note that if you have big number of users this operation might take significant time.

    Hope this helps.

     

     

    Thursday, July 28, 2011 4:41 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hmmm today I noticed another weird thing. It seems users only are granted with contribute rights on the project site when they actually have tasks assigned in the project. Adding them to the project resource pool doesn't enable access to the project site, only assigning them to a task does. Is this the behaviour as it should be? I would find it more logical to grant a user rights as soon as he or she is part of the resource pool of the project.

    MCTS Web Application Development, SharePoint enthousiast.
    Monday, July 25, 2011 12:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi J,
    Yes this is the expected behavior;
    You can see the following details to understand how the Project Site permissions works:
    • Project managers who have published a project or who have Save Project permissions on a project are added to the Project Managers (Microsoft Project Server) site group.
    • Team members with assignments in a project are added to the Team members (Microsoft Project Server) site group.
    • Other Project Server users who have View Project Site permission on a project are added to the Readers (Microsoft Project Server) site group.  

    Adding them to the resource pool does not mean that all the resources are part of the Projects and thus to the project site as well. Which is why only the resources of the project, based on the above explanation, can get access automatically to the project site.

    However you can make the permission process manula from server settings -> Project Site Provisioning Settings. And make this the task of the System Administrator to add all the users to the project sites.

    Hope this helps.

    Please mark as resolved if I've answered your question, vote for it as helpful to help other user's to find a solution quicker. | Khurram Jamshed | Follow my blog about Enterprise Project Management Solution | http://khurramjamshed.blogspot.com |
    Monday, July 25, 2011 12:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Khurram,

    Thanks for your answer. Could you perhaps answer my first questions too if you know the answer? :) Thanks!

    MCTS Web Application Development, SharePoint enthousiast.
    Monday, July 25, 2011 12:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello J,

    to provide all PWA users access to all project sites, create new category and give to all team members view project sites. In Bottom select "all projects". Screenshot is here: http://screencast.com/t/InR442qCH

    In this case, all team members will have access to all project sites no matter if they have tasks there / in project team. Note: Please make sure that there is no Deny in any other category.

    if you want to manage groups membership - you probably need to develop some custom code - event handler that will take care of performing additional work on sharepoint with users and their membership.

    Hope this helps.

    Best regards,

    Anton Kravtsov

    www.FluentPro.com

    Tuesday, July 26, 2011 5:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Anton,

    Super! Seems to work great! Now suppose I created my categoy and want to grant all users contribute rights instead of read rights? Is that possible too? Or is that what you mean with the membership part? I noticed that rights you set manually are overwritten by the project server rights sync, so won't that be the same case for custom code?

    MCTS Web Application Development, SharePoint enthousiast.
    Tuesday, July 26, 2011 6:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi J Siegmund

    For your first question, have a look at this thread below as well just in case you find it useful, however granting

    "Contribute to Project Web Access" permission to team members in combination with my organization category should help getting them contribute access on all project sites 

    In addition have a look at these blogs as well

    http://www.epmfaq.com/ssanderlin/project-server-2007/adjust-the-default-project-web-access-permission-levels 

    Also have a look at this technet doc : http://msdn.microsoft.com/en-us/library/cc197668.aspx

     

    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com
    Tuesday, July 26, 2011 1:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    J,

    Project Server will overwrite permissions every time you do a project publish. This is controlled by some settings in Server Settings -> Project Site Provisioning Settings. You can disable automatic site permissions sync by removing the check box in section Project Site Permission.

    That's the way how project server is controlling permissions.

    To grant a contribute rights, user has to be in a team members group (read to have assignments in that project) or as Sunil mentioned to give them permissions "Contribute to Project WEb Access" but in this case users will be able to modify content in PWA and not just sites - which I would not recommend.

    To implement this functionality i would still consider event handler after publish or after check-in that will update project site permissions for specific users or to all users.

    Please note that if you have big number of users this operation might take significant time.

    Hope this helps.

     

     

    Thursday, July 28, 2011 4:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks, I'll have a go at it!
    MCTS Web Application Development, SharePoint enthousiast.
    Friday, July 29, 2011 6:34 AM