Salesforce Requirements and Permissions

Primer uses minimal field mapping to connect Primer's third-party data with your Salesforce records, enhancing your CRM advertising efforts.

Primer's integration with Salesforce prioritizes security, ensuring your data is protected. If you have questions about security, our customer support team can offer a clear explanation of how we maintain safety during the integration.

Permissions

  1. "API Enabled" must be checked

  2. "Session Security Level Required at Login" must be set to "None".

  3. High Assurance on Session security level required at login should be set to "Disabled" at the profile level. Salesforce blocks some API access when this setting is used on user Profiles and this will prevent Primer from accessing your Salesforce instance.

  4. Primer will have the same access to objects and fields as the Salesforce user connected to Primer. So if fields are read-only or hidden for that user, that is what Primer will reflect.

    1. For text fields, the fields should be set as 'text' only as opposed to 'text area' fields.

    2. You should give Primer "Read" access to the "Lead," "Contact," "Opportunity," and "Account" objects. Primer does not currently delete any records, and we will never delete or overwrite data.

    3. Additional functionality for bulk import is available with allowing access to "Campaign" objects.

  5. Salesforce requires that the user account have the "View Setup and Configuration". Ensure the user account have the "View Setup and Configuration" permission. This permission is set on the Profile of the connected user under the "Administrative Permissions" heading.

  6. When connecting, the Salesforce authorization flow will request scopes api and refresh_token.

We recommend using a stand-alone account specifically for Primer (often called a Service Account) so you can see Primer updates in your audit history.

Object Permissions

PreviousConnecting Salesforce to PrimerNextSalesforce Data Ingestion

Last updated