Security Guide for Siebel eBusiness Applications > User Administration > Adding a User to the Siebel Database >

Adding a New Employee

At a minimum, an employee must have a position, a responsibility, and a Siebel user ID.

You can also associate attributes with employee records such as skills, tools, assignment rules, and availability. By doing so, you can use the employee record and its attributes with features such as Siebel Assignment Manager and Siebel Professional Services Automation.

The following procedure creates a User record for the employee only as a stage in allowing the employee to access the database.

To add a new employee

1. Log in as an administrator to a employee application, such as Siebel Call Center, and then choose Navigate > Site Map > Administration - User > Employees.

   The Employees list appears.

2. Add a new record.
3. Complete the following fields, then save the record. Use the indicated guidelines.

   Field	Guideline
   Last Name	Required. Enter any name.
   First Name	Required. Enter any name.
   User ID	Required. Enter a simple contiguous user ID, which must be unique for each user. Typically, the user provides this user ID to log in. Depending on how you configure authentication, the user may or may not log in with this identifier. If you implement database authentication, this field must be the login name for a database account.
   Password	Optional (required for some authentication implementations). Enter a simple contiguous login password. The password must conform to the syntax requirements of your authentication system, but it is not checked for conformity in this form. For LDAP/ADSI security adapter authentication, the password is propagated to the user directory. For database authentication, the password is propagated to the database. For information about user authentication architectures, see Security Adapter Authentication.
   Responsibility	Required. Pick one or more responsibilities which include appropriate views for the employee. If the administrator who creates this user has a value in their New Responsibility field, then that responsibility is assigned to this user by default. For information about the New Responsibility field, see New Responsibility Field for User Record.
   New Responsibility	Optional. If the administrator who creates this user has a value in his or her New Responsibility field, then that responsibility is assigned to this field by default. For information about the New Responsibility field, see New Responsibility Field for User Record.
   Position	Required. To be an employee, a user must have a position. If you assign multiple positions, the position you specify as Primary is the position the user assumes when he or she logs in.
   Division	Required. This field is populated automatically with the division to which the Primary position belongs.
   Territory	This field is a read-only multi-value group. You are not able to enter a value manually. When you complete the Position field, the Territory field is populated automatically with territories with which the position is associated. (This field appears on the More Info form.)
   Organization	This field value is inherited from the user who creates this user, but the field is editable. Users whose positions are in this organization have access to this employee record. (This field appears on the More Info form.) For information about organization access control, see Configuring Access Control.

Completing Employee Setup

You can set up employees either before or after you assign them a responsibility. For more information about completing employee setup, see the initial setup section of Applications Administration Guide.

Also see Siebel Assignment Manager Administration Guide and Siebel Professional Services Automation User Guide.

Deactivating an Employee

You can deactivate an employee by dissociating the employee record from its responsibilities, altering the user ID, and removing the employee's access to the database.

To deactivate an employee

1. From the application-level menu, choose Navigate > Site Map > Administration - User > Employees.

   The Employees view appears.

2. In the Employees list, select the employee you want to deactivate.
3. In the More Info view tab, delete all records from the Responsibility field.
4. Change the user ID slightly, to indicate that the employee is no longer current.

   You may want to establish a convention for renaming user IDs when you deactivate employees. One possible convention is to append some text such as "expired" to the user ID. For example, you might change CARD to CARD-expired. That way you can continue to see the person's name associated with previous activity in history records.

5. Remove the employee's access to the database.

   If you implemented database user authentication, you should remove the user's database account. If you implemented external authentication, then delete the user from the directory from which the user's database credentials are retrieved.

   NOTE:  In the case of external authentication, if the external user directory (such as LDAP or ADSI) is shared by many applications, do not delete the user from the directory. Make sure that the user's database access user name and password are different from that user's directory user name and password. Otherwise the user might be able to access the database directly using some database connection tools.