For admins only. Every row in the file is emailed an invitation at once, so check the file before you upload it.
Steps
- Open Import staff. Read the list under Expected columns first.
- Make a CSV with a heading row: email, full_name and role. One person per row.
- For the role, use the codes the page lists. Each email must appear only once.
- Keep it to 200 rows and 1 MB. Split a longer list into two files.
- Under CSV file, choose your file.
- Press Upload & send invitations.
- Read the result. It says how many were sent and how many failed, and why.
If it goes wrong
- If any row is invalid, no invitations are sent at all. The page lists up to 25 problems with their line numbers. Fix them and upload again.
- If you run out of seats, the page says so, and everything before that row was sent. Add seats in billing, then upload the rest.
- If someone does not get the email, ask them to check spam. Send a fresh invitation from the staff page.
How it links together
Each person who accepts gets an account with their role. They then appear in staff contacts and can be given a caseload. See the guides to inviting one person.
- Upload file
- Invitations sent
- Person accepts
- Give a caseload
What each person receives
An email from your organisation, saying they have been invited with their role and giving a secure link to accept. The link expires after seven days.
The columns
- email: required. Each address may appear once in the file.
- full_name: required, up to 160 characters.
- role: required. Only the codes listed on the page are accepted.
The checks come first
The whole file is checked before anything is sent. A repeated email, a missing name or an unknown role stops the lot, with the line number of each fault. This means you never get half a team invited by accident.
Seats
Each invitation needs a seat. When seats run out the page stops at that row and tells you. Rows before it were sent. Add seats, then upload a file containing only the rest.
Inviting one person instead
For one or two people, use the invitation form on the staff page. It is quicker than making a file.
Who can use this page
Only admins. Anyone else sees a short note that the page is for the admin role.
