Installing the Peerbound Salesforce app

The Peerbound app in Salesforce allows Peerbound to periodically sync data from Salesforce into Peerbound.

Peerbound supports two different authentication methods when setting up the Salesforce integration. Have your Salesforce admin configure Salesforce permissions as described in one of the sections below. Then, finish the installation in the Peerbound web app on the Integrations page.

Certificate-based server integration (recommended)

Also called the JWT Bearer Flow in Salesforce documentation.

With this integration method, a Salesforce admin will configure an integration user for Peerbound in Salesforce, assign it the appropriate permissions, and name the user as a permitted user for the Peerbound integration app. Then, in the Peerbound web app, you will just need to enter the username of that integration user and Peerbound will be able to sync your data.

We are able to securely sync data with Salesforce because our servers are able to share a certificate with Salesforce to prove our identity.

Here's what you need to do as a Salesforce admin:

1. Install the Peerbound app. Once approved by Salesforce, our app will be installed directly from the AgentExchange marketplace. While we are still awaiting approval, the app can be installed by following this link and logging into your Salesforce organization: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tiw0000029OhtAAE. Choose the "Install for Admins Only" option.

2. Create Permission sets with the permissions needed by the Peerbound integration.

   1. Create the Peerbound Integration User permission set.

      1. Go to Setup > Permission Sets. Click "New". Name the permission set "Peerbound Integration User". Select "Salesforce API Integration" as the License type. Save.

      2. Back on the Permission Set page for Peerbound Integration User, click on Object Settings in the Apps section. We suggest granting View All Fields permissions below for simplicity, but you can remove access to custom fields that won't be used in Peerbound.

         1. Click Accounts and grant Read, View All Records, and View All Fields permissions.

         2. Click Contacts and grant Read, View All Records, and View All Fields permissions.

         3. Click Opportunities and grant Read, View All Records, and View All Fields permissions.

      3. [Needed only if using Peerbound Measure's module to analyze emails.] Back on the Permission Set page for Peerbound Integration User, click on System Permissions in the System section.

         1. Click Edit. Check the box next to Access Activities in the System section. Check the box next to View All Users in the Users section. Save.

   2. [Needed only if using Peerbound Measure's module to analyze emails.] Create the "Peerbound Integration User (Task access)" permission set. Permission sets with the Salesforce API Integration license type cannot be directly assigned access to the task object, so a separate permission set needs to be created for it.

      1. Go to Setup > Permission Sets. Click "New". Name the permission set "Peerbound Integration User (Task access)". Leave the License selection as "--None--". Save.

      2. Back on the Permission Set page for "Peerbound Integration User (Task access)", click on Object Settings in the Apps section. We suggest granting all fields permissions below for simplicity, but you can remove access to custom fields that won't be used in Peerbound.

         1. Click Tasks and grant Read Access to all fields.

3. Create a new integration user for Peerbound.

   1. Go to Setup > Users. Click "New User". Fill in the name and email according to your preferences / conventions, but be sure to select "Salesforce Integration" as the User License and "Minimum Access - API Only Integrations" as the Profile.

   2. Take note of the Username because you will need this when doing the integration in the Peerbound web app.

4. Assign the user a Salesforce API Integration license.

   1. On the setup page for the Peerbound integration user you just created, scroll down to the Permission Set License Assignments section. Click "Edit Assignments". Check the box next to Salesforce API Integration. Save.

5. Assign the permission sets to the integration user.

   1. On the setup page for the Peerbound integration user, scroll down to the Permission Set Assignments section. Click "Edit Assignments". Add the "Peerbound Integration User" and (if applicable) "Peerbound Integration User (Task access)" permission sets. Save.

6. Configure policies for the Peerbound External Client App.

   1. Go to Setup > External Client App Manager. Select the Peerbound app. On the Policies tab, click Edit. In the OAuth Policies section, update the Permitted Users selection to "Admin approved users are pre-authorized". Then, in the App Policies section, add "Peerbound Integration User" and (if applicable) "Peerbound Integration User (Task Access)" to the Selected Permission Sets. Save your changes.

7. Back on the Integrations page in the Peerbound web app, a Peerbound admin will enter the salesforce username

Credentials-based server integration

Also called Web Server Flow (Authorization Code) in the Salesforce documentation.

While this integration method might be quicker to get started with, it requires occasionally re-authenticating, so we strongly recommend moving toward the certificate-based setup as soon as convenient.

1. Install the Peerbound app. Once approved, our app will be installed directly from the AgentExchange marketplace. While we are still awaiting approval, the app can be installed by following this link and logging into your Salesforce organization: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tiw0000029OhtAAE. Choose the "Install for Admins Only" option.

2. Configure policies for the Peerbound External Client App.

   1. Go to Setup > External Client App Manager. Select the Peerbound app. On the Policies tab, click Edit.

   2. In the OAuth Policies section, update the Permitted Users selection to "Admin approved users are pre-authorized".

   3. In the simplest setup, you already have a Salesforce User with all the required access. Assign a profile that's been assigned to that user in the Select Profiles section under App Policies. A better practice is to create a dedicated integration user for Peerbound and build the permission sets as described for certificate-based authentication. Once you've gone through the process of configuring the proper integration user and permission sets, we strongly recommend using the certificate-based setup rather than using this credentials-based setup.

   4. Save