Resource assigned to additional Groups not reflected in Categories RRS feed

  • Question

  • We are not able to view the Resource Category assignments after they were added to additional Groups in PS2010 (PWA). Let me describe the scenario:


    All users belong to the “team member” group and show the associated category of “my tasks” upon account creation through Active Directory synchronization (all users belong to the AD team member group that synchronizes with Project Server’s “team member” group).


    1.       We created Enterprise Resources.

    2.       We assigned these resources to some of the Groups, by going to “server settings”, “manage groups”,

    3.       We assigned the Groups to various Categories.

    4.       We added a few Enterprise Resources to additional Groups.

    5.       When we viewed details on these Users in “manage users”, the new Group assignment showed in “manager users”, however, the categories remain as they were in spite of the new Groups assignments that have additional categories.  We saw only those Categories in the Resource details to which were initially assigned in the Step 3.


    We were expecting to see the additional categories for the users when we viewed them in “manage users”. We expected that once the Resources were added to the additional Groups (Step 4), the additional Categories will automatically reflect for these Resources (as defined under the Step 3) for these Resources. We checked the Resources details for these Users as well, as these resources are also users.  But, the Resource details also do not reflect additional Categories for these Users.


    Should we be able to see the additional categories in “manage users” that result from being added to a new group?
    shyam koppikar
    Wednesday, January 18, 2012 8:13 PM

All replies

  • Shyam --
    You are not understanding how Project Server 2010 works and that what you see is normal.  In fact, the path you are following is a big mistake and will eventually cause you problems.
    When you add a user to a security Group, the system automatically gives the user access to the projects, resources, and views specified in the security Categories that below to the Group, and the Group also gives the user the permissions specified in the Global Permissions area of that Group.  Keep in mind, however, that the system DOES NOT show those Categories when you open the user account for editing, or show those Global Permissions.  That is the default behavior of the software.
    In fact, if you manually add Categories to a user account, you are creating OVERRIDE permissions for that user, and are creating a level of complexity that makes it difficult to manage your security environment.  Beyond this, you should NEVER specify Global Permissions for any user.  When you do this, again, you are creating OVERRIDE permissions for that user, and creating an even more complex environment in which to manage security.  With all due haste, I strongly recommend that you reopen EVERY user account, remove any Categories you added, and remove any of the Global Permissions that you set for the user as well.
    Best practices dictate that you control security by adding users to Groups and that you only add Categories or set Global Permissions for individual user accounts that need some additional kind of permissions or access to other objects, and you should keep these exceptions to the bare minimum possible.  Hope this helps.

    Dale A. Howard [MVP]
    VP of Educational Services
    "We write the books on Project Server"

    Wednesday, January 18, 2012 8:25 PM