Identify the user for purposes of group membership, access control rules, event notification rules, and logging on. The name entered here does not need to be unique; however, the user's distinguished name (which is made up of directory attributes that include the user name and directory location) must be unique.

User login names cannot contain the following characters: #, /, >, \, and <.

User login names cannot contain extended ASCII characters such as ä, ê, ì, õ, ǚ, æ, and so on.

This is a required field.

Specify the full name of the user. There is no requirement for how to specify the full name. For example, the name could be entered as “John Doe” or “Doe, John”.

Specify the last name of the user.

Select the checkbox to allow the full name, last name, or email address of the user to be automatically synchronized between LDAP and the database. This prevents problems that can occur when user attributes are changed in LDAP.

Specify the user's email address.

Although entering a value in the Email field is not required, the following features require that participants have an email address:

If users do not have the email attribute set in their directory service entry, the users do not appear when a search is made in the features that require an email address.

Specify the user's mailing address.

Specify the user's primary telephone number.

Specify the user's secondary telephone number.

Specify the user's fax number.

Specify the URL of a personal website.

Select the organization name to use as the organization attribute value in the user directory entry.

To select from a list of existing organizations, click Find. The Find Organizations window opens for searching for and selecting an organization.

Select the user's preferred template language from the drop-down list.

This is a required field.

Select the directory service in which you want the user entry to reside. The drop-down list displays all of the services that have been established.

User directory services are established by setting up JNDI adapter entries through the Info*Engine Property Administrator and adding the adapter entries to the wt.federation.org.directoryServices property. For additional information, see Working with LDAP Directory Services.

Select the domain with which the user is associated. A domain is an administrative area that defines a set of administrative policies, such as access control, indexing, and notification. Objects associated with a domain are subject to its policies.

To select from a list of existing domains, click Find. The Find Domain window opens and you can search for and select a domain. You can also type the name of an existing domain into the Context field.

If you do not enter a domain in this field, Windchill determines which domain to set according to the domain algorithm that is in place. For information about domains, see Administering Domains and Policies.

Select the domain with which the user's cabinet is associated.

To select from a list of existing domains that have been created, click Find. The Find Domain window opens and you can search for and select a domain.

If you do not enter a domain in this field, Windchill determines which domain to set according to the established domain algorithm. For information about domains, see Administering Domains and Policies.

Specify the user's password.

This is a required field.

Confirm the entry of the user's password.

This is a required field.

Specify additional names under which this user wants to access Windchill. You can enter up to four additional names by entering the first name in the Alternate User Name 1 field, the second name in Alternate User Name 2, and so on. For example, if a user works with two Pro/INTRALINK installations and has a unique user name on each installation, you could enter those names in two of the Alternate User Name <x> fields.

Alternate User Name 1 and additional Alternate User fields can be added to all user information pages by editing the layout of those pages in the Type and Attribute Management utility. For more information, see About the Type and Attribute Management Utility.