Using CSV user import
Overview
You can upload user information using CSV file. Click on the Browse button to locate the CSV file on your hard disk, then press the Upload button.
You can export these files from Excel, or create them manually by following the rules below:
- Each record must be on a separate line
- The fields must be separated by commas or semicolons (the appropriate option has to be selected on the upload page)
- If you cannot add a field, leave it empty (do not skip fields at the end of the row, leave them empty e.g. ;;; )
- If you need comma or semicolon or newline character in a field, you have to surround the entire field with quotation marks ("this is a field, with a comma")
- If you need quotation mark in a field, you have to insert double quotation marks instead of one and you also have to surround the entire field with quotation marks ("this is a field with ""quotations" ")
- The system automatically trims spaces from the beginning and the end of the field
- You can leave the header row in the CSV file, but on the upload page, you have to check the Skip First Row (Heading) option
The CSV file must be UTF-8 encoded, otherwise, names with local characters might get corrupted.
After uploading the file you will see the contents of the file in a table format and you can make changes to the values before executing the import.
List of columns in the CSV file
The following table describes the required fields in the CSV file:
You can download sample CSV file by clicking on the Download Sample XLS File link on the top right corner.
Column | Column Name | Description | Value requirements/rules |
|---|---|---|---|
1 | User name | Full name of the user, e.g. used in searches. | Required |
2 | Login ID | Login name of the user. | Required |
3 | Language | The language of the user interface. | The following valid values apply: |
4 | E-mail address | Email address of the user used to send requested call information to the user. | Maximum length: 128 |
5 | Valid From yyyy.mm.dd | First date when the user can log in. By default, the user cannot see conversations for associated extensions before this date. | The following date formats can be used: If the field is empty, current datee is used. |
6 | Phone Mapping | List of phone numbers / Extensions associated with the user. | Semicolon separatedlist of one phone numbers or URIs (e.g. SIP address) |
7 | Password (MD5 Hash) | MD5 hash of the user's password. | If empty, the login name is used as password |
8 | Change Password at Next Login | Forces users to change their password when they next log in to the system. | 1 - password must be changed |
| 9 | Groups | List of Groups where the user is a member. | Semicolon-separated list of Group names If a Group does not exist it is created |
| 10 | Role API Names | List of Roles associated with the user. | Newline (Alt + Enter in Excel) separated list of Role names. E.g.: r_system_supervisor |
| 11 | Recording Mode | Defines how the phone numbers listed in the Phone Mapping field should be recorded. | full - records in always-on mode on-demand - records on-demand manual - records controlled no - do not record |
| 12 | Time Zone | Time Zone of the user (e.g. used for displaying time in searches) | Time Zone ID. You can find the timezone IDs on the web interface under Administrator / User on any user configuration page. Use the ID in the second half of the timezone you see in the drop-down list. E.g. if you see "GMT+01:00 - Europe/Stockholm" to Time Zone ID to be used in this field is "Europe/Stockholm". |
| 13 | CRM User ID | Customer Relationship Management user Identity Number. | Optional |
| 14 | Modalities | Defines the recorded modality for the extension. Only the configured modalities will be recorded for the extension. | The following valid values apply: file_share |
| 15 | Directions | Defines the recorded directions for the extension. Only the configured directions will be recorded for the extension. | The following valid values apply: all |
| 16 | custom0 | Custom user fields. For more information visit this page. | Optional |
| 17 | custom1 | ||
| 18 | custom2 | ||
| 19 | custom3 | ||
| 20 | custom4 | ||
| 21 | custom5 | ||
| 22 | custom6 | ||
| 23 | custom7 | ||
| 24 | custom8 | ||
| 25 | custom9 | ||
| 26 | Play Notification for PSTN/Federated Inbound Calls (SfB/Lync) | Play Audio Notification for PSTN Inbound Calls. | 1 - enabled 0 - disabled |
| 27 | Play Notification for Conference Calls (SfB/Lync) | Play Audio Notification for Conference Calls. | 1 - enabled 0 - disabled |
| 28 | Audio Notification File for PSTN/Federated Inbound Calls (SfB/Lync) | Audio Notification File for PSTN Inbound Calls. | E.g.: This_Call_Is_Being_Recorded.wma |
| 29 | Audio Notification File for Conference Calls (SfB/Lync) | Audio Notification File for Conference Calls. | E.g.: This_Meeting_Is_Being_Recorded.wma |
| 30 | Music On Hold File for PSTN/Federated Outbound Calls (SfB/Lync | ||
| 31 | IM Notification for Conference Calls (SfB/Lync) | IM Notification for Conference Calls. | E.g.: This meeting is being recorded. |
| 32 | Play Notification for PSTN/Federated Outbound Calls (SfB/Lync) | 1 - enabled 0 - disabled | |
| 33 | Audio Notification File for PSTN/Federated Outbound Calls (SfB/Lync) | ||
| 34 | Play Notification for Inbound Calls (Cisco) |
| 1 - enabled 0 - disabled |
| 35 | Media Resource ID for Inbound Calls (Cisco | ||
| 36 | Retention Period (days) | ||
| 37 | Automatically Delete Conversations after the Retention Period is Over | ||
| 38 | Observer User ID | ||
| 39 | Observer Group ID | ||
| 40 | Play Notification for Outbound Calls (Cisco) | ||
| 41 | Media Resource ID for Outbound Calls (Cisco) | ||
| 42 | Location | ||
| 43 | Record Calls Answered by 3rd Party | ||
| 44 | Recorded Platforms | ||
| 45 | Import Sources | ||
| 46 | Recording Rule ID |