Collabin can import new employees from CSV or XLSX, assign them to existing teams and record allowances for a selected year. An Admin runs the import. Preview validates the data before saving, and the final import can proceed only when every row is valid.
What does the import include?
The import creates new accounts; it does not overwrite existing users in your organization. Importing employees and allowances does not import historical leave requests or attendance records. Plan how to reconcile those separately, especially when moving from Excel partway through the year.
A file can contain up to 2 MB, 1000 data rows and 100 columns. For XLSX, Collabin reads the first worksheet. Save older .xls files as XLSX or UTF-8 CSV first.
1. Prepare teams and leave types
Create the required teams and active leave types before importing. Unknown teams or leave types are not created by the import. Check that the added employees fit within your plan's user limit.
Open the import dialog on the Members page and download the template. Its allowance columns use your organization's leave-type names. The leave-type guide explains how to prepare those types.
2. Fill in the file
| Column | Meaning | Example |
|---|---|---|
email | Required, unique email address | anna@example.com |
full_name | Required full name | Anna Example |
role | Role; blank defaults to employee | EMPLOYEE |
teams | Existing teams separated by a vertical bar | Support|Sales |
allowance:Vacation | Allowance for that leave type | 25 |
carried_over:Vacation | Days brought forward from the previous year | 2 |
Use the exact type name from your downloaded template after the colon. Keep the role values ADMIN, MANAGER and EMPLOYEE untranslated; grant administrator access only when needed.
Copyable example, assuming both teams and the Vacation type exist:
email,full_name,role,teams,allowance:Vacation,carried_over:Vacation
anna@example.com,Anna Example,EMPLOYEE,Support|Sales,25,2
The annual allowance of 25 and the 2 carried-over days are separate values. This row does not import days already taken. For monthly or weekly types, the allowance is per period and carryover must be zero.
3. Review the preview
Select the file and allowance year, then run the preview. It does not create accounts or send invitations. Check names, roles, teams and allowances. Read warnings about unknown columns as well: their contents are ignored.
| Problem | Action |
|---|---|
| Duplicate or existing email | Resolve duplicates; edit existing accounts separately. |
| Unknown team | Create it first or correct the name. |
| Unknown or inactive type | Use an active type's exact name in the header. |
| User limit exceeded | Check the subscription and number of new employees. |
If there is an error, valid rows are not partially imported. Correct the file and generate a new preview.
4. Confirm and verify
Finalizing saves the accounts and allowances together, then sends invitations. Review the Members list and spot-check a few allowances. If an invitation does not arrive, resend it for the existing account; importing the same file again is not an invitation-resend mechanism.
Frequently asked questions
Can I update existing employees with the file?
No. An email address already present in your organization produces an error. Use the relevant account and allowance editors for existing employees.
When are invitations sent?
After a successful final import, not during preview.
For the wider transition, read moving away from Excel. To try Collabin, register here.