Skip to main content

Anyone know why I cannot use a Salesforce dedicated “Integration User” license for the Salesloft → Salesforce Integration?

Salesloft is adamant about giving up a Salesforce User License

 

Hey Jorge,

 

Can you please explain what you mean by a dedicated Integration user? Are you looking for an operations seat? If you’re able to clarify on the above that would be awesome!

 

Thanks so much, 

 

Alice 

 


Hi @JorgeDiaz 

 

Salesloft CSM checking in to share more insight to your question above.

Salesloft requires a standard Salesforce license for the integration user to connect the two systems to ensure that the integration user has the necessary permissions to manage the integration effectively. You can find more on this subject in our Manage CRM Sync article. 

My understanding of SFDC’s Integration User is, it has limited permissions and is uneditable. Salesloft requires the user acting as the Main CRM Connector must have the following Permissions (as well as additional sharing settings):

  • Lead: “read,” “edit,” “create”
  • Contact: “read,” “edit,” “create”
  • Activity: “read,” “edit,” “create”
  • Account: “read,” “edit”
  • Opportunity: “read,” “edit”
  • Field Accessibility:
    • Read Access: Unidirectional Fields (CRM > Salesloft)
    • Read & Write Access: Bi-directional Fields & Unidirectional Fields (Salesloft > CRM)

 


@Salesloft_Rob , 

 

What happens when the Standard License User leaves the Organization? I would anticipate we would have to go back to the Integrations page within both systems to reinstate the connections and such. 

Integrations Users in Salesforce should have full Write capabilities and wherever need be, Custom OBJ/Custom Fields need to be configured for any User within SF (including SF Admin). 


@JorgeDiaz did you manage to get the integration user to work? Seems like it should. I’m about to set up the connection and will give it a shot.


@Salesloft_Rob, integrations users/profiles themselves are limited but you don’t edit them directly. You create a permission set with the appropriate permissions and attach that to the user which allows it similar access to a full, API-only profile.


Reply