What happens to a team member's verifications when I remove them?

Removal is the permanent offboarding option on Valid Email Checker. Click the red Trash icon on the Team page, confirm in the modal, and the team member's access ends immediately. Some things are cleaned up aggressively (the auth account, the team record, their integrations), some things are preserved (the audit trail of what they did), and a few things you might expect to happen — refunds for credits they spent, automatic notifications to teammates — do not happen. Here is the exact breakdown.

What gets deleted on removal

The delete-team-member edge function walks through a cleanup sequence:

• User integrations. Mailchimp, HubSpot, Klaviyo, and any other ESP/CRM connections the member set up are deleted. In-flight verification jobs running through those connections will finish, but no new jobs can start.
• User sessions. Active sessions are terminated. They are forcibly logged out within seconds.
• Their personal verification records and tasks (on their user ID). Some bookkeeping rows that were tied to the member's user account directly.
• Their personal credit transactions / buckets. These should be empty (team members do not have their own credit buckets) but the cleanup defensively wipes anything that might be there.
• User metadata, 2FA settings, user settings, payment methods (if any), invoices, payment transactions, subscriptions. All scrubbed.
• The team_members row. The membership record itself is deleted first (this triggers the Realtime DELETE event the member's open session uses to log them out cleanly).
• Finally, the auth user. The Supabase Auth user is deleted. Their email is now free to sign up again as a fresh account if they want, but it is no longer connected to your team.

What is preserved (on purpose)

• Credit history attributed to them on the owner's ledger. The owner's credit_transactions rows still have performed_by_user_id pointing at the (now-deleted) user ID. The Credits History page may show 'Unknown user' for those rows if it cannot resolve the name, but the rows themselves stay forever — they are part of the owner's audit trail.
• Verification results and download links on owner-scoped tables. Anything that was logged at the account level rather than at the member level remains.
• Past bulk upload results that the owner can still download. Bulk task records belong to the owner account; the member's removal does not delete the cleaned lists they produced.

What does NOT happen automatically

• No credit refund. Credits the member consumed before removal stay consumed. See do team members share my credits — the shared pool is the shared pool.
• No automatic notification to the rest of the team. Other team members are not told that someone was removed. If they share Slack with the removed person they will find out organically; we do not broadcast.
• No auto-revoke of API keys. API keys belong to the owner, not the team member, so they keep working. If you generated a key on behalf of a member and want it disabled when they leave, revoke it manually from Developer → API Keys.
• The removed member does get an email. A 'you have been removed from a team' notification is sent to their address. Body contains a link to signup if they want to start their own account.

When suspend beats remove

If there is any chance the person is coming back — leave, sabbatical, between client engagements — use suspend instead. Suspend keeps the account, the integrations, the credentials, and the history all intact. One reactivation click and they pick up where they left off. Remove is for permanent off-boarding only.