For the complete documentation index, see llms.txt. This page is also available as Markdown.

Determine the Salesforce integration user

This section describes the access permissions required for the Salesforce user that you will use to authenticate to Salesforce.

Authentication Type

The integration uses OAuth 2.0 Authentication.

How the Connection to Salesforce is Established

  1. In SlapFive Settings, you click Integrations > Salesforce Connection, then click the Connect button.

  2. The Integration Server redirects you to the Salesforce login page, where you log in as your Integration User, typing the username and password.

  3. Salesforce authenticates you and asks for consent.

  4. Salesforce issues two tokens:

    1. Access Token - short-lived, used to make API calls.

    2. Refresh Token - long-lived, used to get new access tokens when the old one expires.

  5. The Integration Server stores the Access Token and Refresh Token encrypted in its vault.

NOTE: No usernames or passwords are ever stored in SlapFive. The Integration Server uses the Refresh Token to silently refresh Access Tokens in the background, without needing the password again.

Integration User Permissions

The Embedded Integration with Salesforce requires you to establish a Salesforce Connection using a Salesforce Integration User with these permissions:

Object
Permssion Type
Permission

Opportunity

Object-level

Read, View All

(View All is needed for any automated workflows that listen for specific field changes on Opportunities, such as the referral automation.)

Field-level

  • Edit access to the 4 SlapFive custom fields: Influence Count, SlapFive Influence, SlapFive Influence Score, and SlapFive Program.

  • Read access to all fields referenced by the SlapFive integration, including any fields configured for synchronization or monitoring: Opportunity Name, Id, Description, Stage, Is Closed, Is Won, Amount, Created Date, Close Date, Type, Lead Source, Account ID.

  • Remove or bypass any field validation rules defined for the Salesforce Opportunity object for this user. Example: "You cannot move this Opportunity to Stage 2 without selecting a Meeting Outcome".

Record-level

View All object permission is recommended. If not granted, the Integration User must have record-level visibility to every Opportunity that may be synchronized with SlapFive.

Account

Object-level

Read, View All

Field-level

Read access to all fields referenced by the SlapFive integration, including any fields configured for synchronization or monitoring, such as Industry or Size.

Record-level

View All object permission is recommended. If not granted, the Integration User must have record-level visibility to every Account that may be synchronized with SlapFive.

Contact

Object-level

Read, View All

Field-level

Read access to all fields referenced by the SlapFive integration, including any fields configured for synchronization or monitoring, such as Title or LinkedIn Profile.

Record-level

View All object permission is recommended. If not granted, the Integration User must have record-level visibility to every Contact that may be synchronized with SlapFive.

SlapFive Customer Influence

SlapFive Customer Influence Activity

SlapFive Customer Activity

SlapFive Board

SlapFive Company

SlapFive Contact

SlapFive Story

Object-level

Read, Create, Edit, Delete

SlapFive Customer Influence

3 Record Types

Read and Edit

SlapFive Customer Influence Activity

3 Record Types

Read and Edit

Field-level

Read and Edit access to all fields

Record-level

Access to all records.

The Integration User needs these system permissions to enable the real-time listening for Opportunity, Account and Contact record changes to sync to SlapFive, as this requires CDC registration:

In addition, the Integration User needs access to the setup objects used by the SlapFive Salesforce App:

Restrict Integration User to IP addresses or ranges

If your company requires your Salesforce Integration User to be restricted to specific IP addresses or ranges, your Salesforce Admin needs to add these IP Addresses to the Login IP Ranges for the Integration User:

Last updated