Administrative Utilities → About User Import → Importing Users From a Spreadsheet
Use the Import Users feature to import new users and update existing user accounts from a spreadsheet. Spreadsheets should contain basic information for each user, such as login ID, name, and e-mail address. You then specify a template user that provides role assignments, group membership, privileges, preferences, and more for imported users.
Spreadsheets can come from external tools, such as an Active Directory store or other Lightweight Directory Access Protocol (LDAP) providers, or you can manually create a spreadsheet. For details, refer to Preparing a Spreadsheet for Importing Users.
Consider the following before you import users:
Managed administrators must be granted the privileges in the following table before they can import or update user accounts. In addition, administrators can never update their own user records through the import process.
|Add Users||Administration - System page||Grant to enable the Import Users feature.|
|Edit Users||Administration - System page||Grant to enable administrators to update user accounts. These users must be members of groups that the administrator has privileges to manage. In addition, template users must be members of a group a managed administrator can manage.|
|Submit||Users - Table page||Grant this privilege for the Contacts table to enable administrators to add new Contacts records when they import user records.|
|Update||Users - Table page||Grant this privilege for the Contacts table to enable administrators to add new Contacts records when they import user records.|
Here is an example of a simple spreadsheet used to import users:
In this example, row 1 defines the columns to be mapped. This information is not imported. Row 2 is used as sample data, but the user is imported.
The following table explains how data in the User Attributes columns is mapped to SBM user, resource, and Contacts records.
|User Attribute||User Mapping||Contact Mapping|
|Login ID||Required. For on-demand customers, the login ID must be an e-mail address.||N/A|
|Name||Added to the Name field for the user record.||Added to the User Name field. Also parsed to First Name, Middle Name, and Last Name fields. For example, if the Name row in the spreadsheet is John Q. Smith, the name is parsed across the three fields in the Contacts record.|
|Required. Added to the E-mail field.||Added to the E-mail Address field, if available.|
|Telephone||Added to the Telephone field.||Added to the Phone Number field, if available.|
|Mobile Number||Added to the Mobile Phone field.||Added to the Mobile Number field, if available.|
|Title||Added to the Title field.||N/A|
|Resource Attribute||User Mapping||Resource Mapping|
|Business Unit||N/A||Added to the Business Unit field.|
|Department||N/A||Added to the Department field.|
|Description||N/A||Added to the Description field.|
|Employee ID||N/A||Added to the Employee ID field.|
|End Date||N/A||Added to the End Date field.|
|Job Function||N/A||Added to the Job Function field.|
|Location||N/A||Added to the Location field.|
|Manager||N/A||Added to the Manager field.|
|Skills||N/A||Multiple columns with the same name can be mapped to the Resource: Skills attribute.|
|Start Date||N/A||Added to the Start Date field.|
|Teams||N/A||Multiple columns with the same name can be mapped to the Resource: Teams attribute.|
|Title Group||N/A||Added to the Title Group field.|
|Type||N/A||Added to the Type field.|
|Contact Attribute||User Mapping||Contact Mapping|
|Company||N/A||Added to the Company if the value in the spreadsheet is an active value in the Companies table (on-premise only).|
|Address 1||N/A||Added to the Address 1 field, if available.|
|Address 2||N/A||Added to the Address 2 field, if available.|
|City||N/A||Added to the City field, if available.|
|State||N/A||Added to the State field, if available.|
|Country||N/A||Added to the Country field, if available.|
|Zip Code||N/A||Added to the Zip Code field, if available.|
|Fax Number||N/A||Added to the Fax Number field, if available.|
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.