Feature Request

Currently, the API key used in the KB widget JavaScript is visible within the widget code. When the KB widget is integrated into an application, anyone with access to the JS code can view the API key. Some of our customers have raised this as a security concern and have requested that the API key be encrypted. While we currently provide a Restricted Domains option to ensure that the KB widget is only installed on authorized domains, customers feel that this does not fully address their security concerns. Therefore, they have requested enhancements such as encrypting the API key or introducing a mechanism where the API key rotates or changes dynamically.

Detailed GitHub sync error reporting: Customer needs detailed error messages to be added in the extensions page (GitHub popup) when the system fails to sync files. Support relative image paths for local markdown preview: Update image path rendering to enable local preview support in markdown editors, allowing images to display correctly during offline or local editing. Support for syncing GitHub repos to multiple workspaces: Customer would like to enable seamless synchronization of GitHub repositories across multiple workspaces, allowing teams to manage and access shared code efficiently within different project environments.

The PDF export is unsuccessful when attempting to download over 500 articles in a single request.

When exporting a step by step guide article as PDF, instead of displaying the entire image the image is automatically being cropped to where the click was. Our expectation is to see the entire images to be included in the PDF.

Would it be possible to offer import of an eddy-ai-style-guide in PDF or docx format? We have a large style guide that we want to make available in doc360 but cut/paste from a PDF is problematic. Thanks!!

The Analytics Weekly report currently does not display the Dislike count, and it also lacks information regarding which workspace the data pertains to. It would be useful to include the Dislike count in the report and to customize the information so that it provides more accurate and detailed insights about the data referenced in this email.

When a user clicks on an article, the focus in the Category Manager shifts to another item. We expect the focus to remain on the article that was clicked. Thanks.

Feature Request Description: The Export as PDF option currently follows different workflows depending on where it is initiated: -> Article Level: When exporting a single article as PDF, the export process follows one flow. -> All Articles / Bulk Export: When exporting multiple articles or exporting from the All Articles section, the workflow differs. Requested Enhancement: Standardize the Export as PDF workflow so that the process remains consistent regardless of where it is initiated: -> From an individual article ->From the All Articles section ->From bulk article operations

We’d like to request support for customizable fields within the Ticket Deflector. Enabling the configuration of fields such as App ID, priority, issue type, and product area would allow end users to provide critical context during submission. These details should be passed through and included in the Zendesk ticket to improve visibility, reduce manual triage, and enhance overall support efficiency.

For our internal audits, we need to be able to identify readers not only by name and email, but also by the company they work for and/or their position. To do this, we would need the following: One or more additional data fields in the reader account where we can add custom information. An extension of the filter functionality to filter for custom information, such as a company name.