The Agent Objects tab decides what the AI can see. An object that is not enabled here does not exist for the agent: it cannot be queried in the chat, and record pages of that object show no record context. Within an enabled object, the fields you tick are the ones the AI is told about and the ones sent as record context.
Before you start#
You need the AI_Engine_Admin permission set. Your own read access matters too: the tab lists only objects and fields you can read.
Enable an object#
- Open Ai Agent Admin Setup → Agent Objects.
- Find the object in the list on the left. Use the search box or the All / Active / Custom filters.
- Click the object row to open its settings.
- Switch Active for Agent on.
- In the Fields subtab, tick the fields the agent may read. Select All and Clear help with long lists.
- Click ✓ Save. The confirmation shows how many fields were saved.
Nothing is stored until you click ✓ Save. This includes the on/off tick next to each object in the list: it changes the object only on screen, and the change is lost if you open another tab or reload the page first.
The list contains your custom objects (except AI Engine's own configuration objects) plus those of the following standard sales and service objects that exist in your org: Account, Contact, Lead, Opportunity, Case, Campaign, Campaign Member, Opportunity Contact Role, Contract, Order, Quote, Product, Price Book, Asset, Entitlement, Solution, Knowledge Article, Work Order, Service Appointment, Task, Event and User. System objects such as history, share and feed objects are not offered.
Task, Event and User are always available to the chat, even if you do not enable them. Enabling them still helps: the AI is told about the fields of enabled objects only.
Choosing fields#
- Start narrow. Account, Contact, Lead and Opportunity, plus the two or three custom objects your reps use most, cover most early questions. Add more when users ask for them.
- Tick what people ask about. Names, owners, stages, amounts, dates, statuses, industry, source and the custom fields that carry your business meaning.
- Fewer fields, smaller requests. Every ticked field, including the allowed values of picklist fields, is described to the AI with each chat question. Long field lists make every request larger and slower.
- Field names matter. The AI sees each ticked field by its API name and reads that name as meaning. Fields with clear business names give better answers than fields named after an integration.
Your selection does not widen anyone's access. The agent reads CRM data with the running user's own permissions, so field-level security and sharing apply on top of your selection: a field or record the user cannot read in Salesforce is not returned to them through the chat or the record context either.
Flag personal data#
When a ticked field holds personal data, click Mask as PII next to it. The badge changes to PII. Click ✓ Save to store the flag. When Allow PII is off in Org Profile, flagged fields are replaced with placeholders before anything is sent to the AI provider.
Fields of the Email and Phone types, and compound address fields such as Billing Address, are masked automatically. Individual address parts such as Street, City or Postal Code are ordinary text fields, so flag them with Mask as PII if you tick them. See PII masking.
Activity Digest settings#
When a user asks "what happened this week?" without naming an object, the chat builds an Activity Digest across your enabled objects. See Activity Digest. Two settings per object control it:
| Setting | Effect |
|---|---|
| Include in Activity Digest | On by default. Switch off to leave the object out of digest answers. |
| Digest order | A number that sets the order of sections in the digest. Objects without a number come after the numbered ones, in alphabetical order of their API names. |
The digest covers at most six objects. Use Digest order to put the most important ones first.
Related records#
The Child Objects subtab chooses which related lists are added to the record context on a record page. See Child objects and Meeting Prep.
Deactivating an object#
Open the object, switch Active for Agent off and click ✓ Save. The field selection is kept, so you can switch the object back on later without starting again.
Troubleshooting#
- "Object not enabled for AI Agent" on a record page, or "not configured for AI Agent access" in the chat. The object is not enabled. Enable it and save.
- A field never appears in answers or table columns. It is not ticked, or the user has no field-level access to it.
- The agent queries the wrong field or picklist value. Untick fields with similar names that users do not need, so the AI has fewer candidates to choose from.