Team workspaces
Give every client and team its own operating workspace.
Keep contacts, campaigns, inboxes, domains, suppressions, replies, analytics, settings, and API access inside an explicit workspace, then give each teammate the role their work requires.
Isolated workspaces·Owner, admin, and member roles·Organization-level provisioning
Two operating levels
The organization coordinates. Each workspace contains the work.
Membership, billing, and shared setup paths
Organization roles govern broader administration, while supported DNS and inbox-purchasing connections can be managed centrally for repeatable workspace setup.
Contacts, campaigns, infrastructure, and replies
Every operating record carries workspace context so a team or client can work without exposing another workspace's contacts, inboxes, threads, or campaigns.
Workspace roles
Keep daily operation open while constraining sensitive setup.
| Work area | Member | Admin | Owner |
|---|---|---|---|
| Sequence definitions | Operate | Operate | Operate |
| Campaign lifecycle | Restricted | Manage | Manage |
| Unified inbox and tags | Operate | Operate | Operate |
| Analytics | Core view | Full view | Full view |
| Contacts and exports | Restricted | Manage | Manage |
| Domains, inboxes, providers | Restricted | Manage | Manage |
| Workspace settings and users | Restricted | Manage | Manage |
| Workspace billing authority | Restricted | Restricted | Owner |
Repeatable onboarding
Create the next workspace through the product or the API.
Agencies can use an organization-scoped provisioning key to create and seed a workspace, then receive its scoped operating key once. Plan workspace limits still apply.
- Organization-bound workspace creation
- Idempotent configuration seeding
- Scoped operating key returned once
- Plan capacity enforced during provisioning
FAQ
Frequently asked questions
What is separated by workspace?
Contacts, campaigns, sequences, inboxes, domains, suppressions, reply threads, analytics, settings, connections, and workspace-scoped API access are kept in their operating context.
Which workspace roles are available?
MailSequence supports workspace owner, admin, and member roles. Members can work with sequence definitions, inbox triage, tags, and core analytics; owners and admins manage campaign lifecycle actions, infrastructure, contacts, settings, users, and full analytics.
Can a member access another workspace?
Only if that user has explicit membership or permitted access to the other workspace. Resource queries and policy checks remain bound to the active workspace.
How many workspaces are included?
Starter includes 1, Growth 3, and Scale 10 workspaces. Enterprise uses custom workspace capacity. Other plan limits still apply inside the organization.
Can I create workspaces programmatically?
Yes. The organization-scoped provisioning API creates and seeds workspaces and returns a scoped operating key once, subject to the plan workspace limit.
Is MailSequence white-label?
No white-label capability is claimed. Team workspaces provide operational separation, permissions, shared organization setup paths, and programmatic provisioning.
Give every client or team a clear operating boundary.
Choose the workspace capacity you need, assign roles, and automate repeatable setup where it earns its place.