Connect Salesforce to IrisAgent
A Salesforce admin should do these steps.- Sign in to the IrisAgent dashboard with Google, Microsoft, or Okta SSO.
- Choose Salesforce:
- During onboarding: on Connect your first data source, choose Ticketing system, then Salesforce.
- Later: go to Data Sources → Ticketing System and pick Salesforce.
- Click Connect production org or Connect sandbox org.
- Sign in to Salesforce, grant the OAuth permissions, and click Allow.
Install the IrisAgent app in Salesforce account
- While logged in to the target org, open the installation link:
- Production or Developer org: Production installation link
- Sandbox org: Sandbox installation link (sandboxes must use
test.salesforce.com)
- Select Install for All Users (you can restrict profiles later), check the acknowledgment, click Install, then Done.

Add IrisAgent to the Lightning case page
- Go to Setup → Object Manager and open the Case object.
- Open Lightning Record Pages, then edit or create a page.
- Add IrisAgent Sidebar: Inline Email where you want it. Do not also add the standard IrisAgent Sidebar component.
- Make sure the standard Email action is visible in the Case Feed publisher on load. Agents use it to insert Suggested and Dynamic Resolutions into the email composer.
- Click Save, then Activate if prompted.
Share your custom fields
Email us the API field names for:- Article body in Salesforce Knowledge
- Case priority
- Any other entity where you use a custom field instead of the standard one
Permissions accessed by IrisAgent
OAuth scopes
IrisAgent requests two scopes:api: access to the Salesforce REST API.refresh_token: keeps ingestion running without a new sign-in.
Object permissions
Grant field-level read access on custom fields you share, and edit access on Case fields IrisAgent should update.
- IrisAgent never deletes Salesforce records and does not use the Metadata, Tooling, or Apex REST APIs.
- Case updates are sent with assignment rules turned off, so they do not trigger your assignment rules.
- Live chat handoff to Salesforce Messaging for In-App and Web (Enhanced Chat) uses your Messaging deployment’s guest access, so it needs no extra object permissions.