Configuring Salesforce connection to Census

There are a few considerations when setting up a new connection from Census to your Salesforce instance.

Salesforce required permissions

The objects and fields accessible to Census are all determined by the user account you use when connecting Census to your Salesforce instance. Census will have the same access as the user, so if fields are read-only or hidden for that user, they will be to Census.

In general, you should give Census read and write access to all the objects and fields you may want to update. If you are only using Salesforce as an ingest source, then we will only need read access. 

If you have extra Salesforce seat licenses, we recommend using a stand alone account for Census so you can see Census updates in your audit history. But this does come at additional cost.

In addition, Salesforce currently requires that the user account have the "View Setup and Configuration" permission (As of July 2019, this is a known Salesforce issue). Ensure this permission is set on the Profile assigned to this user under the "Administrative Permissions" heading of their profile.

Salesforce API access

Census uses a number of Salesforce APIs to request metadata about the objects, fields, and permissions configured in Salesforce. We primarily use the Salesforce Bulk API to sync data to Salesforce in the most API quota efficient way possible. 

Using a Salesforce Sandbox

Census supports Salesforce Sandbox instances as well. Note that Sandboxes have their own set of user accounts and you may need to create a new account for Census to replicate permissions. Any time a sandbox is refreshed from production, the account will need to be recreated and the Census link re-authorized.