Admin Rights Required
This document applies to Chili Piper and Salesforce Admins.
Salesforce integration is optimal for any organization relying on Salesforce as its CRM. All visitor and prospect data between Chili Piper and Salesforce needs to be synced in real time.
In this article, we will quickly cover how to set up your integration and the minimum permission scope required for Global Sync users.
How to Setup?
To set up the integration and a Global Sync user, you will first need your Salesforce admin to connect Salesforce via the Integrations page in the Admin Center.
Once connected, you will notice a "Connected" flag, as shown in the screenshot below:
You can use the Reconnect button to reconnect the account for any reason or replace the current Global Sync user.
Salesforce Scope and Minimum Permissions
Below are the minimum Permission Sets (from a user profile level) for a User to Create the Chili Piper Account via Salesforce or for a User to become a Global Sync user:
Administrative Permissions
-
API Enabled
- To connect and interact with Chili Piper
-
View Setup and Configuration
- Required to view individual field accessibility permissions
- View app setup
-
View Roles and Role Hierarchy
- View role details for user lookup and profile data
-
View All Users
- For user sync
Standard Object Permissions
- Accounts: Read/Edit/View All
-
Contacts: Read/Edit/View All/Create
- Create is required if Chili Piper creates Contacts in your Salesforce instance.
-
Leads: Read/Edit/View All/Create
- Create is required if Chili Piper creates Leads in your Salesforce instance. Read/View is required for prospect lookups in Chili Piper, even if you are not using the Lead object in your workflows.
- Opportunities: Read*
- Cases: Read*
- Campaigns: Read/Edit/View All*
-
PushTopic: Create/Read/Edit
- This permission is only needed for Distro
*Only required if you are making use of this object type in Chili Piper (Cases, Opportunities, or Campaigns)
The related object inherits access to Events (Activities).
The connection user should have either "View All / Modify All" or "Modify All Data" for the related object to ensure the creation, editing, and deletion of Events is possible. Given the implications to security, we recommend using delegated object permissions with View / Modify on the object itself rather than Modify All Data.