Export (0) Print
Expand All

Create a category

Updated: December 20, 2007

 

Topic Last Modified: 2007-12-18

You can add custom security categories as necessary to create a Project Server security model that meets the specific needs of users and groups in your organization.

Before you perform this procedure, confirm that:

  • You have read Manage categories in Project Server 2007.

  • You have access to Office Project Server 2007 through Project Web Access.

    ImportantImportant:
    The Manage users and groups global permission in Office Project Server 2007 is required to complete this procedure.

Perform the following procedure to create a category in Office Project Server 2007.

Add a category
  1. On the Project Web Access home page, in the Quick Launch, click Server Settings.

  2. On the Server Settings page, in the Security section, click Manage Categories.

  3. On the Manage Categories page, click New Category.

  4. On the Add or Edit Category page, in the Name and Description section:

    1. In the Category Name box, type a name for the category.

    2. In the Description box, type a short description of the category.

  5. In the Users and Groups section, select the users and groups you want to include in this category. In the Available User and Groups list, select the users and groups you want to include in the category, and then click Add. Group names will be noted with an asterisk. Hold down the CTRL key to select multiple users and groups. Use the Add All button to include all available users and groups in the category. Users and groups added to the category appear in the Users and Groups with permissions list.

    Use the Remove or Remove All button to remove any users or groups that are currently included in the category.

    For each user or group in the Users and Groups with permissions list, specify the permissions that you want the user or group to have when he or she accesses the category. The category permissions list for a selected user or group appears when you select the corresponding user or group in the Users and Groups with permissions list.

    You can set permissions manually for any user or group or you can apply a security template that contains predefined permission settings.

    • To set permissions by using a security template, in the Users and Groups with permissions list, select the user or group to which you want to apply the template. Select the template to apply from the list next to the Set Permissions with Template button, and then click Apply.

    • To set permissions manually, select the user or group to which you want to apply permissions from the Users and Groups with permissions list. In the Permissions list that appears, click Allow or Deny for each activity.

      NoteNote:
      For more information about category permissions, see Microsoft Office Project Server 2007 category permissions.
  6. In the Project section, specify the projects that users with access to this category can view. There are two options.

    1. Select All current and future projects in the Project Server database if you want users and groups with access to this category to see all projects.

    2. Select Only the project indicated if you want users and groups with access to this category to access only the projects you specify. Select the projects you want to be accessible through the category from the Available projects list. Use the Add or Add All button to move projects to the Selected projects list.

      Use the Apply the above Project security permissions to all projects where option to use dynamic rules to determine which projects that users or groups in this category are allowed to access. Select any of the available options:

       

      Dynamic project rule Effect

      The User is the Project Owner or the User is the Status Manager on assignments within that Project.

      Gives users permissions on any project they own. Also gives Status Managers permissions on projects that contain assignments that they manage.

      The User is on that project's Project Team

      Gives users permissions on any project where they are on the project team. Users do not need to have assignments on the project.

      The Project Owner is a descendant of the User via RBS

      Gives users permissions on any project that is managed by resources subordinate to them in the Resource Breakdown Structure (RBS) hierarchy.

      A resource on the project's Project Team is a descendant of the User via RBS

      Allows a user to view any project where a resource is subordinate to the user in the RBS and the resource is on the project team.

      NoteNote:
      Avoid using this rule for users who have many resources under them in the RBS. If the resources under them are on a lot of projects involving many categories, this stress on the authorization system can affect performance (for example, delay the loading of the Project Center page).

      The Project Owner has the same RBS value as the User

      Allows a user to view projects managed by persons that have the same RBS value that the user has.

      NoteNote:
      Use of the dynamic rules is enabled by selecting Only the project indicated. If you solely want to use dynamic rules to allow your users to access projects, then select Only the projects indicated, do not select any projects from the Available projects list, and select your dynamic rules. However, it is possible to also select specific projects as well as use dynamic rules to allow your users to access projects.
  7. In the Resources section, select the resources that the users with access to this category can view. There are three options:

    1. Select All current and future resource in the Project Server database if you want all users and groups who access this category to see information about all resources.

      NoteNote:
      Selecting the All current and future resource in the Project Server database option restricts you from using the dynamic rules.
    2. Select Only the resources indicated if you want users and groups with access to this category to see only the resources you specify. Select the resources that you want users to see information about from the Available resources list. Use the Add or Add All button to move resources to the Selected resources list.

    3. Use the Apply the above Resource security permissions to all resources where option to use dynamic rules to determine which resources that users or groups in this category are allowed to see. You can select any of the available options:

       

      Dynamic resource rule Effect

      The User is the resource

      Gives users permissions to view information about themselves (such as assignments).

      They are members of a Project Team on a project owned by the User

      Gives users permissions to view information for all resources in projects they own.

      They are descendants of the User via RBS

      Gives users permissions to view information for all resources under them in the RBS.

      They are direct descendants of the User via RBS

      Gives users permissions to view information about resources that are directly under them in the RBS.

      They have the same RBS value as the User

      Gives user permissions to view information about resources that have the same RBS value.

      NoteNote:
      Use of the dynamic rules is enabled by selecting Only the resources indicated. If you solely want to use dynamic rules to view resources, then select Only the resources indicated, do not select any resources from the Available Resources list, and select your dynamic rules. However, it is possible to also select specific resources as well as use dynamic rules to view resources.
  8. In the Views - Add to Category section, specify which views that the user and group who access this category can view. From the View list, select the check box next to the view that you want to add.

  9. Click Save.

When creating categories in Office Project Server 2007, note the following:

  • Avoid creating unnecessary categories. Having a large number of groups and categories within an organization can stress the authorization system, which can affect performance.

  • If there are many users at the highest level of the RBS, consider adding them to a custom category that gives them visibility of all projects (avoiding dynamic rules). Top-level RBS users probably have access to all projects, so assigning them to this category avoids unneeded work by the authorization system.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft