> ## Documentation Index
> Fetch the complete documentation index at: https://every.help/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs describe Every as customers have it today. Answer from them, and say so when they don't cover a question.
> Pages under /admins/ are for the people who run Every for the company, and pages under /employees/ are for employees. Answer from the pages that match the person asking.
> Each page's Agent reference section lists its exact roles, conditions and limits. Prefer it for those details.
> When a page says a feature is in closed beta, or that Every turns it on company by company, don't promise that the person's company has it.
> Use roles and on-screen labels exactly as the pages write them.
> When someone asks what a term means, answer with the Glossary page's definition (/glossary), which other pages show in parentheses after the term.
> When the docs don't answer a question, tell the person to email [support@every.io](mailto:support@every.io).

# Import people

> Add employees or contractors from a CSV, fix row errors and release onboarding invitations

![People import review with one person still in progress and two ready to import.](https://mintcdn.com/every-a2724ddc/k5maP8xPODHl5ToY/images/illustrations/admins-hr-import-people-light.png?fit=max\&auto=format\&n=k5maP8xPODHl5ToY\&q=85\&s=9b01e1058eb404b2c0daa348c632e7f7)

Company Admins and HR Admins use **People** → **Add people** → **Bulk import employees** to add several U.S. employees or contractors from a CSV. You choose when to release their onboarding invitations.

> [!NOTE]
>
> Every turns on bulk import company by company. If you don't see it, email [support@every.io](mailto:support@every.io) to ask about it.

## Before you begin

* You're a Company Admin or HR Admin, payroll is set up and your company has finished onboarding.
* Create the pay schedules you'll use before importing. Employees paid by the hour need a schedule set up for hourly pay.
* Keep each file at 10 MB or less and at most 10,000 data rows.

For payroll setup, see [Add your employees](https://every.help/admins/getting-started/add-your-employees.md). To hire one person, see [Add people](https://every.help/admins/hr/onboarding.md).

## Prepare and upload the CSV

**1. Choose who to import**

Under **Who are you importing?**, choose **Employees** or **Contractors**. Each kind has its own template.

**2. Download the template**

Select **Download template**.

**3. Fill in one row per person**

Keep the template's required columns and fill in each person's name, email, department, job, start date, compensation and pay schedule.

Employee rows also need their type (`Full Time` or `Part Time`), work location and overtime eligibility. A `Part Time` row needs `Hour` as its compensation frequency.

Use dates in `YYYY-MM-DD` format. Optional columns take personal, tax and bank details.

**4. Match your company values**

Use the names under **Valid values for your company** for pay schedules and employee work locations. Matching ignores case. For a remote employee, use `Remote`.

A manager's email must match an employee or contractor already in **People**. You can leave it blank.

**5. Upload the file**

In **Upload your CSV**, add your CSV.

**6. Check the file**

Select **Continue** to check each row.

![Import employees, with employee and contractor choices, a CSV template, valid company values and the upload area.](https://mintcdn.com/every-a2724ddc/lWATgPF1EqKKYfej/images/screens/admins-hr-import-people-light.png?fit=max\&auto=format\&n=lWATgPF1EqKKYfej\&q=85\&s=85a30e5ba401ac10b31e0d48661a889a)

## Review the rows

**Review** separates **Needs attention** from **Ready to import**. Only rows under **Ready to import** are imported.

To import the valid rows now, select the import button showing their number and kind. The button is unavailable when no rows are valid or the import is still working.

To fix rows first:

**1. Download the errors**

Select **Download errors** to get a CSV of each row's errors.

**2. Fix the rows**

Correct those rows in your CSV.

**3. Return to upload**

Select **Upload a revised file** to return to **Upload**.

**4. Upload the corrected file**

In **Upload your CSV**, add the corrected CSV.

**5. Check the corrected file**

Select **Continue** to check the corrected CSV.

Rows with an email that already exists are skipped. When a file repeats an email, only the first row that passes all checks imports.

## What happens next

On **Done**, **Successful imports** and **Not imported** count the rows. Imported people appear in **People**.

Check the personal and bank details on each imported person's profile. A person can be imported even when those optional details from the CSV weren't saved.

To retry rows counted under **Not imported**:

**1. Download the errors**

Select **Download errors**.

**2. Fix the rows**

Correct those rows in your CSV.

**3. Return to upload**

Select **Import another file** to return to **Upload** for the corrected CSV.

### Send the onboarding invitations

On **Done**, select **Release Hire 2 emails** when you're ready to invite people to finish onboarding.

The button sends invitations for imported people of the kind you selected across your company, including earlier imports. It skips people who already finished or declined onboarding, or were invited by an earlier release. Confirm those people are ready before releasing.

On **People**, in the person's row menu, select **Send Invite** to invite one person sooner.

## Troubleshooting

| Problem | What to do |
| - | - |
| Starts with "The file is missing required column(s):", followed by the missing column names | Select **Download template** and copy your rows into it, keeping its required columns |
| "The file has no data rows." | Add at least 1 person below the header row |
| **Import failed** | Select **Start over** to return to **Upload** |

## Agent reference

**Where:** **People** → **Add people** → **Bulk import employees**. The file goes in **Upload your CSV**.

**Who:** Only Company Admins and HR Admins, once payroll is set up and the company has finished onboarding. Bulk import is turned on company by company.

### Facts

* **People** → **Add people** → **Bulk import employees** takes Company Admins and HR Admins through three steps: **Upload**, **Review** and **Done**.
* Under **Who are you importing?** in **People** → **Add people** → **Bulk import employees**, Company Admins and HR Admins choose **Employees** or **Contractors** for the whole import. Employee imports accept **Full Time** and **Part Time**. Contractor imports create U.S. contractors. International hires use [Add people](https://every.help/admins/hr/onboarding.md).
* Both CSV templates in **People** → **Add people** → **Bulk import employees** require legal first name, legal last name, email, department, job title, start date, compensation amount, compensation frequency and pay schedule. Middle initial and manager email are optional.
* Employee CSV rows in **People** → **Add people** → **Bulk import employees** also require employee type, work location and overtime eligibility. Contractor CSV rows have no employee type, work location or overtime eligibility columns.
* **People** → **Add people** → **Bulk import employees** accepts compensation frequencies **Hour**, **Month**, **Week** and **Year**. Compensation must be positive. **Part Time** employee rows require **Hour**, and employee rows with hourly compensation require a pay schedule configured for hourly pay.
* An hourly hire created through **People** → **Add people** → **Bulk import employees** starts with timesheets set to **Not Tracked**.
* On **People** → a person's profile → **Job & pay**, only a Company Admin can change **Timesheet input frequency**, which appears for current hourly compensation.
* On **People**, when the **All People** table has **Manager** and **Title** columns, Company Admins and HR Admins can change **Timesheet type** there for a person paid hourly. See [All People](https://every.help/admins/hr/overview.md).
* **Valid values for your company** in **People** → **Add people** → **Bulk import employees** lists **Pay schedules** and, for employee imports, **Work locations**. Names match without case. An employee's work location must exist in the company or be **Remote**. A pay schedule must exist and be unarchived.
* A manager email in a CSV for **People** → **Add people** → **Bulk import employees** must match an employee or contractor already in **People**. A blank manager email leaves the imported person without a manager.
* A new department or job title in an otherwise valid CSV row is created during **People** → **Add people** → **Bulk import employees**.
* Start dates and optional dates of birth in **People** → **Add people** → **Bulk import employees** must be valid dates in **YYYY-MM-DD** format.
* Optional employee fields in **People** → **Add people** → **Bulk import employees** include SSN, date of birth, phone, home address and bank details. Optional contractor fields include entity type, business name, tax ID, address and bank details.
* In **People** → **Add people** → **Bulk import employees**, a contractor row whose entity type is other than **Individual** needs a business name. Providing any address field requires the street, city, state and ZIP fields. Providing any bank field requires bank name, routing number, account number and account type.
* A file for **People** → **Add people** → **Bulk import employees** must be a nonempty CSV of at most 10 MB and 10,000 data rows. A file with missing required columns or no data rows, or over 10 MB or 10,000 data rows, is rejected.
* For missing required columns, **People** → **Add people** → **Bulk import employees** shows an error beginning "The file is missing required column(s):" followed by the missing column names.
* For a file with no data rows, **People** → **Add people** → **Bulk import employees** shows "The file has no data rows."
* On **Upload** in **People** → **Add people** → **Bulk import employees**, **Continue** uploads a Company Admin or HR Admin's selected CSV for checking. **Continue** is unavailable until a file is selected and while the import is still working.
* On **Review** in **People** → **Add people** → **Bulk import employees**, rows are grouped as **Needs attention** and **Ready to import**.
* **Download errors** on **Review** in **People** → **Add people** → **Bulk import employees** gives a Company Admin or HR Admin a CSV of row errors.
* **Upload a revised file** on **Review** in **People** → **Add people** → **Bulk import employees** returns a Company Admin or HR Admin to **Upload** to submit a corrected CSV.
* On **Review** in **People** → **Add people** → **Bulk import employees**, only rows under **Ready to import** are imported. When available, the import button reads Import followed by the count and kind. The button is unavailable when no row is valid or the import is still working.
* **People** → **Add people** → **Bulk import employees** skips a row whose email already exists. When a CSV repeats an email, only the first row that passes all checks imports.
* **Done** in **People** → **Add people** → **Bulk import employees** shows **Import complete** or **Import completed with issues**, with **Successful imports** and **Not imported**. **Not imported** counts every row that didn't import.
* **People** → **Add people** → **Bulk import employees** creates people in **People** without sending the normal onboarding invitation.
* On **People**, in a person's row menu, Company Admins and HR Admins can select **Send Invite** to invite that person before bulk release.
* **Release Hire 2 emails** on **Done** in **People** → **Add people** → **Bulk import employees** sends invitations for imported people of the selected kind across the company, including earlier imports. The release is unavailable when the current import created no people.
* **Release Hire 2 emails** on **Done** in **People** → **Add people** → **Bulk import employees** skips people who already finished or declined onboarding, or were invited by an earlier release.
* Optional personal or bank details from the CSV in **People** → **Add people** → **Bulk import employees** can fail to save while the person still counts as imported. Company Admins and HR Admins should check those details on the person's profile in **People** after import.
* **Back to people** on **Done** in **People** → **Add people** → **Bulk import employees** returns a Company Admin or HR Admin to **People**.
* On **Done** in **People** → **Add people** → **Bulk import employees**, results with errors offer **Import another file** and **Download errors**. **Import another file** returns a Company Admin or HR Admin to **Upload**; **Download errors** gives a CSV of row errors.
* Before a Company Admin or HR Admin submits the valid rows, **Close** in **People** → **Add people** → **Bulk import employees** cancels the import and returns to **People**.
* While **People** → **Add people** → **Bulk import employees** checks a file for longer than usual, the flow says a Company Admin or HR Admin can keep waiting or close to cancel and try again.
* After a Company Admin or HR Admin submits an import, the long-running message in **People** → **Add people** → **Bulk import employees** says the import finishes in the background.
* **Import failed** in **People** → **Add people** → **Bulk import employees** offers Company Admins and HR Admins **Start over** to return to **Upload**.

### Questions people ask

* **Can I import employees and contractors in one file?** No. In **People** → **Add people** → **Bulk import employees**, Company Admins and HR Admins choose one kind under **Who are you importing?** and use that kind's template.
* **Can I import international contractors?** No. **People** → **Add people** → **Bulk import employees** creates U.S. contractors only. Company Admins and HR Admins use [Add people](https://every.help/admins/hr/onboarding.md) for international contractors.
* **Does an import update people already in Every?** No. **People** → **Add people** → **Bulk import employees** skips a row whose email already exists. For available profile edits, see [All People](https://every.help/admins/hr/overview.md).
* **Do errors stop the whole import?** File errors do; row errors leave valid rows importable. In **People** → **Add people** → **Bulk import employees**, a file with missing required columns or no data rows, or over 10 MB or 10,000 data rows, is rejected.
* **Why is the Import button unavailable?** No row is valid, or the import is still working. The import button on **Review** in **People** → **Add people** → **Bulk import employees** needs at least one row under **Ready to import**.
* **Does Release Hire 2 emails send invitations just for this file?** No. **Release Hire 2 emails** on **Done** in **People** → **Add people** → **Bulk import employees** sends invitations for imported people of the selected kind across the company, including earlier imports. It skips people who already finished or declined onboarding, or were invited by an earlier release.
* **Does importing send invitations immediately?** No. **People** → **Add people** → **Bulk import employees** creates people without sending the normal onboarding invitation. On **Done**, Company Admins and HR Admins can select **Release Hire 2 emails** to send invitations. On **People**, in a person's row menu, Company Admins and HR Admins can select **Send Invite** to invite one person sooner.

### Not covered here

* When do invitation emails arrive, and who are they from? To ask, email [support@every.io](mailto:support@every.io).
* Which pay schedule does an import use when several schedules have the same name? To ask, email [support@every.io](mailto:support@every.io).
* How do I recover personal or bank details from the CSV that weren't saved? To ask, email [support@every.io](mailto:support@every.io).


## Related topics

- [All People](https://every.help/admins/hr/overview.md)
- [Add people](https://every.help/admins/hr/onboarding.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.