Table of contents
Salesforce Setup
ClientSights connects to Salesforce using OAuth 2.0. Once authorized, ClientSights automatically sets up a private data channel in your Salesforce org and begins ingesting activity for all mapped users. Setup takes a few minutes and requires a Salesforce user with admin-level permissions.
ClientSights requires Enterprise Edition or higher. Professional and Starter editions do not support the data stream ClientSights depends on. If your org is on an unsupported edition, ClientSights will surface a clear message before the OAuth flow begins.
For a full explanation of how Salesforce activity appears in ClientSights, see Salesforce Integration Overview.
Step-by-Step Setup Instructions
Step 1: Pre-authorize ClientSights in your Salesforce org
Before connecting, a Salesforce admin needs to install and authorize ClientSights as an external app in your org. This is a one-time step required by Salesforce for all third-party integrations.
In Salesforce, go to Setup → External Client Apps and install ClientSights. Once authorized, proceed to connect from ClientSights.
If this step is skipped, the OAuth flow will fail before completing.
Step 2: Start the connection
- Go to Settings → Services
- Find Salesforce in the list
- Click Connect
Only Admins, Executives, and Owners in ClientSights can initiate this connection.
Step 3: Choose your environment
Select Production or Sandbox depending on which Salesforce org you are connecting. Most teams connect their production org. Use Sandbox for testing purposes only.
Step 4: Authorize ClientSights in Salesforce
Salesforce will display an authorization screen asking you to grant ClientSights access. You may see a security warning. This is standard Salesforce behavior for third-party integrations and does not indicate a problem with ClientSights.
The screen will list three permissions ClientSights is requesting:
- Access the identity URL service: used to identify the connecting user and workspace
- Manage user data via APIs: used to read record changes, field history, and user data. ClientSights cannot write to your Salesforce org
- Perform requests at any time: allows ClientSights to run background sweeps for field history and new records without requiring you to be logged in
Click Allow to proceed.
The user completing this step needs the Customize Application permission in Salesforce. This is typically available to System Administrators. If the connection fails with an access error, ask your Salesforce admin to complete this step.
Step 5: Wait for provisioning
After authorization, ClientSights automatically sets up a private data channel in your Salesforce org and subscribes the four default real-time features: Tasks, Events, Opportunities, and Cases. This takes a few seconds. You will be returned to the ClientSights integration page once it is complete.
The connection is named after your Salesforce org, for example “Acme Inc.”
Step 6: Review user mapping
Open the Users tab on the Salesforce integration page. ClientSights automatically maps Salesforce users to ClientSights users by matching email addresses.
Review the list and confirm that your active team members are mapped correctly. For any user that did not map automatically, use the dropdown to assign them manually. Users marked as unmapped will not have their activity attributed on the timeline.
Salesforce integration users, Chatter Free users, and system accounts are excluded automatically and will not appear in the mapping list.
Step 7: Review features and CDC slot usage
The Overview tab displays a Features panel showing all eleven feature areas and their current status. By default, ClientSights enables four features using real-time Change Data Capture: Tasks, Events, Opportunities, and Cases. The remaining Features (Accounts, Contacts, Leads, Notes, Email, and Comment & Updates) run on the 10-minute polling sweep.
If your Salesforce org already has CDC slots in use from another integration, some features may show a Blocked badge. See Salesforce Integration Overview for guidance on managing CDC slot limits.
To enable or disable specific features for individual users open the Features tab.
What Happens Next
Once the connection is established and users are mapped, ClientSights begins receiving Salesforce activity immediately via real-time CDC. The Field History and Delta sweeps run every 10 minutes and will backfill 30 days of history on first connection. Allow up to 10 minutes for that historical activity to appear on the timeline.
User mappings and feature settings can be reviewed and updated at any time from the Salesforce integration page. If you need a connection removed, contact us via in-app chat.