Configuring Coveo for Salesforce

The Coveo for Salesforce configuration page allows you to configure your search and the related actions to your Coveo for Salesforce organization.


Accessing the Configuration Page

  1. Ensure that you have the right permissions to access the configuration page (see Accessing the Coveo for Salesforce Configuration Pages).

  2. In the Setup menu, search for and click Installed Packages.

    Lightning Experience
    Salesforce Classic
    Under Platform Tools, select Apps > Installed Packages. Under Build, select Installed Packages.
  3. In the Installed Packages list, next to the Coveo package, click Configure.

Configuring Your Coveo for Salesforce Organization

In the Coveo for Salesforce Configuration page, you can:

Using the Advanced Configuration Page

Modifying these settings can negatively impact your content privacy. You are strongly discouraged from modifying these options unless instructed by Coveo Support.

With the Free Edition

The Advanced Configuration allows you to configure the JWT Flow (see Understanding How Coveo Uses the JWT Flow).

With the Pro Edition


  • To manage the profile used for your search queries before logging in, select one of the following options:

    • Anonymous Profile: queries present content based only on the currently logged in Salesforce user.

    • QueryingUserProfile: queries present content available to the user performing the query and to the default querying user profile.

      Prior to the May 2017 release of Coveo for Salesforce (v2.41), the Anonymous Profile and the QueryingUserProfile were reversed, meaning that the description for the Anonymous Profile applied to the QueryingUserProfile and vice versa.

  • Coveo for Salesforce 3.42 (November 2019) To manage the Coveo Global DNS (Multi-region) support, choose whether you enable the Multi-Region Deployments. You have to enable this option if you want to take advantage of your multi-region deployments.

  • To manage the information sent to Coveo Analytics, select one of the following options:

    • Entire E-mail address: the e-mail address of the user is hashed before being sent to Coveo Analytics.
    • E-mail username: the first part of the e-mail address is hashed, while the second part is not.
    • Nothing: the e-mail address is left intact when sent to the Coveo Analytics. This is the default and recommended option.

      Hashing the e-mail address may lead to your users essentially querying only publicly available content.

Recommended Articles