The following are the headings that must appear in the header row. For all data files, you must include all fields, in the order indicated in this list. Data must exist for the USERNAME through LASTNAME fields, but MINIT, EMAIL, and NTINTEGRATED fields can be empty. Field order is not important when using a database connection because the system orders the fields appropriately.
USERNAME: Corresponds to the Username field.
PASSWORD: Corresponds to the Password field.
FIRSTNAME: Corresponds to the First Name field.
LASTNAME: Corresponds to the Last Name field.
MINIT: Corresponds to the Middle Initial field.
EMAIL: Corresponds to the E-mail field.
NTINTEGRATED: Corresponds to the NT Integrated option.
You can also include optional fields in the file, if desired. If used, these fields must appear in the order specified in the list below and they must appear after the required fields.
USERGROUP: Should reflect the name of all user groups in which a user is to be enrolled. User groups do not have to exist in the database prior to running the User Import Utility. If the user group does not exist on the server, it is created. After importing the data, view the User groups page to see that the new user group was created.
STARTDATE: Corresponds to the Start Date field. Dates can be typed in any format and are converted to the m/d/yy format.
ENDDATE: Corresponds to the End Date field. Dates can be typed in any format and are converted to the m/d/yy format.
Custom User Fields: Custom user fields must exist in the Knowledge Center database; otherwise, they are ignored during the import process. In addition, if a custom user field is required and no value exists in the field for a particular user, an account is not created in the Knowledge Center for that user and an error is generated in the log.
For text or Excel files, the name in the header row must be identical to the custom field name in the database. Type the field name in capital letters and if the name includes multiple words (for example, Sales Territory), include the appropriate spaces in the header row. In addition, the data in the data file must be of the same type as the custom user field in Manager (for example, text should be in the data column for a text custom user field, date/time in the data column for a date/time custom user field, and so on.).
To specify values for Boolean custom user fields, use 0 to indicate “false” and 1 to indicate “true.” To specify multiple values for a data field (for example, an Unordered List custom user field or multiple user groups to which one user belongs), separate each value with a comma.
Note: The option to set NT integration is read from the login address. If that address is entered via NT integration, then all addresses are set to require NT authentication.