⚙️ Introduction

This job is designed to create and update Customer Users by connecting your system to DJUST via SFTP.

You can:

Create and update Customer Users
Assign users to one or more Accounts and Organisations
Manage user groups, permissions, and active status
Delete users from the platform

📂 Import model

CSV Structure

The CSV file must contain one row per Customer User.

📄
Template
You can use the following spreadsheet as a template to structure your import:
Customer Users - Template

📋 Fields

Field	Definition	Values available	Required for creation	Required for update	Editable	Default Value
`Customer User External Id`	Unique external identifier for the Customer User.		✅	✅
`Customer User Civility`	Civility / title of the user.	`MR` / `MRS` / `MISS`	✅	✅	✅
`Customer User First Name`	First name of the user.		✅	✅	✅
`Customer User Last Name`	Last name of the user.		✅	✅	✅
`Customer User Email`	Email address of the user. Used as login identifier.	Valid email format	✅	✅	✅
`Customer User Phone`	Phone number of the user.		✅	✅	✅
`Customer User Groups`	Permission group(s) assigned to the user. Use `\|\|` to assign multiple groups.	`FOC_Admin` / `FOC_User` / `FOC_Webmaster`	✅	✅	✅
`Customer User Account Ids`	External Id(s) of the Account(s) the user belongs to. Use `\|\|` to assign multiple accounts.	Format: `ACCOUNT1\|\|ACCOUNT2`	✅	✅	✅
`Customer User Organisation Ids`	External Id(s) of the Organisation(s) the user has access to. Use `\|\|` to assign multiple organisations.	Format: `ORG1\|\|ORG2`			✅
`Customer User Main Organisation Id`	External Id of the user's main organisation. Must be one of the values listed in `Customer User Organisation Ids`.		☑️ (Required if `Customer User Organisation Ids` is provided)	☑️ (Required if `Customer User Organisation Ids` is provided)	✅
`Customer User Password`	User's password. If empty on creation, a password is auto-generated and sent to the user. If empty on update, the existing password is preserved.	8–255 characters, at least one lowercase letter, one uppercase letter, one digit, and one non-whitespace character.			✅	Auto-generated
`Customer User Inactive`	Marks the user as inactive (cannot log in) without deleting the account.	`TRUE` / `FALSE`			✅	FALSE
`Customer User Delete`	Permanently deletes the user from DJUST and the identity provider.	`TRUE` / `FALSE`			✅	FALSE
`Customer User Store Ids`	External Id(s) of the Store(s) the user is attached to. Use `\|\|` to assign multiple stores. Ignored if at least one store is selected in the job configuration.	Format: `store1\|\|store2`	☑️ (Required in multi-store context and if no store is selected in the job configuration)	☑️ (Required in multi-store context and if no store is selected in the job configuration)	✅
`CF_customFieldExternalId`	Custom field value. Column name must follow the `CF_camelCaseName` convention.	Depending on the custom field type			✅

☑️
Conditionally required

⚠️
Required Custom Fields
Any custom fields configured as required in DJUST must also be included.

🧠 Key Business Rules

Identification & uniqueness

Customer User External Id must be unique across all Customer Users in DJUST.
Customer User Email is used as the login identifier and must be unique.

Accounts & Organisations

A user can belong to multiple Accounts (use || as separator).
Customer User Main Organisation Id, when provided, must be one of the values in Customer User Organisation Ids.

Password handling

On creation: if Customer User Password is left empty, DJUST auto-generates a password.
On update: if Customer User Password is left empty, the existing password is preserved (not modified).
Policy: 8–255 characters, at least one lowercase letter, one uppercase letter, one digit, and one non-whitespace character.

Activation & deletion

Customer User Inactive = TRUE disables login but preserves the user record and its associations. Set to FALSE to reactivate.
Customer User Delete = TRUE permanently deletes the user.

Multi-store

In a multi-store context, the Stores associated with each Customer User can be defined in two ways — the job configuration takes precedence over the CSV column:
- No store selected in the job configuration (default): the Customer User Store Ids column from the CSV is used. Use || to assign multiple stores (e.g. store1||store2).
- At least one store selected in the job configuration: every Customer User imported is associated with the stores defined in the job configuration. The Customer User Store Ids column from the CSV is ignored (no error is raised on its values). Mono-store tenants are not affected by this behavior.

📌
Best Practices
✔️ Validate that all referenced Account, Organisation, and Store External Ids exist in DJUST before running the import.
✔️ Use a consistent and stable Customer User External Id strategy — it is the key used to match existing users for updates.
✔️ Map required Custom Fields before running the import.