How to Keep Each Client's Email Lists Separate When You Verify for Many Clients

The risk with many clients in one verification account is a mix-up, not a hack. A list uploaded without a label, an export sent to the wrong client, a usage number nobody can split. The fix is a rule that every list is filed under a client the moment it is uploaded, and a tool that makes that the easy path. On the Agency plan, that tool is client workspaces.

How lists end up mixed

• Files named leads_final_v3.csv with no client in the name.
• A shared downloads folder that holds every client's exports.
• One person verifying for three clients in the same afternoon.
• No way to tell, a month later, which list belonged to whom or how much it cost.

None of these is a security failure. All of them are how the wrong file ends up in the wrong inbox.

What workspaces do

On Agency, you file each list under a client workspace. Then:

• History can be filtered by client, so you see only that client's lists.
• Exports can be filtered by client, so a download does not contain someone else's rows.
• Usage is shown per client by month, with a CSV export, which makes the monthly report and any billing straightforward. See billing clients for verification.

Lists you do not file show up under a "No workspace" label, so unfiled work is visible and not lost.

What workspaces do not do

They are not separate client accounts and do not give clients a login. They do not change who on your team can see what: every seat on the account shares the account's lists. If a person should not see a client's data, do not give that person a seat. More on that in seats without sharing logins.

A simple routine

1. Create the workspace when you sign the client, before any list exists.
2. Name files client-first: acme_2026-11_webinar-leads.csv.
3. Pick the workspace at upload, not afterwards.
4. Export from the filtered view, never from the full history.
5. Check the "No workspace" bucket weekly and file anything left there.
6. Delete the downloaded file from your own machine once it is in the campaign tool.

Keeping the do-not-send side separate too

Suppression lists need the same care: one client's unsubscribes should not silently block another client's sends, and a shared list should be a deliberate choice. See a shared do-not-send list across client domains.

When one client has several lists

Use the list name for the campaign and the workspace for the client. Per-client usage then rolls up all of that client's lists by month, and you can see which campaign used the most checks.

Next step

Workspaces, branded client reports and 15 seats come with the Agency plan. Compare it with the others on pricing.