Install a Search Client in Salesforce Communities (Lightning)

In this article, you will learn how to replace the default Salesforce component Search Results with a SearchUnify package, which on top of being native, can fetch results from your entire org and external sources, such as your organization's YouTube channels, Slack discussions, and GitHub repositories. The installation takes only a few minutes but goes a long way in enhancing user experience.

Comparison of Search Results Component and SearchUnify Package

When users are confronted with thousands of posts and articles, most choose to run a search. Navigation seems old school to many. As a Salesforce admin, you can improve user experience by replacing the default Search Results component with a powerful SearchUnify package. This table summarizes the key differences between the both.

  Search Results (Component) SearchUnify Package
Default Component Yes No
Native Support Yes Yes
Global (Org) Search No


Objects Supported Articles, Discussions Articles, Discussions, and all other standard and custom objects
Results from External Sources No Yes

Enable SearchUnify Search on Salesforce Communities

Create a Salesforce Lightning Search Client

  1. Ensure that Salesforce Communities are enabled. Skip this step if you already have a community.
  2. Create a Salesforce Lightning search client.
  3. Configure the Salesforce Lightning search client.

Install SearchUnify Package

  1. Unzip the search client and open readme.
  2. Copy the link to the search client package.

  3. Paste the link in your browser window and install SearchUnify Lightning Community for All Users.

  4. Click View in another browser for configuration.

Connect Salesforce Org with SearchUnify Instance

The data flow between SearchUnify and your Salesforce org is managed through Remote Sites, of which two must be created before you can proceed with configuration. For instructions, check out Create Remote Sites in Salesforce.

Process SearchUnify Package

  1. Select your community for configuration from the drop down.

  2. Copy the Service Endpoint and UID from readme. (Install Search Client, Step 4)

  3. Enter your Service Endpoint (in readme.txt), Provision Key (in readme.txt), and UID. Also enter the page where the search results will be displayed.

    Important. The Provision Key will be shared by your SearchUnify representative.

    Important. Select or create a page with full-width and only one column. The page name should be limited to lowercase letters and hyphens. Spaces are not allowed.

  4. Click Process.

Insert SearchUnify Search Component to a Community Page

  1. Open your community in the Builder mode. (From Setup, go to All Communities through Quick Find Box, and click Builder.)
  2. Move to Security from .
  3. Select Allow Inline Scripts and Script Access to Whitelisted Third-party Hosts from the Script Security Level dropdown.

  4. Click from the sidebar, select Theme, and enter Configure.

  5. Click , and from the Search Component drop-down select SUAuthBanner_1234 (where 1234 are the first four digits of your UID).

  6. Drag SUAuthSearch_1234 (where 1234 are the first four digits of your UID) to the Content section of the page you have selected or created.

You have successfully installed SearchUnify on Salesforce Communities.

Further Customization (Optional)

Besides SUSearchUnifyHeaderDymamic and SUBannerComponent, SearchUnify Lightning Community offers the following components. Use them to further enhance user experience.

  • SUListComponentDynamics for customizing search results pages. Its attributes are pagesize, modalOpen, pageHeaderTitle, gotoSearchPageText, noResultFoundMsg, openNewTab, showMetadata, and showResultbody.
  • SUSearchComponent_< first_four_value_of_search_client > provides five attributes: noSearchResultFoundMsg, defaultFilterCollapse, defaultSearchPage, pageSize, and searchString.
  • SURecommendedDataDynamic to manage recommendations. Its attributes are recommendedHeading and pageSize.
  • SU Ltng Analytics on Case provides search data of the user who has raised that case.

Last updatedFriday, September 4, 2020