The setup runs in three places. Plan one hour per user for the first rollout; ongoing onboarding is a 10-minute task once the org-wide configuration is in place.
- Enable the Gmail integration in Salesforce
Setup, Gmail Integration and Sync, toggle Let users access Salesforce when working in Gmail. Confirm Lightning Experience is the active UX; the extension does not work with Classic.
- Allow the Google Workspace add-on
Google Workspace admin opens admin.google.com, Apps, Google Workspace Marketplace apps, and allow-lists the Salesforce add-on for the relevant OU.
- Configure Einstein Activity Capture (optional)
Setup, Einstein Activity Capture, create a configuration, assign users, and pick the sharing model (Everything, Contacts and Events, Don't Share).
- User installs the Chrome extension
User opens Chrome Web Store, installs the Salesforce extension, signs in with their Salesforce credentials.
- User installs the Google add-on
From Gmail, user opens the right-side panel, clicks the plus icon, installs Salesforce add-on, accepts the OAuth consent.
- Test logging an email
User opens any thread, clicks the Salesforce sidebar, searches for a record, clicks Log Email. Verify the Task or Email Message appears on the chosen record.
- Einstein Activity Capture stores emails in a separate activity store, not as standard Task records. Reports built against the Task object will miss captured activities unless the EAC virtual report types are used.
- Lightning Sync was deprecated in 2023; new orgs use Einstein Activity Capture. Existing orgs on Lightning Sync should plan a migration before Salesforce removes the feature.
- Auto-Bcc to Salesforce (Email-to-Salesforce) still works as a backup but creates Tasks without the rich Email Message metadata the modern integration produces.
- Google Workspace policy can block the OAuth consent, leaving users stuck on the sign-in screen. The Workspace admin must explicitly approve the Salesforce add-on for the user's OU.