Skip to main content
Solved

Zendesk federated search - restricting content indexed


With the Zendesk Knowledge Base integration we’ve noticed that articles published internally end up being indexed in the community search even though they should not be accessible publicly.

Is there a way to setup the integration to avoid those being indexed and only published content being accessible?

Best answer by adrienne

Thanks for the nudge, Scott. At present, it seems the answer is no. There doesn’t seem to be an 'automated' way to do this via Zendesk’s articles/search API, so I don’t believe there’s any way to exclude the content on our side. I have, however shared this feedback with the engineers, so they are aware of this limitation. 

View original
Did you find this topic helpful?

5 replies

  • Helper ⭐️⭐️
  • 9 replies
  • August 19, 2021

Hi Scott,

Yes, you are able to determine which content you would like indexed by our Federated Search integration. To do this head to Control > Integrations > Zendesk > and expand the Federated Search card to find Filter by Category.

From there, you can enter the category IDs of the categories that you want to show in federated search, separated by a comma (e.g. 123564, 123721) – you can find the category ID in the URL, it’s the number directly after /categories/

Please note: Advanced filters can only be configure when Federated search is Disabled.

For additional information, see below:

Hope this helps!


  • 0 replies
  • August 19, 2021

@adrienne thanks -- in this case it was published to an existing category but published internally vs. externally. Ideally we’d have a way to hide the internally accessible content even if in a category we make publicly available.


  • Helper ⭐️⭐️
  • 9 replies
  • August 19, 2021

Ah, I see, thanks for the clarification! Let me investigate a bit further here.


  • 0 replies
  • September 22, 2021

@adrienne any updates you can provide on this?


  • Helper ⭐️⭐️
  • 9 replies
  • Answer
  • September 24, 2021

Thanks for the nudge, Scott. At present, it seems the answer is no. There doesn’t seem to be an 'automated' way to do this via Zendesk’s articles/search API, so I don’t believe there’s any way to exclude the content on our side. I have, however shared this feedback with the engineers, so they are aware of this limitation. 


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