Overview
Create outbound messages with sender account, recipients, subject, text/HTML content, headers and attachments while preserving drafts as first-class records.
Problem
One-off workspace email needs durable draft state and governed sender/attachment selection.
Solution
Use MailBridge compose and draft APIs to persist content, recipients, headers and attachments before immediate or queued delivery.
How it works
Drafts keep separate recipient, header, and attachment records. Users can reopen, update, send, enqueue, bulk-send, bulk-enqueue, or delete drafts according to plan and permission rules.
Who is this for
Operations User
Email Operator
Expected outcomes
- Durable draft state before delivery
- Consistent sender, recipient, attachment and send authorization
Key metrics
Security impact
- Draft bodies, recipients, headers, attachments, sender account references and send state · PII: yes where email addresses, message content, attachments, recipients, or integration payloads contain personal data
Compliance
- Workspace permissions
- Sender-account and attachment resource authorization
Availability & next steps
Starter
Pro
Enterprise