Managing team members: suspend, reactivate, remove, monitor

Last updated May 19, 2026Team management

Once you have team members on your account, the Team tab is where you manage their access, monitor their usage, and make changes over time. Every action — suspend, reactivate, remove — is owner-only and takes effect immediately.

Viewing the team

Account Settings → Team. The member list at the bottom of the page shows every active and pending member with the following columns:

ColumnDescription
EmailLogin email
StatusActive, Pending, or Suspended
Invited DateWhen you sent the invitation
Last LoginExact timestamp of their last sign-in
Credits UsedCredits consumed this month (resets at the start of each month)
ActionsSuspend/reactivate, remove

Monitoring credit usage

The Credits Used column tells you per-member consumption for the current month. Common uses:

  • Identify who is using the most credits (often the highest-volume verification user).
  • Spot inactive members (zero credits used in a month is a strong signal — consider removing).
  • Plan top-ups based on rolling team-level usage rather than a single global number.
  • Investigate sudden spikes (large unexpected jumps can indicate a misconfigured integration on a team member's account).

Counts reset on the first of each month. Historical per-member usage is preserved in the credit-history log if you need to look back further than the current period.

Suspending a team member

Suspending temporarily blocks access without removing the member. The right tool when you want to pause someone — vacation, leave, investigation — without losing the record.

How to suspend

  1. Open Account Settings → Team.
  2. Find the member in the list.
  3. Click the suspend icon in the Actions column.
  4. Confirm.

What happens at suspension

  • Status flips to Suspended (red badge).
  • Their current session is terminated immediately — they are signed out.
  • They cannot sign in again until you reactivate them.
  • They receive an email notification informing them of the suspension.
  • Their per-member usage history and verification results are preserved on the account.
  • Any integrations they connected remain configured but become inactive (they cannot run new jobs through them).

When to suspend

  • Team member is on extended leave or vacation.
  • You need to temporarily pause someone while investigating unusual usage.
  • A project that required their access has ended but may resume.
  • You want to revoke access before a difficult conversation — pause first, decide on removal afterward.

Reactivating a suspended member

  1. Open Account Settings → Team.
  2. Find the suspended member.
  3. Click the reactivate icon in the Actions column.

Access is restored immediately. They can sign in again with their existing credentials — no new password or new invitation needed. Their preserved usage history is visible to them again, and any integrations they had configured are usable again.

Removing a team member

Removing permanently deletes the team-member relationship. The action is final — you cannot undo it. To restore access, you would send a fresh invitation, which creates a new account record.

How to remove

  1. Open Account Settings → Team.
  2. Find the member.
  3. Click the delete icon in the Actions column.
  4. Confirm in the modal.

What happens at removal

  • Their current session is terminated immediately.
  • They can no longer sign in or access the account.
  • They receive an email notification.
  • Their verification history and uploaded results remain on the account — those are your data, not theirs.
  • Any integrations they connected become orphaned and need to be reconnected by another team member or the owner.
  • Per-member usage stats roll up into the historical totals but the per-row member identity is preserved for audit purposes.

When to remove vs. suspend

  • Remove if the person has permanently left the company or no longer needs any access.
  • Suspend if the absence is temporary or you want to investigate before deciding.
  • Suspend then remove if you want to revoke access first and decide on permanence later (low-risk path for ambiguous cases).

Managing pending invitations

If a member has not accepted (status: Pending), you have two options:

  • Wait — invitations do not expire. The pending entry stays until they sign in or you remove it.
  • Remove and resend — if you suspect the original invite never arrived, remove the pending row and send a new one. That generates a fresh password and a fresh email.

What team members can and cannot do (reference)

Team members CAN

  • Verify single emails from the dashboard
  • Upload bulk lists
  • Download their own verification results
  • View the shared credit balance (read-only)
  • Connect and use their own integrations
  • Update their own profile and security settings (password, 2FA, sessions)
  • View Credits History (read-only)

Team members CANNOT

  • Buy credits — Buy Credits sidebar item is hidden
  • Generate API keys — Developer sidebar item is hidden (Sidebar.tsx:188)
  • View billing or invoices — Billing & Payments and Invoices tabs are hidden
  • Invite other team memberscreate-team-member rejects with 403
  • Suspend or remove other members — Team tab is owner-only
  • Cancel the subscription or change plans — subscription management is owner-only
  • Configure auto-refill or low-balance alerts — those tabs are hidden
  • See other members' verification details — they only see their own work

Best practices

Review the team quarterly

Once a quarter, walk down the team list. Remove members who left, suspend genuinely inactive accounts, and check for unusual usage patterns. Lean teams stay safer than bloated ones.

Communicate before suspending or removing

The system sends automatic email notifications, but a personal message from you avoids confusion. If you are suspending for investigation rather than for cause, tell the member that's what you're doing.

Investigate high-usage spikes

Per-member usage that suddenly jumps is worth a conversation. Could be a legitimate large project — could also be a misconfigured integration that is verifying the same list multiple times, or an API key that leaked into a public repo. Better to ask than to debug it after the fact.

Common questions

Can a suspended member see old verification results?

No. While suspended they cannot access the account at all. When reactivated, their historical results are still in place.

What happens to a removed member's verifications?

The verification results stay on the account — they are your data, not theirs. Removing a member does not delete any verification rows.

Can I transfer ownership to a team member?

Not through the dashboard. Ownership is tied to the original signup record. If you genuinely need ownership transferred (departing founder, role change), email support@validemailchecker.com — we handle these case-by-case after verifying identity on both sides.

Do removed members keep any data or access?

No. Removal is immediate and complete on the team-account side. Their independent account (if they create one elsewhere later) is unrelated.

Can I see exactly which emails a team member verified?

You see their total per-member usage and their bulk-task names on the shared Uploads & Results page. You do not see the individual rows of single-email verifications they ran from the dashboard verifier unless you filter by member. The audit trail prioritizes usage accountability over individual privacy on personal verifications.

Next steps