Add a user account in Project Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2016-11-14

Every Microsoft Office Project Server 2007 and Microsoft Office Project Web Access user must have a user account before he or she can log on to Office Project Server 2007 and interact with Project Server data. User accounts can be added through the Manage Users page in Project Web Access Server Settings.


Windows users can also be added to Project Server security groups from the Active Directory directory service through Active Directory Synchronization.

Before you perform this procedure, confirm that:

  • You have read Manage users in Project Server 2007.

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

  • The user accounts you are adding are properly configured in either Active Directory or the forms-based membership provider so that their information is available to Office Project Server 2007. Office Project Server 2007 supports two authentication methods for its users (Windows authentication and forms-based authentication). For more information about supported authentication methods for Office Project Server 2007, see Plan Project Server 2007 authentication method.


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

To add a user account

Use this procedure to add a Office Project Server 2007 user account to your Office Project Server 2007 instance.

Add a user account

  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 Users.

  3. On the Manage Users page, click New User.

  4. On the New User page, in the Identification Information section, do the following, as needed:

    1. Select User can be assigned as a resource if you want this user account to be able to be assigned tasks as a resource. Selecting this entry makes the user an Enterprise Resource. This setting is selected by default.

    2. In the Display Name text box, type the name for the user account. This is a required field.

    3. Optionally, in the E-mail address text box, type the email address for the user. If you want this user to be emailed for notifications and reminders, this is a required field.

    4. Optionally, in the RBS box, enter a Resource Breakdown Structure code value. Click the Select Value icon to display the RBS Code list from which you can select a value. The RBS code defines the hierarchical position that a resource holds in the organization.

    5. Optionally, in the Initials box, type the initials for the user.

    6. If the user maintains a team Web site, type the hyperlink destination and URL address in the Hyperlink Name and Hyperlink URL boxes, respectively.

  5. In the User Authentication section, select the method for authenticating this user when he logs on. You can select either:

    1. Windows Authentication, using the Windows account   If you select this authentication method, type the user's account name in the User logon account box in the form of DomainName\UserAccountName. To prevent the user's information from being synchronized with your organization's Active Directory directory service, select Prevent Active Directory synchronization for this user.

    2. Form authentication, using the fully qualified provider user name (MembershipProvider:UserAccount)   If you select this authentication method, type the user account name in the form of MembershipProvider:UserAccount.

  6. In the Assignment Attributes section, specify the following information about the user's ability to be assigned to projects as a resource:

    1. Select Resource can be leveled to allow the user to be subject to the leveling process. This option is selected by default.

      Leveling is the process used to resolve resource conflicts or over-allocations by delaying or splitting certain tasks. When Project levels a resource, its selected assignments are distributed and rescheduled. For more information about leveling, see the Office Online article Distribute project work evenly (level resource assignments) (\&clcid=0x40).

    2. In the Base Calendar list, select a base calendar for the user. A base calendar is a calendar that can be used as a project and task calendar that specifies default working and non-working time for a set of resources. For more information about base calendars, see the Office Online article Overview: Using Calendars in Project (\&clcid=0x40).

    3. In the Default Booking Type list, select the user's booking type as either Committed or Proposed. A committed resource is formally allocated to any task assignment within a project. A proposed resource has a pending resource allocation to a task assignment that has not yet been authorized. This resource assignment does not detract from the availability of the resource to work on other projects.

    4. In the Timesheet manager box, if the user has a timesheet manager, type or search for the manager's name. For more information about timesheet managers, see Timesheet approval configuration.

    5. In the Default Assignment Owner text box, type or search for the default assignment owners. An assignment owner is an enterprise resource who is responsible for entering progress information in Project Web Access. This person can be different from the person initially assigned to the task.

    6. In the Earliest Available box, type or select the earliest date that the user will be available as a resource.

    7. In the Latest Available box, type or select the date latest date that the user will be available as a resource.

  7. In the Security Groups section, in the Available Groups list, select the groups to which the user will belong and then click Add. The groups that you select appear in the Groups that contain this user list. If you want the user to be a member of all available groups, click Add All. Users automatically inherit the permissions associated with any groups they belong to.

    Use the Remove and Remove All buttons to remove the user from groups to which they currently belong.

  8. In the Security Categories section, in the Available Categories list, select the category which the user will access, and then click Add. The categories that you select appear in the Selected Categories list. If you want the user to access all available categories, click Add All.

    For each category in the Selected Categories list, specify the permissions that you want the user to have when the user accesses the category. The category permissions list for a specific category will appear when you select the corresponding category in the Selected Category list.

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

    • To set permissions by using a security template, in the Selected Categories list, select the category 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 in the Selected Categories list, select the category to which you want to apply permissions. In the Permissions list, click Allow or Deny for each activity. In most cases, you only need to set permissions at the group level rather than configuring permissions for individual users; use category permissions for users with special needs that are not covered by the permissions that are assigned to groups.


      For more information about category permissions, see Microsoft Office Project Server 2007 category permissions.

  9. In the Global Permissions section, select the global permissions for the user. You can apply global permissions manually or by using a security template. To set global permissions using a template, select the template to apply from the list next to the Set Permissions with Template button, and then click Apply.


    For more information about global permissions, see Microsoft Office Project Server 2007 global permissions.

  10. In the Group Fields section, if your organization created codes for grouping and costing purposes, type these codes in the Group box, Code box, Cost Center box, or Cost Type box.

  11. In the Team Details section, if you want the user to be a member of an existing team, select Team Assignment Pool, and then type the name of the team in the Team Name box.

  12. In the System Identification section, you can optionally type additional identifying information for the user in the External ID box. This information can be used to link the person to corresponding information in a human resources department, or to facilitate the consolidation of reporting of resource use beyond what Project Server provides.

  13. Click Save.

Additional considerations

When adding user accounts, keep the following in mind:

  • It is a best practice to avoid assigning global permissions directly to individual user accounts. It is preferable to add users to groups that have the required permissions.

  • If you have more than 400 Project Server users in your organization, the user list on the Manage User page will not appear. This is done by design, because loading a large number of users to the page can cause performance issues. Although the user list does not appear, you can use the search options to list users by user name or e-mail address.

See Also


Manage users in Project Server 2007