Users (Full Update)
Description
Upsert User Resource
See the Aerial Spec for more details.
File Naming Convention
TGEN_users_fullupdate_2026-08_<optionalSuffix>.csv
importType:fullupdateapiVersion:2026-08
Columns
Nested object fields are flattened into columns using dot notation (parent.child). Array fields are flattened using zero-based index notation, one element per column (field[0], field[1], and so on).
Note: A whole array cannot be passed in a single column: a literal value such as ['value-1','value-2'] will be rejected. To import multiple array elements, add one indexed column per element. Rows in the table below with type array describe the field as a whole and are not valid CSV column headers.
| Column Header | Description | Key Information | Type | Required |
|---|---|---|---|---|
username | The username of the employee | string | Yes | |
password | For standard integrations, this field is used exclusively to set a temporary password during user creation; the password field is ignored when updating existing users. Unless configured otherwise, temporary passwords must be at least 12 characters long and must include one letter, one number, and one special character. Legacy configurations support ongoing (and non-temporary) password updates. | string | No | |
disabled | Boolean dictating if user is disabled (true or false) | boolean | No | |
employee | Unique Tulip identifier of the employee | Max Length: 36 | string | No |
roles | Array of role external ID’s | Not a CSV column header. Pass each array element in its own indexed column (roles[0], roles[1], and so on). | array | No |
roles[0] | Array element | string | No |
Sample CSV
See the following users CSV sample file.
Note: The sample CSV may contain sample ID fields which reference other resources that do not match the data in your environment.