Add or change a user

  1. On the Quick Launch, click Server Settings.

  2. On the Server Settings page, click Manage Users.

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

    To change the settings for an existing user, click the user's name in the table, and then complete the rest of the steps in this procedure. If no user names appear in the table, search for the user by typing all or part of the user's name or e-mail name and then click Search.

  4. On the New User page (or the Edit User page if you are modifying an existing user), in the Identification Information section, type the user's display name, e-mail address, phonetic spelling of the name, initials, and Resource Breakdown Structure (RBS) value.

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

    Note: To allow the user to be assigned to tasks as a resource, select the User can be assigned as a resource check box. Selecting this check box specifies that the user is an enterprise resource.

  5. In the User Authentication section, select a method for authenticating users when they log on:

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

    • Forms authentication     If you select this authentication method, type the user's account name in the form of MemberShipProvider:UserAccountName.

      Important: The exact form of the account name is determined during Setup of Microsoft Office Project Server 2007, and it may be different from the form suggested here. Check with your system administrator or the person who installed Project Server to determine the form of the account name.

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

    • To exclude this user from the leveling process, clear the Resource can be leveled check box. Next, select the base calendar that you want to assign to the user.

    • Select the user's booking type as either committed or proposed in the Default Booking Type list.

    • If the user has a timesheet manager, in the Timesheet Manager box, type or search for the manager's name.

      In the Default Assignment Owner box, type or search for the assignment owner's name.

    • To specify the user's availability, type the dates in the Earliest Available box and the Latest Available box.

      Tip: Click the Date Picker calendar , and then click the dates on the calendar.

  7. In the Resource Custom Fields section, type the values that represent any custom fields that were created for your organization. This section appears only if your organization uses resource custom fields.

  8. In the Security Groups section, click a group in the Available Groups table, and then click Add. The resource is added to the Groups that contain this user table.

    Click Add All to add this user to all available groups. Users automatically inherit the same permissions that were assigned to the groups.

  9. In the Security Categories section, in the Available Categories list, select the categories that the user can access, and then click Add. Click Add All to add this user to all available categories.

  10. For each category in the Selected Categories list, specify the permissions that you want the user to have when he or she accesses the category. In the Global Permissions section, select one of the following check boxes for each permission:

    • Allow      Select this check box to explicitly allow permission for the user.

    • Deny      Select this check box to explicitly deny permission for the user.

      Notes: 

      • If neither Allow nor Deny is selected, users will not have access to the category unless they are explicitly given access elsewhere, for example, by the permissions set on a group to which they belong.

      • In most cases, you need to set permissions only at the group level and not at the user level. Use global permissions for users with specific permissions that are not covered by the group's permissions.

      • If a permission is set to Allow at the user level, and is set to Deny at the group level, the permission will be denied. Group level permissions take precendence over user level permissions.

      • To quickly set permissions, you can use a template. In the Set permissions with Template box, select the security template that you want to apply toward the user's permission settings, and then click Apply.

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

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

  13. In the System Identification Data section, 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.

Why can't I perform some actions in Microsoft Office Project Web Access?

Depending on the permissions settings you used to log on to Project Web Access, you may not be able to see or use certain features. Also, what you see on some pages may differ from what is documented if your server administrator customized Project Web Access and did not customize the Help to match.

Top of Page

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×