The new version of our Salesforce integration is now available. System admins can follow the steps below in order to give your organization access to within Salesforce.

AppExchange Marketplace listing:

Demo video:

Migrating from version 1? Follow the instructions here first: Migrating from legacy to v2.

Install the app

Search for '' in the AppExchange Marketplace and select our application.

Follow the install guidance and complete the information until you see the screen below. Select Install for All Users at the install page.

This will allow all users to access the application after permissions have been granted within Salesforce (as shown later). The install process will take a few minutes.

Verify that the app has been installed by searching for in the App Launcher search bar.

Click on either option and the below screen should appear.

This is expected and verifies that the application has been installed correctly. The next step is to give appropriate access to the users in your organisation (including admins).

Grant access to Users

Go to Setup and search for App Manager. Select Manage for the CobrowseIOWebApp as shown below.

Select Edit Policies and change Permitted Users to "Admin Approved users are pre-authorized" and then Save.

Managing access using Salesforce Profiles

If you manage access using Salesforce Profiles within your organisation to access then follow the steps below. If you instead require Permission Sets, skip to the next section.

Next select Manage Profiles from the Profiles section of the Manage page display.

Within the Manage Profiles options select System Administrator and other profiles (e.g. Standard User) and then Save.

Search in the App Launcher search bar again and go back to the dashboard by selecting either option.

The dashboard should now be visible to permitted profiles.

Managing access using Salesforce Permission Sets

If you manage access using Salesforce Permission Sets, then follow the instructions below. Otherwise, use the previous section to enable using Salesforce Profiles.

Due to an underlying Salesforce restriction, you need to clone the Permission Sets that are shipped with our App when it is installed in order to enabled them.

To do this, go to your organisation's Permission Sets tab and Clone the Agent and Admin Permission Sets.

Note: you may change the name of the cloned permission sets, but you should not make any other changes.

This will mean that two Permission Sets for both Agent and Admin appear, this is expected.

Go back to the App Manager and manage CobrowseIOWebApp again. Select Manage Permission Sets and add both of the cloned Agent and Admin Permission Sets to the App. The correct ones are the ones that are able to be added, the non-cloned ones will show an error message.

Next, simply add the relevant Permission Sets to the Profiles or Users who you wish to access

Make sure to correctly add the appropriate Permission Set (either Admin or Agent).

If your users have custom user profiles, then you need to add both the original and cloned Permission Set to your users, e.g. Agent and Agent (cloned) Permission Sets for each agent who does not have admin rights.

The application will now appear to your agents and admins who have been granted the correct permissions.

You can add the widget to your record pages for Cases, Contacts, Accounts, or any other record pages accessible via Sales Console, Service Console, or otherwise.

To do this, navigate to the page you would like to add the widget to and click the settings button in the top right to "Edit Page".

You can then drag and drop the Sidebar managed component (from Custom - Managed on the left) into the location of your choice and Save.

The sidebar widget should then be displayed in all of the pages that it has been added to.

Configuring Account Settings

Account Settings can be configured by an admin user by going to the application and clicking on the Account Settings icon.

If you migrated from v1, then your account settings will have been preserved.

Add our SDKs to get started!

See Getting started to add our SDKs and begin end-to-end testing! Your license key can be found in your Account Settings, seen above.

Filtering devices using Salesforce Record metadata (optional)

This step is optional for clients who wish to override the default device filtering in the Sidebar widget. For example in Cases and Contacts, the sidebar widget will filter by devices that match the end user's email address by default.

In Salesforce legacy, this filtering was provided in the Settings tab. It is now located within the Dashboard. Go to Dashboard (e.g. via App Launcher search) then Account Settings (Admins only), then Integrations, then Salesforce record Mapping.

The first argument specifies the page for the filtering to be applied to, e.g. "Case". Then the key:value pair specifies the SalesforceMetadata:Cobrowse.ioCustomData that should be mapped together, linking the Salesforce metadata from a page to the corresponding custom data field to filter the devices.

In the example above (and by default), "ContactEmail" in Salesforce is mapped to "user_email" in custom data. This means that "ContactEmail" filters the devices shown on the "Case" pages.

This information must match the correct metadata to work, and it must be formatted in correct JSON (as the other examples are).

See for more information on using custom data to identify your devices.

If you have any questions about the above steps then please get in touch at!


Granting multiple users Admin role permissions

As part of the install, you may need to grant multiple users the Admin role permissions within, e.g. so that they can see all agents' session history. This should happen automatically, but if it does not work then it can also be done manually.

Simply go the User's profile within Salesforce via Setup then Users and Users again. Select the User and inspect their Permission Set Assignments. Edit Assignments and add the Admin permission set to their profile. They will then have Admin rights which can be verified in the Dashboard.

Last updated