Send drafts (composing Gmail drafts)
Sharing a case creates a real Gmail draft in your own Gmail mailbox with subject, body, and attachments pre-filled. The draft opens in Gmail's compose view in a new tab — you review and click Send from inside Gmail yourself. Document Blueprint never sends mail; it only drafts.
Last updated
Sharing a case creates a real Gmail draft in your own Gmail mailbox with subject, body, and attachments pre-filled. The draft opens in Gmail's compose view in a new tab — you review and click Send from inside Gmail yourself. Document Blueprint never sends mail; it only drafts.
What you need
- Your own Gmail account connected at Settings → Integrations (one-time OAuth — the same connection that powers inbound automations). Drafts always land in the signed-in user's mailbox; there's no "send as the workspace owner" option.
- Permission to compose. Workspace owners always have it. Workers and clients start without it — your workspace admin enables you per-account at Settings → Team → Compose Emails.
- A case to share.
How it works
When you trigger a share, the app composes a {to, cc, subject, body, attachments} payload from the active send template and the selected case(s), then calls the Gmail Drafts API on your behalf. A real draft appears in your Gmail account, and a new browser tab opens directly into Gmail's compose view with everything pre-filled. You review, edit if needed, and click Send from inside Gmail.
The product composes; it never sends. It hits Gmail's draft endpoint (users/me/drafts), not the send endpoint. Every outbound message terminates with you clicking Send inside Gmail, with a human in the loop.
Why drafts and not direct send
Email is high-stakes. A misconfigured field, an unintended recipient, or a wrong attachment can damage relationships. The human-review step inside Gmail is the cheapest insurance against those mistakes.
After enough real-world testing in production, direct send may become an opt-in option. For now, every outbound message terminates as a Gmail draft you click Send on yourself.
Step by step
- Open a case (or select multiple cases in the dashboard).
- Trigger the share — Compose share in the case detail overflow menu, or Compose Draft in the batch action bar when multiple cases are selected.
- Pick a saved send template, or configure the recipients, subject, body, and attachments inline.
- Optionally add a personal note — it appears at the top of the body.
- Click Open Gmail Draft. The action creates the draft in your Gmail account and opens it in a new tab.
- Gmail's compose view loads with everything pre-filled.
- Review, edit anything that needs editing, click Send from inside Gmail.
Two share paths
The product has two distinct share entry points — don't confuse them:
- Single-file share — the Share button in the file review modal. Hands one file's title + URL to your device's OS share sheet via the Web Share API. No template, no body, no Gmail. For "just share this one PDF" cases.
- Composed share (this article) — Compose share / Compose Draft. Builds a templated subject + body, attaches one or more files from the case, and creates a real Gmail draft. The whole reason send templates exist.
When you can't compose
If your workspace admin hasn't granted you the "Compose Emails" capability, the composer footer shows "Ask your workspace admin to enable Compose Emails for your account." instead of the Open Gmail Draft button. You can still read the composer and see what the draft would contain — you just can't dispatch it. Ask your admin to flip the toggle at Settings → Team for your member row.
If you have permission but haven't connected your Gmail yet, the footer shows "Connect your Gmail to compose" instead. Click it to walk through the one-time OAuth, then come back and the Open Gmail Draft button replaces the connect CTA.