PlacementFlow connects to Microsoft 365 / Outlook with a single OAuth sign-in that covers email, calendar, and Teams. This is the mailbox your warm email (candidate submissions, client follow-ups) sends from, and the calendar your interviews sync to.
That's it. One connection gives you:
Google Workspace support is coming — it's pending Google's security audit process. Until then the connect option shows as Coming soon, and Microsoft 365 / Outlook is the supported provider. There is no generic IMAP/SMTP option; connections are OAuth only, so PlacementFlow never sees or stores your password.
| Permission | Why it's needed |
|---|---|
| Send mail as you | Submissions and warm follow-ups from your address |
| Read replies | Auto-pause sequences when someone responds |
| Read/write calendar events | Interview scheduling and two-way sync |
PlacementFlow doesn't read your personal email, attachments, or your full inbox — only the reply threads it needs to keep sequences honest. Full details are in the Privacy Policy.
Cold candidate and BD outreach never sends from your connected mailbox. It goes out from dedicated sending domains that PlacementFlow provisions and manages, so cold volume can never damage your own domain's reputation. Your mailbox is reserved for warm, high-trust email.
Microsoft access tokens expire regularly; PlacementFlow refreshes them automatically in the background. You normally never notice.
If a refresh permanently fails (password change, revoked consent, organisation policy change), the account shows an error state in Settings → Email Accounts — reconnect by going through the same connect flow again.
Disconnecting a mailbox pauses any campaigns that send from it. Reconnect the same address and those campaigns resume automatically.