FAQ
Which email providers can I connect?
Microsoft 365 (OAuth), Google Workspace (OAuth), or Resend (API key). One active provider per tenant. Falls back to Blankitt-owned email if unset.
1 min readLast updated 25 May 2026
Jump to section
Three options
| Provider | Auth | Best for |
|---|---|---|
| Microsoft 365 | OAuth (client_id + tenant_id + client_secret) | Teams running on Microsoft 365 |
| Google Workspace | OAuth (refresh_token via consent flow) | Teams running on Google Workspace |
| Resend | API key | Anyone — easy to set up, transactional |
Connecting Microsoft 365
- Register an app in Azure AD (Application permissions:
Mail.Send) - Grant admin consent
- In Settings > Email > Microsoft 365 > Connect, enter tenant ID, client ID, client secret
- Set
from_addressto the licensed mailbox (typicallyhr@yourdomain.com) - Click Activate
Connecting Google Workspace
- Set up an OAuth client in Google Cloud Console
- Enable Gmail API + add
gmail.sendscope - In Blankitt HR, click Connect — you'll be redirected to consent
- Authorise; you're back in HR with the connection active
Resend
Just paste your Resend API key + verified from_address. Cheapest path.
Fallback
If no provider is configured, HR routes mail through Blankitt's own email service (M365 primary, Resend failover) — the same chain the rest of Blankitt uses. Limited custom-domain support; fine for invites and self-service emails to your team.
Why one active at a time
Switching providers mid-flight could split delivery between two; the toggle is exclusive to avoid confusion. Deactivate before swapping.