---
schema_version: "1"
id: 1f3ca3c6239439511a7820e6591f4ca06b925435eca1c765a874a4ede98829b0
title: Einstein and Data Usage in Agentforce Coworker
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/agentforce-coworker/agentforce-coworker-about/agentforce-coworker-einstein-data-usage.md
canonical_url: https://developer.salesforce.com/docs/data/agentforce-coworker/guide/agentforce-coworker-einstein-data-usage.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b2f72dfe846c554196c9785e71ee7bb521d6be58b3ddaa6d3bfaacfec109756d
products:
  - Agentforce Coworker
  - Data 360 Developer Documentation
---
# Einstein and Data Usage in Agentforce Coworker

Einstein powers the generative AI features in Agentforce Coworker. Review this table to understand the type of data used by Einstein features in Agentforce Coworker.

The table indicates which features use global models trained on customer data. These models look for aggregated trends across multiple Salesforce customers. If an Einstein feature uses a global model, the customer can opt out of the global model and have control over whether their data contributes to global models. For more information on how to control how your data is used, see [Manage Salesforce Access to Customer Data](https://help.salesforce.com/s/articleView?id=ai.generative_ai_consent_optout.htm&language=en_US&type=5).

| Feature             | Customer Data and Salesforce Objects Used                                                   | Usage Data Used                                                                                                    | Global Model Used |
| ------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------------- |
| Agentforce Coworker | Search terms, search results, CRM objects, and data sources connected by customers | User engagements, record IDs, org metadata and metadata for matching users, documents, and queries | Yes               |
