Skip to main content
Search

Embed your own search platform in CC


Yoeri
Forum|alt.badge.img+3
  • Gainsight Employee ⭐️⭐️⭐️
  • 392 replies

The CC search engine allows your community members to search through all relevant content in your community. With the out of the box federated search integrations you can also easily push external content into the CC search engine.

We are seeing companies building their own unified search experience across various customer channels (community, academy, documentation) with their own (third-party) search platform. These companies want to use their own search solution in the CC instead of using CC default search engine.

This article provides a high level description on what steps need to be taken to disable CC’s default search engine and how to embed your own search platform.

How to embed your own search platform on CC

Embedding your own search platform in CC requires technical work. We highly recommend you to get assistance from your developer resources if you are looking into this!

If you want to bring your own search you will need to do two things:

  1. Disable CC’s default search
  2. Embed your own (third-party) search functionality in the CC using a custom header

Disable CC’s default search

Throughout the CC you will find search actions (in the hero banners and in the main navigation). You will need to disable/hide these search actions using Custom CSS.

Example of search bar on the homepage

Embed your own (third-party) search functionality in the CC platform using a custom header

After you have disabled the CC search actions you will need to embed your own search bar into the platform. We recommend you to create your own custom header and within this header include your own search bar. You can either add your own custom header to the CC by directly inserting your own HTML/CSS or by inserting an SSI file.

Example of custom header with a custom search box

Limitations

  • Community members will be taken away from the community when they search in your own search functionality because your search result pages will live outside of the CC.
  • Community members can’t find hidden/gated content because external search solutions can’t know wether a user has permissions to view certain content or not.
Did you find this topic helpful?

2 replies

  • Contributor ⭐️
  • 1 reply
  • September 6, 2022

Hey @Yoeri ! This looks great and we’d love to build it in our community. Do you know if there are any plans to fix the limitations?

Thank you ! :)


Yoeri
Forum|alt.badge.img+3
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • 392 replies
  • September 7, 2022

Custom pages, as announced in our latest roadmap update, will allow you to embed search results from third-party search vendors on a custom page in our platform (e.g. community.com/searchresults). 

The second limitation can not be solved by inSided solely - third-party search vendors need to know which user is searching and what the permissions of this user are in order to serve gated content. This requires an integration between inSided and the third-party were user information and permissions are shared. This kind of integration has to be build on both ends (inSided and third-party search). There are currently no plans to looks in this. You can read our latest roadmap plans on: 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings