When you turn on Einstein Activity Capture, Salesforce creates a corresponding Einstein Activity Capture service on the Activity Platform Hyperforce infrastructure.
Required Editions
| Available in: Lightning Experience |
| Available with Einstein Activity Capture Standard in Sales in Starter, Pro Suite, Professional, and Enterprise Editions |
| Available with Unlimited Edition, Einstein 1 Sales Edition, and Agentforce 1 Edition |
| Available with Einstein for Sales, which is included in Einstein 1 Sales Edition and available for an extra cost in Enterprise and Unlimited Editions |
| Available with Sales Engagement, which is included with Sales in Performance and Unlimited Editions, and available for an extra cost in Professional and Enterprise Editions |
| Available with Revenue Intelligence, which is available for an extra cost in Enterprise and Unlimited Editions |
Encrypted private keys authenticate the integration between Salesforce first-party servers, where your primary Salesforce data is stored, and Activity Platform Hyperforce infrastructure servers, where some of your Einstein Activity Capture data is stored. These keys are required when Einstein Activity Capture makes API calls to the infrastructure.
Data Separation
Einstein Activity Capture data is logically separated. Even though it’s in the Salesforce main instance, your data is tagged to your org and isolated. Users in other orgs can’t access your captured emails. This separation is enforced by design in multitenant storage.
Org Trust and Revocation
Admins can disconnect a user’s Einstein Activity Capture connection by removing the user from the Einstein Activity Capture configuration. Users can delete their accounts connected to Salesforce. From personal settings, in the Quick Find box, enter Connected Accounts, and then select Email and Calendar Accounts. Disconnecting an account revokes the token and stops data capture. Retention policies decide the retention period of the data captured.
If you suspect any compromise, such as a token leak, you can revoke the OAuth token from the email provider side, for example, through Microsoft’s admin portal or Google security settings.