How do I reactivate a suspended team member?

Reactivating a suspended team member on Valid Email Checker is the symmetric reverse of suspending them — one click on the Team page, an instant state flip in the database, and an email to the member letting them know they can sign in again. Their account, history, integrations, and login credentials are all intact from when they were suspended, so they pick up exactly where they left off.

How to reactivate

1. Open Account Settings → Team.
2. Find the suspended member — their status badge will be red and read Suspended.
3. Click the green Ban icon in the Actions column. The tooltip on a suspended row reads 'Reactivate' (the same icon serves both directions; the color tells you which direction the click goes).
4. The status badge flips back to green Active.

What happens server-side the moment you click

1. Status flips to `active` in the database. team_members.status updates from suspended to active.
2. A reactivation email is sent to the member. The email body confirms the account is active again and includes a Login button pointing at https://app.validemailchecker.com/auth/login.
3. Login is unblocked. From this moment, the member can sign in with their existing email and password. The auth check no longer rejects them at the session layer.

What they see when they come back

Nothing about the account looks different to them. The dashboard, the integrations they had connected, the verifications in their history — all unchanged. The credit balance reflects the current shared pool (which may have moved up or down while they were suspended). If they had 2FA enabled before suspension, the 2FA prompt still appears at login as normal.

What if they forgot their password during the suspension?

Standard password-reset flow. From the login page they click the forgot-password link and a reset email goes to their address. We do not generate a new temporary password on reactivation — the original credentials are still in place. If they cannot reset and you cannot reach them through normal channels, removing and re-inviting them (one click each) generates a fresh temporary password as part of the re-invite. See how do team members log in for the first time for the password mechanics of the invite flow.

When reactivation is the wrong call

Two cases where you should remove rather than reactivate:

• The member left the org permanently. Reactivating to give them temporary access is fine, but if the relationship is over, removal cleans up the auth account and the team-member record properly. See what happens to a team member's verifications when removed.
• You suspect the suspension was triggered by their account being compromised. If you suspended because of a security incident, reactivate only after you have confirmed credentials are rotated, 2FA is in place, and the original concern is resolved.