An email verification integration often starts with one developer and one API token. As more people and projects use it, the questions change: which contacts belong to this client, who can manage access, and who pays for this project’s usage?

Workspaces give each project or team a place of its own in UnwrapEmail. You can create or join multiple workspaces with one account. Each workspace has its own contacts, bulk operations, exports, API tokens, custom domain blacklist, usage, and subscription.

A workspace for each boundary that matters

An agency can keep each client’s contact lists and validation jobs in a separate workspace, then invite the people who work on that client. A product team can use separate workspaces when production and test data need different access or billing.

You do not need another workspace for every integration. If two applications should share the same contacts, team, and subscription, give each application its own API token inside the same workspace. Create a separate workspace when the data, membership, or subscription should be separate too.

The Workspaces page shows the workspaces you belong to and your role in each. Choose + New workspace, enter a name, and open the new workspace as its owner. For a longer list, search by name to find the one you need.

Switch projects without losing track of the context

The menu beside the dashboard logo switches workspaces. Each selection opens that workspace’s overview. If it needs an active subscription, the server sends you to its subscribe page. The same menu is available there, so you can choose another workspace without completing checkout for the current one.

Workspace pages carry their workspace ID in the URL. You can keep one workspace open in one tab and another in a second tab. Switching the second tab does not change where the first tab’s forms submit.

Your own profile stays separate. Change your personal display name from Profile in the account menu. Change a workspace’s display name or copy its ID from Settings → General.

Invite people with the access they need

Open Settings → Members to send invitations, review the member table, and manage pending invitations. Teammates accept using the verified email address that received the invitation. You can resend an invitation or revoke it before it is accepted.

Workspaces have three roles:

  • Owner: manages the workspace, appoints admins, transfers ownership, and controls its subscription.
  • Admin: manages API tokens, invites and removes members, and views workspace billing.
  • Member: uses the workspace’s data and product features without managing tokens, membership, or billing.

Member access is not read-only. Choose the role based on what someone needs to do in that workspace, and use the members and roles guide for the full permissions table.

Integrations stay attached to their workspace

API tokens belong to the workspace where they were created. REST calls and MCP tools use that workspace’s data and subscription. Changing your selection in the dashboard does not redirect an integration to another workspace.

Tokens also remain with the workspace when their creator leaves. A team can change ownership without replacing every integration credential. When offboarding someone who held token secrets, review those credentials separately: removing their membership does not revoke workspace tokens.

Ownership and payment can change separately

Each workspace has its own subscription and usage. One payer can fund multiple workspaces, but activating one does not activate the others.

Ownership can be transferred to an existing member from the Members table. The new owner takes over administration, and the former owner becomes an admin. Billing responsibility stays with the existing payer until the new owner accepts it in Settings → Billing.

For an active subscription, the billing handover is scheduled for the next billing period. This gives the team an explicit step for changing who pays while keeping the workspace and its integrations together. The billing and ownership guide explains the transition and the requirements for leaving or deleting a workspace.

Start with your next project

Open Workspaces, create a workspace with a recognizable name, and invite the people who need access. Activate its subscription when you are ready to use the verification tools, then create a token for the integration that will send requests.

The workspace documentation brings the setup, membership, and billing guides together.