Work on lists as a team

Share lists, results, history, and suppressions in one organization. Invite teammates and manage API keys in one place.

Get started free API and SDKs

Fig. 1Organization · Northwind

Sample workspace

Roles: Owner, Admin, Member
Sign-in: Each teammate has an account
Scope: Everything belongs to the organization
Seats: From 3 on Free

§ 1

Why it matters

Checks get lost in spreadsheets

When each person cleans lists on their own, results are repeated, lost, or out of date.

Everyone sees the same results, so nobody cleans the same list twice.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Lists and results sit in one person's account.With Verifier: Lists, results, and suppressions belong to the workspace.
Without: API keys are shared in chat.With Verifier: Each API key has its own scopes and can be revoked.
Without: Each teammate keeps a different suppression file.With Verifier: Everyone works from the same suppression list.

§ 2

How it works

One organization, shared work

Lists, jobs, history, suppressions, and settings belong to your organization. Each teammate signs in with their own account.

Fig. 3One organization, shared work

3.1Create your organization
3.2Invite your teammates
3.3Work on lists, suppressions, and settings together

Each teammate signs in with an account

§ 3

What you get

What you get.

3.1Comments on jobsLeave notes on a list job, so the next person knows what was decided.
3.2Provisioning for larger teamsEnterprise plans support SCIM, so accounts follow your identity provider.

Table 3 · What belongs to a workspace

Object	Shared with the team
Lists and results	Yes
Check history	Yes
Suppression list	Yes
API keys	Yes, each key has its own scope
Delivery endpoints	Yes
Usage	Yes, one total for the plan

§ 4

In practice

Typical uses.

Case 4.1
Marketing and operations together
Operations cleans the export, and marketing sends from the clean file.

Works with the tools you send from.

All integrations

Questions

Before you start.

How many people can join?

Free includes 3 seats, Starter 10, Professional 50, and Enterprise has no seat limit.

Checks get lost in spreadsheets

When each person cleans lists on their own, results are repeated, lost, or out of date.

Everyone sees the same results, so nobody cleans the same list twice.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Lists and results sit in one person's account.With Verifier: Lists, results, and suppressions belong to the workspace.
Without: API keys are shared in chat.With Verifier: Each API key has its own scopes and can be revoked.
Without: Each teammate keeps a different suppression file.With Verifier: Everyone works from the same suppression list.

One organization, shared work

Lists, jobs, history, suppressions, and settings belong to your organization. Each teammate signs in with their own account.

Fig. 3One organization, shared work

3.1Create your organization
3.2Invite your teammates
3.3Work on lists, suppressions, and settings together

Each teammate signs in with an account

What you get.

3.1Comments on jobsLeave notes on a list job, so the next person knows what was decided.

3.2Provisioning for larger teamsEnterprise plans support SCIM, so accounts follow your identity provider.

Table 3 · What belongs to a workspace

Object	Shared with the team
Lists and results	Yes
Check history	Yes
Suppression list	Yes
API keys	Yes, each key has its own scope
Delivery endpoints	Yes
Usage	Yes, one total for the plan

From a raw listto a safe send.

Work on lists as a team

Checks get lost in spreadsheets

One organization, shared work

What you get.

Typical uses.

Works with the tools you send from.

Before you start.

From a raw listto a safe send.

Work on lists as a team

Checks get lost in spreadsheets

One organization, shared work

What you get.

Typical uses.

Works with the tools you send from.

Before you start.