Connect a Gmail mailbox
Connect a user-owned Gmail mailbox for supported email work.
- For
- Signed-in users and integration owners
- Owner
- Integration operations
- Outcome
- Test, monitor, recover, rotate, and disconnect a Gmail mailbox safely.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
Connect a user-owned Gmail mailbox for supported email work. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.
Prepare the connection
The provider controls consent, mailbox permissions, and token lifetime.
- Sign in to the intended Google account and review the requested access.
- Confirm that the connected address shown in Sakhaa is correct.
- Use a non-sensitive test thread and verify send, receive, and reply association.
Connect and prove health
- Open /app/settings?section=email in the correct workspace.
- Save the oauth consent only in the protected setup surface.
- Connect the mailbox and confirm the connected account appears before sending.
- Confirm this healthy result: The mailbox shows as connected and its sync state is current.
Use synthetic data and an approved test identity. Do not use customer traffic only to prove a connection.
Monitor and recover
- Monitor: Review connection, token, mailbox sync, send, and reply-threading state.
- Recover: Reconnect the mailbox, then run a bounded sync if the account is healthy but stale.
- Rotate: Reconnect through OAuth. Do not copy or store provider tokens manually.
- Disconnect: Disconnect the mailbox and confirm the replacement send path for open work.
- Limits: The provider controls consent, mailbox permissions, and token lifetime.
- Fallback: Use the company send path or another approved mailbox while the user reconnects or completes a bounded sync.
Support boundary
Sakhaa supports the CRM configuration and product behavior. The provider controls account approval, billing, quotas, and external service availability.
- Record the provider, workspace, approximate time, safe error code, expected result, and actual result.
- Do not include passwords, access tokens, API secrets, message content, or unnecessary customer data.