Email Integrations
Gmail
Connect a Gmail mailbox from Atlas settings so Atlas can ingest operational email and attach relevant threads to cases.
Prerequisites
| Google role | Workspace admin or mailbox owner |
|---|---|
| Mailbox | Shared operations inbox or named user inbox |
| Scopes | Read mail, send mail when approval policy allows |
Connect in Atlas
Atlas Settings -> Email
The Gmail flow lives in the Email settings surface, not the ERP connector grid.
- Mailbox example
- ops@acme-manufacturing.com or purchasing@acme-manufacturing.com.
- Empty state
- No mailboxes connected yet, with a Connect Gmail button.
- Connected row
- Mailbox address, Connected/Revoked/Error status chip, last sync time, Reconnect when revoked, Disconnect, and Sync now.
- Inbox check
- Use View Inbox to confirm Atlas has ingested the mailbox after OAuth completes.
- 1
Open Atlas settings
Sign in to Atlas, open the settings page, and find the Email section. If no mailbox is connected, the panel shows No mailboxes connected yet.
- 2
Click Connect Gmail
Atlas calls the Gmail connect endpoint and redirects you to Google OAuth. Use the Google account for the operations mailbox you want Atlas to ingest.
- 3
Review the Google consent screen
Google shows the app name, account, and requested Gmail permissions. Confirm the account is the mailbox Atlas should monitor, then approve the consent screen.
- 4
Return to Atlas
After the redirect completes, the Email section should show the mailbox address with a Connected status. Atlas begins the initial sync automatically.
- 5
Send a test message
Send a realistic customer or supplier email to the connected mailbox, then open Atlas Inbox from the Email section and confirm the thread appears.
Approval boundary
Atlas can draft responses from Gmail context, but external sends follow your configured autonomy and approval policy.
OAuth scopes
Gmail access is granted through Google OAuth. Atlas should request the narrowest Gmail scopes that support the enabled workflow. Read-only triage can use read scopes; workflows that label/archive threads need modify access; workflows that send approved replies need send access.
| Read-only triage | gmail.readonly or an equivalent restricted read scope |
|---|---|
| Inbox management | gmail.modify when Atlas needs labels, archive, or thread state updates |
| Approved replies | gmail.send when Atlas is allowed to send or submit final email through Gmail |
| Long-running access | offline access so Atlas can refresh access without asking the operator to sign in every run |
Restricted scope review
Gmail scopes that read or modify mailbox content are sensitive or restricted. Production OAuth apps should expect Google verification and internal security review before broad rollout.
Google setup references
- Google Gmail API scopes
Use this when confirming which Gmail scopes map to read, modify, and send capabilities.
- Remove third-party app access
Use this during recovery when the wrong Google account was authorized or app access needs to be revoked before reconnecting.
Verify the connection
- 1
Confirm the connected account
Check that the connected Google identity matches the mailbox Atlas should monitor, especially if the browser has several Google accounts signed in.
- 2
Send a representative test email
Use a realistic customer or supplier request with the same subject, sender pattern, and attachment shape your workflow will see in production.
- 3
Check thread ingestion
Open Atlas Inbox and confirm the test thread appears with the expected sender, timestamp, subject, and body preview.
- 4
Run Sync now if needed
If the mailbox row is connected but the thread has not appeared, click Sync now in the Email section and re-check the inbox.
- 5
Check action policy
If the workflow can draft or send email, verify the first run stops at approval rather than sending unexpectedly.
Disconnect and reconnect
Reconnect Gmail when the wrong account was authorized, scopes changed, the admin revoked app access, or Google returns token errors such as invalid_grant.
- 1
Disconnect in Atlas
In Atlas Settings -> Email, click Disconnect on the mailbox row so new ingestion jobs stop using the old credential.
- 2
Remove third-party access in Google
In the Google Account security settings, remove Korso or Atlas from third-party app access for the mailbox account.
- 3
Reconnect from a clean browser session
Return to Atlas Settings -> Email and click Connect Gmail or Reconnect. Use an incognito window or sign out of unrelated Google accounts if account selection was the original problem.
- 4
Run a fresh test email
Do not rely on old thread state. Send a new test message and confirm ingestion uses the new account.