Recommended security settings

A checklist of settings that keep AI Engine's access and data exposure to what your users actually need.

AI Engine follows your Salesforce permissions, but several settings decide how much data is available to it and who can see its logs. Use this checklist when you set up AI Engine, and review it after every package upgrade.

Access#

Assign AI Engine Admin only to the people who configure AI Engine. It gives full access to the configuration and to all activity log records. Give sales users AI Engine User only. See Permissions and sharing.
Grant principal access to the provider credential only to AI Engine users. Grant it through a permission set assigned to the same people who have the AI Engine permission sets.
Prefer the packaged permission sets to clones. Clones do not receive changes from upgrades, so they drift out of date.
Remove access when people change roles. Once the AI Engine permission sets are removed, the user's next AI request is refused. Remove their principal access too.

Data scope#

Enable only the objects and fields users need in Agent Objects. The AI is only told about enabled objects and fields, so a narrow scope limits what chat questions can retrieve. Start with the core sales objects and add more when there is a clear need.
Leave out fields with special-category or confidential data (for example health, HR or bank details) unless the use case requires them.
Configure child objects and Meeting Prep objects deliberately. They add related records to requests. For objects selected under Meeting Prep — Additional Objects, every field the user can read on those records is included, so choose objects whose fields you are comfortable sending, and keep the record limit low.
Pick Scoring Context Fields. Without them, scoring falls back to a built-in field list plus the Agent Objects fields. Selecting the fields yourself makes the scoring request contain exactly those fields.

Personal data#

Keep Allow PII off (the default). Email, phone and address fields, and common identifiers found in text, are then masked before requests leave Salesforce. Masking is pattern-based, so also follow the next point.
Mark personal-data fields as PII in Agent Objects and list further fields under Custom PII fields in the Org Profile, for example text fields that hold national ID or tax numbers. See PII masking.
Keep the playbook free of personal data. The Org Profile playbook texts are included in chat and record-action requests.

New installations of AI Engine set the AI Activity Log to Private. Org-wide defaults are your org's own setting, and a package upgrade does not change them, so confirm the value in your org:

Go to Setup → Sharing Settings.
In Organization-Wide Defaults, click Edit.
Find AI Activity Log and set Default Internal Access and Default External Access to Private.
Decide on Grant Access Using Hierarchies in the same row. While it is selected, managers can read the log records of users below them in the role hierarchy. Clear it if they should not.
Click Save. Salesforce may recalculate sharing in the background and email you when it finishes.

With Private, users see their own log records, and admins with AI Engine Admin see all of them. Check the setting again after upgrades and whenever you review sharing.

Web search#

Turn on web-search options only where they add value. Meet Prep: include web search (Org Profile) and Verify Company On The Web (AI Scoring) are off by default. Web Check and Company News run only when a user clicks them.
On Azure OpenAI, decide whether web search may use OpenAI. Web-search features on Azure use a separate OpenAI connection. See Choosing a provider for compliance.

Provider account and key#

Use a dedicated API key for AI Engine, and set usage or spending limits in your provider's console if it offers them.
Rotate the key on a schedule and keep a second provider tested for outages. See API keys and Named Credentials.
Review your provider's API data terms, including retention and whether API data may be used for training, and choose the settings or agreement your policy requires.

Monitoring#

Review the Activity Monitor regularly for failed calls and unusual usage by user or feature. See Activity log and auditing.
Show SOQL in Chat is a troubleshooting aid. It is saved in the browser where it is switched on, not for the whole org. Switch it off again when you are done.