In most environments, Riva is deployed with the "use impersonation" connection option enabled in the sync policy. In those deployments, the typical configuration involves creating
This article describes management tasks for target users:
Riva for Exchange and Salesforce using SSO - There are some differences with managing target Salesforce users when Riva is configured to the Single Sign-On (SSO) feature in Salesforce. See Manage target Salesforce users in an SSO-enabled Riva environment.
To temporarily disable and re-enable data sync for all target users in a sync policy, use these procedures:
Disable a sync policy to stop data sync to all target users of that policy. On the first full sync cycle after the policy is disabled, Riva stops syncing the target users.
Enable a sync policy to start data sync to all target users of that policy. On the first full sync cycle after the policy is enabled, Riva starts syncing the target user.
Use these procedures to temporarily disable and re-enable data sync for a specified user.
To temporarily stop syncing to a specific user, remove the user from the assigned sync policy. On the first sync cycle after the policy is saved, Riva stops syncing data to the removed user.
Note: The removed user remains visible in the user queue in the Riva Service Monitor application until the service is stopped/started or restarted.
To re-enable sync to a target user previously removed, re-assign them to the sync policy. On the first sync cycle after the policy is saved, Riva starts syncing data to the re-enabled target user.
Overview of the process:
For detailed instructions, see Remove user(s) from Riva sync policy and reset the license count.
You can add users to a sync policy after completing the initial testing and possibly modifying the sync policy so that you are satisfied that Riva is syncing data between the email system and the CRM as expected.
There are two methods to add users to be synced by Riva:
To prevent possible duplication of records or sync errors, ensure that you follow the correct procedure:
Article ID: 566
Last updated: 09 Oct, 2018