Documentation/
Démarrer

Import your employees

Add employees to Gensy from a CSV file, by hand, from your Microsoft 365 directory, or by pasting text such as a signature.

The Import ▾ menu on the Employees page offers three sources; New employee creates a profile by hand. On the Free plan, the only slot is your own profile: importing other employees requires a paid plan.

CSV file

  1. File — drag and drop the CSV. The CSV template (Fields → ··· → Export CSV Template) already has the right columns; replace its example row, or it will be imported as an employee.
  2. Mapping — link each column to a field. At least one column must match the email. A column can also specify the template to assign.
  3. Validation — valid rows and errors: empty or invalid email, empty row. The “skip invalid rows” option imports the rest; an unknown template imports the row without a template. Addresses already in Gensy and duplicates within the file are skipped by default (“Import these rows too” box). An import that would exceed your plan’s employee limit is refused as a whole.
  4. Done.

Microsoft 365

Choose the Microsoft 365 source and connect the account: a tenant admin must consent to the User.Read.All permission (reading the directory). From the Starter plan up; owner and admins only. Load the users, map their fields to yours, then import. Disabled accounts, addresses already in Gensy, external guests and accounts without a mailbox are skipped; add shared mailboxes by hand. Disconnect (owner only) removes the connection.

Paste a text

Paste a signature, a business card or an email: AI fills in the fields, you check the values, then click Create employee (one profile per analysis, without the photo). 3 credits per analysis, from the Starter plan up.

Duplicates

Imports skip, by default, addresses already in Gensy and duplicates within the file (“Import these rows too” box); adding by hand, Paste a text and Duplicate don’t check. At deployment, an address carried by several profiles with a template or department shows Duplicate (Manual): it is never deployed automatically, to avoid overwriting the wrong signature.

The employee profile

Each profile holds the organization’s fields, a department and a template. The photo is an Image (URL) field, uploaded from the profile (2 MB maximum): without such a field, there is no photo. The Email aliases (Outlook) field lists the other addresses — UPN, former addresses — under which the Outlook add-in will recognize the person.

After the import

  • Bulk actions — select several rows to assign a department or template, duplicate or delete (bulk deletion is reserved for the owner and admins).
  • Clean up data — in the ··· menu: capitalization, North American phone numbers, emails and spaces fixed without using credits. From the Starter plan up.
  • Employee portal — let everyone complete their own profile and photo.
  • Export CSV — the profiles matching the current search and filters, one column per field (no department or template).

Watch out

Changing a deployed employee’s template or department unpublishes their signature (redeploy it afterwards); Gensy asks for confirmation. Deleting a profile unpublishes nothing: with Gmail, the signature stays in the mailbox, so unpublish it first in Deployment; with the Outlook add-in, it stops being inserted.

Need help?

Support answers from within the app, with your workspace already in context.

Open support
Open support

Free to start.
Pay as your team grows.

© 2026 GENSY.EMAIL (Agence Hélium Inc.)
All rights reserved.

Privacy policy
(website)
Have a web or app project?
Hire the team behind gensy.email