Give VAs and SDRs Access to Email Verification Without Sharing a Login

Give each person their own seat and keep the owner login to yourself. A shared password is the easy start and the hard cleanup: you cannot see who uploaded what, you cannot remove one person without changing it for everyone, and the login ends up in a chat thread. Business and Agency plans include seats so this does not have to happen.

What the plans include

Plan	Seats	What the seats share
Business, $99 a month	5: you plus 4 teammates	The account's lists, volume and API keys
Agency, $249 a month	15: you plus 14 teammates	The same, plus client workspaces and branded client reports

Seats share the account's volume. A teammate's checks count toward the same monthly total as yours. For the case where a Pro account is shared informally, see team seats vs a shared account.

Why VAs and SDRs need access at all

VAs usually clean and verify lists; SDRs usually pull a verified list for a campaign. Giving them their own seat means the person who needs the list can get it without asking you to export it, which takes you out of the loop on routine work.

A simple access policy

1. Owner login stays with the owner. Billing and plan changes are not a VA's job.
2. One seat per person, never per role.
3. Remove the seat the day someone leaves, including contractors at the end of an engagement.
4. Decide who gets a seat by what they may see. Every seat shares the account's lists. If a contractor should only touch one client's list, think twice before seating them on an account that holds all your clients.
5. Put the file rules in writing. Verified exports go into the campaign tool and get deleted from downloads.
6. Use API keys for tools, not people. Keep keys out of shared docs and rotate them when someone with access leaves.

Using workspaces with seats

On Agency, ask team members to file every list under the client workspace at upload. The client filter then keeps history and exports tidy. Remember it organises lists, not permissions. See keeping each client's lists separate.

What to log

• Who has a seat and why.
• The date each seat was added and removed.
• Which API keys exist and who holds them.

A short table in your ops doc is enough.

Capacity check

More hands means more checks. Before adding people, see how many client lists fit in 750,000 checks a month. Past the monthly volume on Business or Agency, lists keep running in the slower lane and are never cut off.

Next step

Seats are part of the Agency plan; Business has 5. See both on pricing.