> 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 employees in bulk?

### Overview

The import feature lets you add or synchronize 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**, **delete** 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 an**alerts** report about the detected anomalies (invalid rows, missing fields, etc.).

#### Step 5 — Check the analysis

An**analysis** report details the operations that will be performed (creations, updates, deletions).

#### Step 6 — Start execution

Confirm to launch the **runner** which applies the operations. The status is updated live.

#### Types of operations

* **Add** (upsert): create new collaborators or update existing ones
* **Delete** (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 ID: this is the only place where you can see, before execution, how many email addresses stop being identifiers.

#### Collaborators without email address

The template includes a column **Username** and a column **TV PIN code**, alongside the column **Email**. They allow collaborators without a work email address to be imported.

* Each row must include at least one identifier: an email address or a login ID.
* A row that assigns a login ID 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 meet these rules are flagged in the alerts report, before any writing takes place: the file is not executed until they have been corrected. See [How do I 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, continuous synchronization with a corporate 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.