Organization & Sub-Accounts
Overview
The Organization & Sub-Accounts structure is designed to help you manage complex setups involving multiple teams, clients, environments, or products - all under a single Organization.
Each sub-account functions as a fully isolated workspace with its own set of projects, sending domains, email templates, stats, credentials (SMTP/API), and even team members. This separation ensures that data, permissions, and sending behavior in one sub‑account will never affect the others.
At the same time, your Organization acts as the central hub:
Centralized billing lets you keep all sub‑accounts under one subscription plan and one invoice.
Shared quota pools apply across all sub‑accounts using Email API/SMTP, Email Campaigns or Email Sandbox, making it easy to allocate resources flexibly.
Org-level permissions give users access to all current and future sub‑accounts by default - ideal for admins or managers.
Sub-account-level permissions can be assigned when you need to restrict access to just selected environments or clients.
Clear separation of data. Projects, templates, stats, and domains stay neatly separated between sub‑accounts.
Deliverability isolation. Each sub‑account's sending reputation stays isolated. If one goes off track, others remain unaffected.
Smooth migration of accounts. Existing standalone accounts can be converted to sub‑accounts, bringing over settings, stats, and domains seamlessly.
This structure is ideal whether you're working with:
API/SMTP
Email Campaigns
Email Sandbox
No matter the product, sub‑accounts remain consistently isolated and manageable.
Additionally, if your teams or clients shift over time, you can transfer sub‑accounts between Organizations without losing historical data, settings, or domain authentications. Our support team can guide you through this process to make it smooth and safe.
If your account is currently using Braintree as the payment gateway, you'll need to migrate to Stripe in order to enable and use the Organization & Sub‑Accounts feature.
When to use Organization & Sub-accounts
Use Organization & Sub‑accounts to:
Isolate own projects or products.
Serve multiple clients or brands without overlap.
Control access for different teams, business units or clients.
Prevent issues in one sub‑account affecting others.
Keep email stats, templates, or sender configurations isolated.
Creating a sub-account
Go to the left-side menu and select Organization. This will open the Organization panel.

Click Sub-accounts menu item and Create Sub-Account button.

Enter the sub-account name and click Create.

You will be automatically redirected to the new account settings page, where you can manage other account settings.

You're ready! Each sub‑account starts fresh with no domains, tokens, or stats - configure however you like.
You can create as many sub‑accounts as needed - there is no limit, making this feature scalable for any organization size.
Switch between your organizations and sub‑accounts from the left-side menu anytime.

Migrating an already existing account
If you have multiple Mailtrap accounts and want to merge them under a single Organization (without re-authenticating domains or losing data), our Support Team can help make the process smooth. You can transfer any account, including free ones. The only requirement is that the destination Organization is on a subscription plan that includes Organization & Sub-accounts.
To start, email us at [email protected] from the account owner's email address (the one who owns the account you want to move) and include:
Account name or ID you want to transfer
Destination Organization name or ID
Email address of the destination Organization Owner (for security verification)
Reason for the transfer (e.g., merging workspaces, restructuring your team, etc.)
Once we receive your request, our team will confirm the transfer with both sides.
Important notes
If you need to transfer multiple accounts, please submit one request per account. Always send each request from the account owner's email.
The transferred account will be removed from the original Organization.
Original Organization admins and viewers will lose access to this account. Account-level admins and viewers will retain their access.
If the transferred account was the only one in the original Organization, the subscription for that Organization will be canceled. If no accounts remain, the empty Organization will be deleted.
Transfer and access
After both sides approve:
The account will be moved from the Original Organization to the Destination Organization.
The account will now use the subscription and usage limits of the Destination Organization.
Usage counters will reset, since the account is now part of a new shared plan.
Permissions & user management
The Organization & Sub‑Accounts structure offers flexible and secure user access controls, so you can easily tailor permissions based on team roles, client needs, or project scope.
Types of access
There are two levels of user access:
1. Organization-level access
Users with this access-level can see and manage all current and future sub-accounts within the Organization. This is ideal for admins, finance, or central teams that need a global overview. You can assign roles such as:
Org Owner – The highest-level role within Organization structure. This role is automatically assigned to the person who created the Organization and comes with full, unrestricted access.
Org Admin – Full access to organization settings and billing, as well as admin access to all sub‑accounts.
Org Viewer – View-only access to organization settings and billing, as well as view access to all sub‑accounts.
Billing Admin - Full access to billing.
Billing Viewer - View-only access to billing.
2. Account-level access
If a user only needs access to selected sub‑accounts, you can invite them to those accounts only. Description of account-level roles can be found here: Account-level User Management.

Viewing current users
You can easily check who has access to your account.
Account users:
Go to the Settings → User Management tab to see a list of all users with account-level access. Permissions can be updated at any time from this panel - you can change access rights or remove users with just a few clicks.
Organization-level users:
All users with Organization-level access also have access to your account, and they are listed in a separate "Organization" tab. These users automatically have access to all current and future sub‑accounts.
If you are an Organization Owner or Organization Admin, you can edit organization-level users (e.g., invite, remove, or change roles). If you don't have admin rights, you will still see the full list of org-level users, but only in view-only mode.

API tokens
API tokens in Mailtrap are account–level. That means each sub‑account has its own isolated set of tokens used for authentication when interacting with Mailtrap's API or SMTP services. Also, an organization has its own tokens to create and list their sub-accounts.
Key Points
Isolated by design: Tokens are unique to each sub‑account and cannot be used to access resources from other sub‑accounts or the entire Organization.
Scoped access: API tokens grant access only to the specific data and resources within the sub‑account they were created in, helping maintain strict separation between teams or environments.
Management via UI: Tokens can currently be created, viewed, and revoked via the API Tokens section inside each sub‑account.
FAQ
Users and Permissions
Organization and Sub-Account Management
Quotas and Stats
General
Last updated
Was this helpful?

