An administrator is configuring Einstein Activity Capture (EAC) for a team of sales executives who use Google Workspace. Management specifies that client emails and calendar events must automatically display on opportunity record timelines, calendar items must sync bi-directionally, and executive leadership must understand how captured data affects activity reporting in standard Salesforce reports.
Which two statements accurately describe the setup requirements and operational behavior of Einstein Activity Capture that the administrator must consider?
- Users must be assigned an Einstein Activity Capture permission set before they can be added to an active sync configuration in Setup.Answer
- Captured emails and events are stored off-core in external AWS storage, meaning they do not create standard Task or Event records and are excluded from standard Salesforce activity reports.Answer
- CNew user profiles must be created and assigned to sales executives to enable the automated background capture and sync engine.
- DEnabling bi-directional event sync automatically generates standard Task records in Salesforce to ensure full compatibility with operational report types.
Answer
The correct requirements are that users must be assigned an Einstein Activity Capture permission set prior to configuration inclusion, and that captured emails/events reside on external AWS storage and thus do not appear in standard Salesforce activity reports.
Assigning users an Einstein Activity Capture permission set is a strict requirement prior to adding them to an EAC configuration. Additionally, EAC captures emails and events off-core into AWS cloud storage; while these activities appear seamlessly on record activity timelines, they do not create core Task/Event records and are excluded from standard Salesforce activity reports.
Step-by-Step Solution
Key Concept
Einstein Activity Capture Architecture and Prerequisites
Estimated Time:2m 0s