The most common sync an admin turns on is Einstein Activity Capture, which connects users' Microsoft or Google email and calendar to Salesforce. Set it up once at the org level, then add the users or profiles who should sync.
- Open the Einstein Activity Capture setup
In Setup, use Quick Find to open Einstein Activity Capture, then start the guided setup to create a configuration. A configuration bundles your capture and sync choices and the people they apply to.
- Choose the email and calendar sync settings
Decide whether email syncs as full messages or header-only, and whether calendar events sync in both directions. These choices affect privacy and what appears on the activity timeline, so confirm them with stakeholders before saving.
- Assign users or profiles
Add the users, profiles, or permission set holders who should be included in this configuration. Only assigned users have their email and calendar captured.
- Have each user connect their account
Each assigned user connects their Microsoft or Google account from their personal settings under Email and Calendar Accounts. After connecting, allow up to 24 hours for past activity to appear.
Full message captures the email body and metadata; header-only captures just sender, recipients, and subject for tighter privacy.
Choose one-way or bidirectional event sync. Bidirectional lets edits flow both ways but introduces conflict handling.
Scope the configuration to specific users or profiles so only the intended people sync their accounts.
Decide whether captured emails and events are private to the user or shared with their team on related records.
- The first sync is not instant. Salesforce notes it can take up to 24 hours for past emails and events to populate after a user connects an account.
- EAC captures activity into its own store using public cloud infrastructure, so some synced items do not behave like standard Task or Event records in reports.
- For calendar events, EAC gives preference to changes made in the connected Microsoft or Google calendar when a conflict occurs.
- If your org still runs the retired Lightning Sync, migrate to EAC rather than running both, since the two store data differently.