Shared team mailboxes with ownership, routing, and access control

Coordinate support, QA, finance, and platform teams around shared inboxes with access control, alias routing, and event visibility.

Create team inboxes Organization docs

Trusted by top companies worldwide

Product features

Concrete controls for shared team mailboxes

Run shared team mailboxes with clear ownership, role-based access, aliases, and auditable event workflows.

Organization workspaces with shared inbox inventories

Run MailSlurp as a shared workspace where support, QA, engineering, and operations can work on the same mailbox estate without sharing one personal account.

Manage organization users

Roles, invites, and CSV onboarding

Assign mailbox access through organization roles, invite members directly, and bulk onboard teams as shared inbox use grows.

Manage roles and invites

SAML SSO and access-link login

Connect enterprise identity, control who can enter the workspace, and keep login behavior aligned with the organization that owns the shared mailboxes.

Set up Okta SSO

Alias, ruleset, and webhook controls around shared addresses

Pair shared inboxes with aliases, routing rules, and webhook events so the mailbox can act like a real operational queue instead of a passive shared address.

Explore email webhooks

Support and success rotation inboxes

Use shared inboxes for ticket triage, onboarding questions, and escalation queues so every message has a visible owner and service-level target.

Explore

Release and QA review channels

Keep pre-release notifications and test results in dedicated team mailboxes so engineering, QA, and product can work from the same message timeline.

Explore

Finance, vendor, and compliance communication

Create durable shared addresses for procurement, finance, legal, and audit workflows while preserving message history and access controls.

Explore

Provision inboxes on demand

Create isolated addresses for users, tenants, releases, or tests without shared mailbox state.

Explore

Organization workspaces with shared inbox inventories

Run MailSlurp as a shared workspace where support, QA, engineering, and operations can work on the same mailbox estate without sharing one personal account.

Manage organization users

Roles, invites, and CSV onboarding

Assign mailbox access through organization roles, invite members directly, and bulk onboard teams as shared inbox use grows.

Manage roles and invites

SAML SSO and access-link login

Connect enterprise identity, control who can enter the workspace, and keep login behavior aligned with the organization that owns the shared mailboxes.

Set up Okta SSO

TScreate-inbox.ts

const MailSlurp = require('mailslurp-client').default;
const mailslurp = new MailSlurp({
  apiKey: process.env.API_KEY ?? 'your-api-key',
});

// create an inbox with options using the inbox controller
const inbox = await mailslurp.inboxController.createInbox({
  // name is used a contact name when sending
  name: 'John Doe',
  // use the expanded domain pool so randomly assigned email address is more varied
  useDomainPool: true,
  // permanent by default or supply an expires at time
  expiresAt: undefined,
});

Use inbox APIs, SMTP, and webhook events in the same workflow

Start with SDK helpers for inbox creation and message waits, then move into event-driven routing when the workflow expands.

Open docs

TScreate-inbox.ts

const MailSlurp = require('mailslurp-client').default;
const mailslurp = new MailSlurp({
  apiKey: process.env.API_KEY ?? 'your-api-key',
});

// create an inbox with options using the inbox controller
const inbox = await mailslurp.inboxController.createInbox({
  // name is used a contact name when sending
  name: 'John Doe',
  // use the expanded domain pool so randomly assigned email address is more varied
  useDomainPool: true,
  // permanent by default or supply an expires at time
  expiresAt: undefined,
});