An Account Email is a user's identity on your event — the key to their login, their history, their profile. Until now, a single stray cell in a People Excel import could quietly change it. One wrong value, one accidentally cleared field, and an existing attendee's Account Email was overwritten. That door is now closed. The People Excel import rejects any row that would change or clear the Account Email of an existing user, and tells you exactly which rows were blocked and why.

What's new

The People Excel import now validates the Account Email column against your existing users. If a row matches an existing user but carries a different Account Email — or leaves the cell empty — that row is rejected before it can touch the account. Everything else imports as usual.

Key behaviors

• Same email, no problem: rows that match an existing user and keep their current Account Email pass straight through, exactly as before.
• Changed email, rejected: any row attempting to set a different Account Email on an existing user is blocked and counted in the import modal's Errors.
• Empty email, rejected: a blank Account Email cell on an existing user is blocked too — no accidental wipes.
• Nothing else gets touched: when a row is rejected, none of that user's other fields are modified. The whole row is skipped cleanly.
• New users unaffected: rows whose ID doesn't match an existing user flow through normally — onboarding new people works exactly as it always has.
• Mixed files still work: in a file with both valid and invalid rows, only the offending rows are excluded. The rest are processed without interruption.

In your results CSV

Download the results and every blocked row is spelled out for you:

• Each rejected row appears with an ERROR status.
• The error column reads: "You cannot change the Account Email of an existing user."
• The row and id columns pinpoint the exact source row and record, so fixing the file takes seconds.
• Other error types keep their own distinct messages — you can tell issues apart at a glance.