What are the acceptable values for default user data fields?

Platform User Data Field

Acceptable CSV Values for the Field and Examples

Notes about Field

Username

String or numeric (Example: john.smith)

This field and the User ID or UUID fields cannot be in the same CSV, or you will receive an importing error.

You can use this field to change the usernames of user profiles via CSV. See more information in the New Username row of this table.

This field is not case-sensitive.

First Name

String (Example: John)

Last Name

String (Example: Smith)

Email

Most valid email addresses are accepted.

(Example: john.smith@example.com)

45-character limit preceding the ‘@’ character

45-character limit following the ‘@’ character.

Level

user

poweruser

superadmin

“user” = the user account will be a User.

“poweruser” = the user account will be a Power User.

“superadmin” = the user account will be a Superadmin.

This field is not case-sensitive.

Profile Name

Names of existing Power User profiles, as a string.

Profile names must be separated by the | character (pipe, or, vertical bar). When assigning multiple profiles to a Power User, do not use | as the separator in the CSV file. You can assign up to 10 profiles per Power User.

Branch Name

Name of an existing branch as a string.

Please note that you cannot add a user to more than one branch during this type of import.

This field is case-sensitive.

Branch Code

Code of an existing branch as a string.

Please note that you cannot add a user to more than one branch during this type of import.

This field is case-sensitive.

Branch Name Path

Example: “Root/ParentBranch1/ChildBranch1”

This represents the full path of branches where the user needs to be placed; any non-existing branch will be created automatically. The full path must be specified also when creating a sub-branch of an existing branch (which is not the root branch).

Note that when this field is specified, the “Branch Code Path” field must be specified along with branch codes matching the specified names.

This field is case-sensitive.

Branch Code Path

Example: “R/PB1/CB2”

This represents the full path of Branches where the user needs to be placed; any non-existing Branch will be created automatically. The full path must be specified also when creating a sub-branch of an existing branch (which is not the root branch).

Note that when this field is specified, the “Branch Name Path” must be specified as well with Branch names matching the codes specified.

This field is case-sensitive.

Password

String

(Example: aptSvvTrWlY452L6)

Passwords specified here must match the complexity criteria specified in the Advanced Settings area of the platform.

A password is auto-generated when a user is created without a password.

This field and the Hashed Password field cannot be in the same CSV, or you will receive an importing error.

Hashed Password

String

The password must be pre-encrypted using the Blowfish algorithm with 13 passes. 

This field and the Password field cannot be in the same CSV, or you will receive an importing error.

Active

0/1

no/yes

false/true

User will be Active = 1, yes, true

User will be Inactive = 0, no, false

This field is not case-sensitive.

Force Password Change

0/1

no/yes

false/true

Force the user to change the password upon the next login = 1, yes, true

Do not force the user to change the password upon the next login = 0, no, false

Expire On

YYYY-MM-DD

DD-MM-YYYY

MM/DD/YYYY

YYYY/MM/DD

Language

Example: English
Full list of ISO language codes

Must match how the language name is written in the platform. Find the full list in the Advanced Settings area or in your Localization Tool (in the Code column). 

Please note that if you try to create a user with a language that is not active in your platform, you will get an error. 

This field is case-sensitive and the text must be lowercase. 

Date Format

en

it

es

YYYY/MM/DD

This field uses ISO Language codes as acceptable values. The date format will correspond to that language's standard format. Full list of ISO language codes.

Timezone

Region/Local

Must match how the timezone name is written (just the name without GMT + XX:XX) in the platform. Find the full list in the Advanced Settings area in the Date and Time tab. For example, Jerusalem should be written as "Asia/Jerusalem", while Prague should be input as "Europe/Prague"

This field is not case-sensitive.

New Username

String or numeric (Example: john.smith)

You can use this field to change the usernames of the user profiles via CSV. Map the column in your CSV with the current usernames that you want to change to the Username or User ID Docebo field, and map the column in your CSV with the new usernames to the New Username Docebo field.

This field is not case-sensitive.

User ID

Numeric

This field is the internal user identifier in a specific platform database (not displayed anywhere in the user interface); it is determined by the platform and cannot be edited or removed.

This field and the Username or UUID fields cannot be in the same CSV, or you will receive an importing error.

You can use this field to change the usernames of the user profiles via CSV. See more information in the New Username row of this spreadsheet.

Is Manager

no/yes

When this field is set to Yes, the user is created as a manager, and can manage team members. 

UUID

Numeric

This is the unique user identifier assigned by Docebo to the user; it is determined by the platform and cannot be edited or removed.

This field and the Username or User ID  fields cannot be in the same CSV, or you will receive an importing error.

You can use this field to change the usernames of the user profiles via CSV. See more information in the New Username row of this spreadsheet.

Type of Manager

Username of the manager associated with the user

The name of this field is the description of the type of manager, as defined in the platform (for example, Functional Manager). You can add more than one manager type (thus, more than one column), depending on the hierarchy defined in the platform, in the Manage Manager Types section.