Feature Request

We are trying to embed the Ask Eddy widget into a new application. We found the product enforces Cross Origin Embedder Policy (COEP) as part of the product’s security baseline, and this configuration cannot be changed. With COEP enabled, browsers require all cross origin resources such as Document360 to explicitly allow embedding. Currently, the Document360 widget assets do not include the Cross Origin Resource Policy header required for this scenario, which results in the widget being blocked. To support COEP enabled applications, the Document360 widget assets need to include the following response header: Cross-Origin-Resource-Policy: cross-origin Thank you.

Prospect is expecting Decision tree also in KB widget like we have provided Ticket deflector as a new tab This will allow the users to have a Decision tree inside their application and get used to the platform better.

The customer reported that the KB widget takes around 8 to 10 seconds to load on the first login and requested faster performance. They expect the widget drawer to open instantly and the content to load within 2 seconds.

For widgets configured with JWT, categories and articles are displayed based on the reader group ACL. However, the reader group ACL is currently not enforced for internal link navigation within the widget. As a result, even though users do not have access to certain restricted articles, those articles can still be accessed if they are linked within another article.

Customers expect the “Open in New Tab” option to work consistently for both Documentation and API Documentation links, including cross-workspace navigation. Currently, this behavior is limited to API Documentation, causing navigation issues and 404 errors. The request is to extend this functionality to all documentation links to ensure seamless and consistent user experience.

When editing a widget, toggling the JWT option (enable or disable) causes the widget JavaScript to update immediately and regenerates a new API key, even when no explicit save action is performed. This behavior can result in the widget returning 401 Unauthorized errors in production environments if the newly generated API key is not updated in the embedded widget code. Additionally, API key regeneration triggered by this action is not recorded in Team Auditing logs. Currently, audit entries are created only when changes are followed by an explicit save action, which makes it difficult for customers to track when and why an API key was changed. Improving visibility and consistency around API key changes would help customers manage widget integrations more reliably and avoid unexpected production issues.

Currently, when a user is reading an article within the widget and clicks a link to another internal article, pressing the Back button takes them back to the category tree instead of the previous article they were just viewing. This breaks the user’s reading flow and feels unintuitive — users expect to return to the previous article, not the category list. Proposed Enhancement: Update the widget’s navigation logic so that when an internal article link is clicked: -> The Back button takes the user back to the previous article, not the category tree. -> Only when the user reaches the first article in their navigation history should the Back button return to the category tree.

Currently, the articles created using step by step guides are visible only through the site and it is not visible in the widget. It would be great if we could have this functionality in the widget as well.

Posting on behalf on Cycode. They use URL mapping a lot and have requested to have a sorting feature as they are unable to find the URL mapped names. Their reqyest is to have a basic alphabetical ordering alongside sorting options which should also includes dates. This way, they needn't scroll through all the pages to find one.

When Eddy AI is used on the published site, a blinking cursor appears while the answer is being fetched. That gives users a clear signal to wait. In the KB widget, there is no such indication. The customer needs to add a loader or similar visual in the widget AI flow to show that the system is retrieving a response.