This article lists what AI Engine includes in each request to your AI provider. It is written for admins and security reviewers who need to answer "what leaves Salesforce?". Everything below is read with the running user's permissions (for automatic scoring, the user the scoring job runs as), so records and fields that user cannot see are not included.
When Allow PII is off (the default), the values described in PII masking are replaced with placeholders before the request is sent.
Included in most requests#
- Your playbook. The Org Profile texts Company Description, Lead Process, Email Guidelines, Qualification Questions and Compliance Guardrails are included in chat and record-action requests, so they shape tone and content. Do not put personal data or confidential information you would not send to the provider into these texts.
- Record context, when a feature runs on a record: the fields enabled for that object in Agent Objects (empty fields are left out) and related information your admin configured, such as recent tasks, events, Chatter posts and child records.
Per feature#
| Feature | What goes to the provider |
|---|---|
| Sales Agent chat | The question; the last few messages of the conversation; the user's name and Salesforce user ID (so questions about "my" records work); a description of the objects and fields enabled in Agent Objects, including picklist values; the current record's context while the chat shows IN CONTEXT. A further request then sends the query that ran, the number of records returned and a sample of up to 10 rows, and the AI writes the answer from that. |
| Tables, charts, Show all, export | Nothing. These are built from Salesforce data in your org and browser. |
| Next Steps, Draft Email, custom prompts | Record context and playbook. Custom prompts also send the template text and the rows returned by any data sources on the template. Global prompts run without record context. |
| Analyze Email | The selected emails from the record's activities, or the text pasted into Paste Email, plus record context. |
| Meet Prep | Record context, recent activities, key contacts (names and titles; on an Account also their email addresses, which are masked when Allow PII is off), open opportunities and records of the related objects selected under Meeting Prep — Additional Objects in the Org Profile. For those related records, every field the user can read is included (long values shortened), up to the record limit set per object. With Meet Prep: include web search on, the company name is also used for a web search. |
| Web Check | The company name, website, city, country and industry from the record. The person's name, title, email address and phone number are included only when Allow PII is on. |
| Company News | The company name for the web search; the search results are then sent with the record context and playbook to write the news cards. |
| AI Score | The fields selected in Scoring Context Fields (or the fallback field list), a summary of recent won and lost records (business attributes such as source, industry and amount), activity and recency information, and your field weights and scoring instructions. |
| Verify Company On The Web (scoring) | One web search per scored record with the company name, email domain and website. On a Lead, the person's name and title are included only when Allow PII is on. The email address and phone number are not sent; only the domain of the email address is. |
| Magic Snap | The photo, the optional note and, for photos taken with the camera, the approximate location if the browser allows it. Research this company and Find companies send the company name, website and city, or the description you typed, to a web search. |
| PDF documents | For AI-written sections, the section's prompt plus the record's name and ID. Table and field sections are filled from Salesforce and are not sent. |
| Help mode | The question, the relevant built-in help text and any help extension your admin added. No CRM records. |
Web search#
Web Check, Company News, research questions in the chat, Meet Prep web search, Verify Company On The Web and Magic Snap research use the web search tool of your AI provider. The provider runs the searches on the public web using the search subject (typically a company name). With Azure OpenAI, web search goes through a separate OpenAI connection; see Choosing a provider for compliance.
What is not sent#
- Records the user cannot see, and fields hidden from the user by field-level security.
- In the chat and record actions, objects that are not enabled in Agent Objects. Record context contains only the enabled fields, and the AI is told only about enabled objects and fields. A chat query can read only enabled objects, but it can include other fields of those objects that the user can see, such as the name of a related record. Meet Prep related objects and AI Scoring use their own settings, described in the table above.
- The current record, when the user has switched the chat to DETACHED.
- Your API key as part of the prompt. Salesforce adds it to the request as authentication; see API keys and Named Credentials.
Keeping requests small#
The less you enable, the less is sent. Enable only the objects and fields users need, mark personal-data fields as PII, and keep web-search options off where you don't need them. The same choices also reduce token usage; see Token usage and cost.