Feature Request

Possibility to change the size and the shape of the in-app icon.

As a user, I would like to request the ability for the Knowledge base assistant to be localized for different languages. This would allow me to access the information and assistance provided by the assistant in my preferred language, making it more accessible and easier to use for non-English speakers.

These buttons should show at the bottom of articles in the widget same as in the full documentation view. We have many articles which are broken into sub-chapters as separate articles, because the next/previous buttons work well for indicating there's more related stuff - but when opening the article in the KB widget (assistant) we don't see these buttons.

To provide our users additional context, it would be great to include glossary terms in article lists in the knowledge base widget.

Customer is trying to embed Kb Widget within their product and experiencing an issue due to CSP defined on their end. Customer would like to consolidate the below services to one destination hosted by us. Below are the details. Document360.io Algolianet.com Jquery.com Jsdelivr.net Gstatic.com Fontawesome.com Googleapis.com

Currently, when we enable or disable the JWT toggle for the widget, the API key changes for that particular widget. As a result, if the widget has already been installed, it disappears from the Knowledge Base site or third-party application, displaying an "Invalid API token" error in the console. It would be helpful for the users if we display a warning message while disabling/enabling the JWT toggle in the widget settings. This will make sure that the users are cautious while enabling/disabling this JWT option in the widget.

We would like all icons to be sourced from the same icon set for the KB widget. Specifically, we would like to update the move icon, close icon, and magnifying glass in the search bar to match the style of the back and expand icons.

I would like Document360 to reconsider this design choice, as it can cause confusion for users. To enhance the user experience, the back arrow should be displayed when an article is expanded in the KB widget, allowing users to navigate back a screen and avoid feeling stuck. Given its small size, this button shouldn't significantly distract from the main content.

In the KB assistant/widget, enlarge images when clicking on them

We are currently testing the widget implementation of our help center content and have provided feedback on an article. However, in the feedback manager, there is no indication that the feedback came through the widget. It would be very useful to have visibility into whether feedback is submitted through the widget or from the help center page outside of the application.