Table of contents
Salesforce Setup
WorkSights connects to Salesforce using OAuth 2.0. Once authorized, WorkSights 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.
WorkSights requires Enterprise Edition or higher. Professional and Starter editions do not support the data stream WorkSights depends on. If your org is on an unsupported edition, WorkSights will surface a clear message before the OAuth flow begins.
For a full explanation of how Salesforce activity appears in WorkSights, see Salesforce Integration Overview.
Step-by-Step Setup Instructions
Step 1: Start the connection
- Go to Settings → Services
- Find Salesforce in the list
- Click Connect
Only Admins, Executives, and Owners in WorkSights can initiate this connection.
Step 2: 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 3: Authorize WorkSights in Salesforce
Salesforce will display an authorization screen asking you to grant WorkSights access. You may see a security warning. This is standard Salesforce behavior for third-party integrations and does not indicate a problem with WorkSights.
The screen will list three permissions WorkSights 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. WorkSights cannot write to your Salesforce org
- Perform requests at any time: allows WorkSights 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 4: Wait for provisioning
After authorization, WorkSights automatically sets up a private data channel in your Salesforce org and subscribes the five default features: Tasks, Events, Opportunities, Cases, and Contacts. This takes a few seconds. You will be returned to the WorkSights integration page once it’s complete.
The connection is named after your Salesforce org, for example “Acme Inc.”
Step 5: Review user mapping
Open the Users tab on the Salesforce integration page. WorkSights automatically maps Salesforce users to WorkSights 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 6: Review features and CDC slot usage
The Overview tab displays a Features panel showing all eleven feature areas and their current status. By default, WorkSights enables five features using real-time Change Data Capture: Tasks, Events, Opportunities, Cases, and Contacts. The remaining Features (Accounts, 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, WorkSights 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.