This article describes how to prepare a Riva connection account, the Salesforce account, and the Riva server to support a Riva standard impersonation connection to Salesforce.
To prepare Salesforce for the Riva sync:
From the Windows system that will host Riva (see system requirements), confirm that you can log in to Salesforce by using an admin account and a normal user account.
The Salesforce administrator can choose to set up trusted network access, so that Salesforce user security tokens are not required. For instructions, see Enable trusted network access for Riva On-Premise.
Riva needs to use the credentials of a Salesforce user account that has been assigned to the System Administrator Profile:
Security policies for some organizations require assigning the Riva connection user to a custom Salesforce profile to limit permission assignment, in which case the permissions assigned to that Salesforce profile must meet the minimum Riva requirements. For more information, see Verify Salesforce "connection user" permissions.
(Riva 2.4.47 or higher.)
To enable Riva to authenticate to Salesforce with OAuth:
For each user that Riva will sync data for, ensure that the primary email address for each target Salesforce user account matches the primary SMTP Reply-to email address of the corresponding user mailbox.
Step 7: Add Custom Fields to Salesforce for Riva
The Riva connection to Salesforce uses the Standard Impersonation Model: Riva uses the permissions of the CRM user configured in the Riva Salesforce connection to create and modify items and data in the CRM. When Riva creates new items or modifies existing items in the CRM, Riva assigns ownership to the end user. But, by default, because the actions are being performed by the Riva connection user, the audit fields in CRM record the Riva connection user as the user that created and modified the item.
The following information is required when you create the Riva connection to the Salesforce organization.