Proteus understands that your Salesforce Organization is business-critical and needs to be kept as simple as possible to minimize surface area for issues. Engage’s integration with Salesforce is designed to minimize the modifications and access necessary to your Salesforce Organization for a given use-case. Engage doesn't require you to install any custom Apex code nor requires any invasive changes to your Salesforce objects and fields. The following table summarizes the scope of access needed.
Reading data to load into an Engage Workspace. This includes loading Contact data.
(Optionally) Reading and/or updating fields in Salesforce to match Engage Workspace and/or Contact Labels
(Optionally) Reading data from Salesforce to show to your users in Engage’s Workspace Detail View - this data is fetched as needed to render to user and is not stored in Engage
(Optionally) Populating Salesforce activity feed with activity occurring on the Engage Workspace
(Optionally) Adding/updating contacts in Salesforce based on information that users provide via Engage
(Optionally) Update Opportunity Stage based on changes in Engage Workspace status
(Optionally) Reading a custom field to determine the initial status for Contacts loaded into Engage from Salesforce
Configure a Connected App in Salesforce for Engage as described here.
Connect a Salesforce User to the App (we recommend an API-only user).
The “View Workspace” and “Create Workspace” buttons for the Salesforce Account and/or Opportunity pages
Install a Salesforce Package as described here.
Push Topics are used to monitor Account, Opportunity, and Contact for updates
(Optionally) Engage can monitor other Salesforce objects for changes and respond via the Engage Trigger System.
None - this only requires the configuration described above for the REST API.
(Optionally) Embedding the Engage File Management component into Opportunity and/or Account pages to access and manage Engage Workspace files directly within Salesforce.
Component installed via a Salesforce Package as described here.
(Optionally) Engage can be configured as a SAML Service Provider so that your users can login to Engage based on their Salesforce user accounts (or any other SAML Identity Provider)