Creating Users to Select as Administrators
 |
Only members of an organization can be organization administrators, product creators, library creators, project creators, or program creators.
|
In a production environment, users are usually defined in an enterprise directory that is set up during installation. If you are setting up a test system and do not have a set of users from which to select administrators, you can create a set of test users in the default directory service using the Participant Administration utility. The Participant Administration utility is available from Site 
> .
> .The Administrator user that is created during the installation (for example, wcadmin) is not associated to a specific organization; this user does not have the organization attribute (usually “o”) set. Therefore, this user cannot be added as an organization administrator unless the Administrator user is updated to include the organization attribute. You can use the Participant Administration utility to update the Administrator user.
| | If your site does not use the organization attribute in the directory service entry, users can be assigned to an organization using the usersOrganizationName property. For more information on using this property, see Configuring Additional Enterprise Directories. |
At a minimum, you need to either update the Administrator user so the user is a member of the default organization or create another user who can be the organization administrator. This user can then administer the organization and create products, libraries, projects, and programs.
 | If you want to use a site administrator to manage organizations, you should create a second site administrator for these tasks to improve Windchill performance. For more information, see Establishing Site Administrators. |