> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/administration/import-collaborateurs.md).

# How do I import collaborators in bulk?

### Introduction

The import feature makes it possible to add or sync collaborators in bulk from a file, without having to add them one by one.

### How it works

#### Step 1 — Processing history

From collaborator Administration, go to the page **Import** which lists the history of previous synchronizations.

#### Step 2 — Choose the import type

Select the operation type: **add**, **deletion** or **mirror synchronization**.

#### Step 3 — Upload the file

Upload the Excel or CSV file containing the collaborators.

#### Step 4 — Review the alerts

The system analyzes the file and displays a report of '**alerts** on the anomalies detected (invalid rows, missing fields, etc.).

#### Step 5 — Review the analysis

A report of '**analysis** details the operations that will be carried out (creations, updates, deletions).

#### Step 6 — Start execution

Validate to start the **runner** which applies the operations. The status is updated live.

#### Operation types

* **Add** (upsert): create new collaborators or update existing ones
* **Deletion** (delete): remove collaborators
* **Mirror synchronization** (mirror): replace the entire list — collaborators absent from the file are removed

#### Test mode (dry run)

It is possible to run a simulation before actually executing the changes. Test mode displays a report of the planned operations without applying them.

The simulation becomes **required** for a file that assigns or modifies a login identifier: this is the only place where you can see, before execution, how many email addresses cease to be identifiers.

#### Collaborators without an email address

The template includes a column **Username** and a column **TV PIN code**, alongside the column **Email**. They make it possible to import collaborators who do not have a professional email address.

* Each row must have at least one identifier: an email address or a login identifier.
* A row that assigns a login identifier without an email address must include a 4-digit code, otherwise the collaborator would have no way to activate their account.
* The same identifier cannot appear twice in the file.

Rows that do not comply with these rules are flagged in the alerts report, before any writing: the file is not executed until they have been corrected. See [How do you add a collaborator without an email address?](/en/administration/collaborateur-sans-email.md).

#### Message tracking

Each synchronization operation generates tracking messages indicating the result for each collaborator (success, error, etc.).

### Alternative: SCIM provisioning

For automatic and continuous synchronization with an enterprise Directory (Azure Active Directory, Okta, etc.), see the article "Automatic collaborator provisioning (Provisioning / SCIM)".

### What the assistant can do

The assistant cannot launch a bulk import. It can explain how it works and guide you to the Administration interface. With the Administration scope, the assistant can add collaborators one by one.