Download a blank import template here: User Import CSV template. A link to the most current template is also available from the User Import page in the LMS by opening the online Help icon.
Important: All columns, column names, and column order must remain unchanged in the uploaded file regardless of whether they are being used or not. Any alteration will cause the import to fail. When you name your file, the filename must NOT contain any spaces or special characters (e.g. &, +, #, $…). The only special characters allowed are hyphens (-) and underscores (_).
PREPARE THE USER IMPORT FILE FOR NEW USERS
The CSV template file must be submitted in the standard template format. Entries on the template are mapped to corresponding fields on the user’s account and profile pages in the LMS.
New users created from the User Import process are assigned the default “Student” role and belong to a unique User Group created for the successful addition (incorporating date/time stamp information to ensure easy reference against the import). Because User Groups are integrated into user search/filter options across many areas of the LMS, this design should allow easy targeting of this specific user population for a general “Welcome!” announcement, batch enrollment in new employee orientation, etc. No automatic notifications are provided to the imported users. We recommend using the Announcement feature to notify users of their temporary passwords and their usernames, if a particular convention was used, such as the user’s email address.
Required Fields
Username: Must be unique across all LatitudeLearning® portals; email address can be used as a unique username. If a user record fails due to a duplicate username and you do not find that user in your LMS, it is a user in another LMS. If you are using import to update an existing user, this must match the current username exactly. This column maps to the Username field on the user account General Info page.
First Name: If it contains apostrophes (‘) or commas (,), the name must be nested between quotation marks (“), e.g. “La’rissa”. This column maps to the First Name field on the user account General Info page.
Last Name: If it contains apostrophes (‘) or commas (,), the name must be nested between quotation marks (“), e.g. “O’Neil” or “Jones, Jr.” This column maps to the Last Name field on the user account General Info page.
Effective Date: Enter the date the user account should become active in format mm/dd/yyyy. This may also be known as the user start or hire date. If this date is in the future, the user will remain inactive until this date matures. This column maps to the Effective Date field on the user account General Info page.
Primary Location Code: This must be a Location code, not the location name or description. It must be a location, not be a higher organization level like Division or Business Unit. Numbers with leading zeros must be nested between quotation marks (“), e.g. “005” or “01A2”. This column will become the organization shown on the user’s primary profile under the Profiles tab.
Primary Location Start Date: Enter the date the Primary Location Code should become active in format mm/dd/yyyy This column relates to the Primary Location code above and determines when the profile created at this location becomes active. For new users, this is normally the same as the overall Effective Date.
Primary Position Code: This must be a position code, not the position name or description. Entries with leading zeros or commas must be nested between quotation marks, e.g. “005” or “01A2”. This column maps to the user’s Profiles tab as the primary position at the related primary location.
Primary Position Effective Date: Enter the date the Primary Position Code should become active in format mm/dd/yyyy. This column relates to the Primary Position code above. For new users, this is normally the same as the overall Effective Date or the Primary Location Start Date.
Columns not listed above are optional.