Connect a personal Gmail account

⚠ Not currently available.

Personal Gmail connect is disabled. The flow’s only purpose was to send from your personal address — its inbound arrives through a Gmail forwarding rule, not through us — and sending from a connected mailbox is not supported. Muin no longer requests the gmail.send permission, so there is nothing this connection would enable today.

The rest of this page describes the intended design, kept for reference. If you want your work mail in the comms hub, use Connect a Google Workspace mailbox (read-only inbound sync).

Connect a personal @gmail.com account to Muin without giving us inbox-read access. Personal Gmail uses a different model from Workspace: Muin only requests permission to send on your behalf, and you set up a Gmail filter that forwards just the messages you want into the Muin comms hub. Your inbox stays your own.

Workspace vs personal Gmail. If your Gmail address is at your organization’s custom domain (e.g. you@yourorg.org), that’s Workspace — use Connect a Google Workspace mailbox for full inbox sync. Personal Gmail is the privacy-respecting bridge for when full inbox access isn’t appropriate.

Prerequisites

A personal Gmail account (any @gmail.com address). Workspace accounts are blocked from this flow — they’re routed to the Workspace path automatically.
A Muin tenant ingestion address — you’ll see it in the wizard. It looks like your-tenant-slug@inbound.falaah.ai.
Muin tier: any tier with the Communications Hub enabled.

Privacy promise

What we ask for	What we use it for
`gmail.send`	(Not currently requested — this flow is disabled. It would have sent a reply only when you explicitly accepted an AI suggestion or composed a message in Muin.)
`email`, `openid`	Identify which Gmail account connected.

What we do NOT ask for	What stays private
`gmail.readonly` (or any read scope)	Your inbox content stays in your inbox — Muin can’t read it.
Drive, Calendar, Contacts	Untouched.
Spam folder, trash, archives	Untouched.

The mail Muin sees is only what your Gmail filter forwards. You control the filter; you can change or delete it any time from your Gmail settings.

Step-by-step

Sign in to Muin and go to Settings → Communications → Connected mailboxes, or open the wizard at /settings/communications/mailbox/connect.
Choose Personal Gmail on the provider-select step. The consent screen reminds you that Muin won’t be reading your inbox.
Click Continue with Google. Google signs you in and shows the permissions screen — confirm the Send mail on your behalf scope and click Allow.
Muin shows you your forwarding destination — it’s your-tenant-slug@inbound.falaah.ai. Copy it.
In a new tab, open Gmail → Settings (gear icon) → See all settings → Forwarding and POP/IMAP.
Click Add a forwarding address, paste the address from step 4, and click Next → Proceed. Gmail emails a confirmation code to that address.
The code arrives in Muin, automatically — no need to copy it manually. The wizard polls and confirms the address as Verified within ≈30 seconds.
Switch to the Filters and Blocked Addresses tab in Gmail settings. Click Create a new filter.
Set the filter criteria. We pre-fill a smart default — typically from:donor.org OR from:newsletter@... OR has:attachment — but you can tighten or broaden it. The narrower your filter, the less mail flows through.
Click Create filter, then check Forward it to: pick your Muin ingestion address. Click Create filter to save.
Send yourself a test email matching the filter. The Muin wizard’s polling indicator flips to ✓ Active within 5 minutes.

How donor mail reaches Muin (the forwarding bridge)

   Donor sends mail to your Gmail
         │
         ▼
   Gmail filter forwards matching mail to {slug}@inbound.falaah.ai
         │
         ▼
   AWS SES receives, stores in muin-{env}-email-ingestion S3
         │
         ▼
   SNS notifies Muin's webhook
         │
         ▼
   Inbound router routes to your tenant's comms hub
         │
         ▼
   You see the message threaded into the Muin Unified Inbox

Troubleshooting

Symptom	Action
Wizard stuck on “Waiting for the first forwarded email…” >5 min	Send yourself a test email matching the filter. If still stuck, click Get help to open a tagged ticket — we’ll work the `email-mailbox-forwarding-rule-not-working` runbook.
”This forwarding address is not yet verified” in Gmail	Re-add the address in Forwarding and POP/IMAP — Gmail re-sends the code, and Muin auto-confirms.
Filter exists but no donor mail forwards	Filter criteria too narrow. Edit the filter in Gmail and broaden the rules.
You hit Gmail’s “20 forwarding addresses” cap	Remove an unused forwarding address in Gmail settings before re-adding ours.

Disconnecting

Settings → Communications → Connected mailboxes → Disconnect clears the OAuth send token. We can’t delete your Gmail filter for you (we never had access to it) — go to Gmail’s Filters and Blocked Addresses to remove it manually.