Achilles — Auth: Bulk Invite Preview

Step 2 of bulk import: review the parsed list before sending invitations.

Wireframe

step 2 · review and send

achilles.local/admin/users/import /admin/users/import · Owner / Admin

1 2

Review the list

Default role

Member

All 260 new 240 existing 12 duplicates 3 errors 5 2

Email	Name	Role	Status
anna@company.com	Anna Orlova	Member	new
dmitry@company.com	Dmitry Sokolov	Admin	new
igor@company.com	Igor Lebedev	Member	existing 3
anna@company.com	—	Member	duplicate
maria@company	Maria Kim	Member	invalid email 4

Skipped rows don't block sending

filter · errors

← All errors 5

Email	Name	Status
maria@company	Maria Kim	invalid email
p.orlov@	Pavel Orlov	invalid email

state · sent

Invitations are on their way

240 queued · 15 skipped · 5 errors 5

Download report Go to invitations

1 The role for rows without one in the file; a role set in the row is kept. Same rules as a single invitation.
2 Counters by status — a click filters the table to those rows, "All" restores the full list.
3 "Existing" — the address is already in the system or awaiting acceptance; it isn't invited again.
4 Invalid rows and in-file duplicates are skipped and recorded in the report — they don't block sending.
5 The send summary. Invitations land in the invitations tab with pending status.