Bulk import for volunteers

You can now bulk-import team volunteers (team managers, team parents, assistant coaches) from a CSV — the third importer to go live, after athletes and facilities.

Who can use it: club admins and coaches. Where to find it: top nav → Import → Volunteers.

What it does

• Upload a CSV with one row per volunteer assignment. Each row references a team by name, so a single file can assign volunteers across many teams in your club.
• If the volunteer doesn’t have a user account yet, one is created automatically from their first name, last name, and email. Their login stays disabled until they claim the account via the existing signup or password reset flow — so this is safe to bulk-upload without worrying about premature access.
• If the volunteer already has a user account (matched by email), the existing account is reused. We do NOT overwrite their name, phone, or other profile data.
• The same person can be a volunteer on multiple teams. Put them on multiple rows with different team names — the user is matched once by email and a separate team_volunteers row is created for each team.

Example: one volunteer helping two teams

 team_name,first_name,last_name,email,volunteer_role,background_check_status
Mustangs,Sarah,Chen,sarah.chen@example.com,Team Manager,cleared
Mustangs,Raj,Patel,raj.patel@example.com,Team Parent,pending
Thunder,Sarah,Chen,sarah.chen@example.com,Team Manager,cleared 

Result: 2 users(Sarah + Raj), 3 team_volunteers rows(Sarah→Mustangs, Raj→Mustangs, Sarah→Thunder). Sarah’s user record is created once and linked to both teams.

What’s required in the CSV

team_name , first_name , last_name , email . Everything else is optional: phone, volunteer_role (free text), background_check_status (pending / cleared / expired / none / never_checked), background_check_date, start_date, notes.

Team names are matched case-insensitively within your club — the team must already exist (the volunteer importer doesn’t auto-create teams, since team settings like season and primary coach can’t be inferred from a volunteer row).

Re-running is safe

Re-importing the same CSV is idempotent. The (team, user) pair has a unique constraint, so duplicate rows are silently skipped — no double-assignments, no duplicate users. This is useful when you want to correct a few bad rows and re-upload the fixed file.

What’s coming next

• Coaches + users import — creating user accounts with specific club roles (separate from volunteers, which are per-team assignments).
• Teams import — will land last, since team rows reference coaches and facilities that must exist first.
• Invite emails for auto-created volunteer accounts (so they know they’ve been added and can claim their login).