CSV Manual Bulk Upload User Provisioning, Syncing and Deprovisioning

This article shows App managers how to provision and deprovision user data from their HRIS system using a CSV file. CSV template for provisioning, syncing, and deprovisioning with all the necessary columns, are attached to the bottom of this article, as well as in the application under Example CSV (see screenshots below). When provisioning or syncing in Simpplr, App managers will select which columns they want to map from the CSV, and ensure the columns they want to map contain the appropriate data. 

 

For automated user provisioning via CSV on an SFTP location, check out this article.

Set up CSV user provisioning/deprovisioning

Back to top

To add or remove users in bulk using a CSV file:

  1. Go to Manage > Users > Add or remove.
    AWS_manage_users_1.gif
  2. Here you can upload a CSV file from your computer, or use the sample CSV Simpplr provides by clicking Example CSV. This will guarantee all the proper fields are included. 
  3. Using the CSV template, populate your people data for your users. Adding and removing users both require adding the user attributes to the CSV file. Note, letter case value must match exactly for every field value.
  4. Select which fields you want to add or remove. First name, last name, email address (or at least one other login identifier) and role name are all required. The role name field must match an existing role already created in the platform, such as Application Manager or End User.
    AWS_manage_suers_2.png
  5. Select the default language, locale, timezone, and profile for all users. If you'd like to have a different language, locale, timezone, or profile for a specific user, you can input that data in the corresponding column of the CSV.
  6. Once you save and upload your CSV file, choose to add a brief file description to clarify what your file contains if you'd like.
  7. Select Add or Remove users. This will determine whether or not you're provisioning or deprovisioning users.
    AWS_CSV_upload_users.png

Adding and syncing users

  1. If adding users, additional details are required to fill out. First, Simpplr requires you enter Login identifier fields. This allows non-SSO users to access your environment via one or more login identifiers. Select which field matches the data in the CSV. This is only for non-SSO users, which may or may not be applicable to your org. 
  2. When complete, scroll down and select which User attributes match the data in the CSV. For example, First name should match the first_name value in the CSV (or whatever you labeled that value). First and last name are required here, but you can add as many attributes as you'd like.
  3. If your CSV data contains existing users whom you're updating attributes for, select Update attributes. If not, select do not update attributes.
  4. Finally, choose to send a welcome message to your new users. This message will be sent to all new users via text and email. The message is not customizable.

Removing users

  1. If removing users, upload the CSV file containing data for all the users you'd lime to remove, then select Remove
  2. After this step, we only need to match the CSV fields for the required non-SSO login identifier fields. This may or may not be applicable to your organization. When finished, click Remove users.

Reactivating users

Reactivation of users is also supported. In case you need to reactivate a suspended or deactivated user, use the same provisioning.csv file you used to provision users. To reactivate, simply:

  1. Provide the old username, profile and email in the CSV. 

  2. In the user status section where a user is marked 'Inactive', change it to 'Active'.
  3. Upload the same way as instructed above.
  4. Once the file is processed successfully, inactive users are moved to Active status.

  5. In case of any failure, the admin will receive the error email with the failure reasons (more on this below).

Please note that reactivation only means changing the status from 'Inactive' to 'Active' while retaining the old user data. If any user data need to be updated, it needs to be done through the syncing process.

Prepare your CSV file

Back to top

The CSV files for provisioning should contain a number of columns that can be mapped with Simpplr. During provisioning and syncing setup, App managers will select which columns they want to map (some columns are required). 

Provisioning

You can download the CSV template for provisioning in the section below, which contains the following columns:

  • First Name (required)
  • Last Name (required)
  • Email Address
  • Employee Number
  • Mobile
  • Phone
  • Timezone
  • Language
  • Locale
  • Address Line 1
  • Address Line 2
  • City
  • State
  • Country
  • Postal code
  • Job Title
  • Department
  • Division
  • Start Date (must be written in the format 'YYYY-MM-DD')
  • Role Name (required) (This must match an already created role in the Manage roles menu)
  • Birthday
  • Additional Columns 1 & 2
  1. Name the CSV file you're provisioning from user-provisioning.csv.
  2. Populate the columns you want to map.

Locale fields

Note that if/when assigning locales to users, you must enter the corresponding value form the list below with the locale you want to use. DO NOT enter the locale, enter the country value. The country must match exactly as in the list below.
AWS_locale_values.png

Error handling

Back to top

When the bulk upload process is complete, the App manager will receive an in-app notification for the completed bulk upload as well as an email stating the error. To see if there are any errors in-app, click the notification to get to the Bulk upload history, then download the completed file. There are two new columns in the file, Status and Reason. If there are errors, the Status column will reflect where the error was, and the Reason column will explain the reason for the failure.CSV

 

Link to template

Back to top

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

See more