Feature Request

Preview: Currently, the Smart Bar preview displays only a sample placeholder line instead of the actual content entered by the user. The customer would like the preview to display the actual Smart Bar content. Character Limit: Currently, the Smart Bar has a maximum limit of 250 characters. The customer would like the character limit to be increased or made configurable, as they previously used more than 250 characters in a single Smart Bar.

The chatbot currently does not display source references, and it would be very helpful if it could provide citations similar to those shown in Eddy AI Search.

I want to be able to report on how many articles a user contributed to that got published in x time frame. I want to see if those articles were new vs edits of existing articles. The way that it is only contributions that are shown on a user level is not enough. I also want to see the list of articles that each user contributed to. Currently when you click into the user it doesn't apply time filter that was already applied to the list view. We are trying to understand better each user's performance over a month and a quarter and it's very hard and manual to pull all these details.

When replicating articles from one workspace to another, hyperlinks within the replicated content continue to point to the original workspace instead of updating to the corresponding articles in the destination workspace. This is a significant issue for organizations that maintain multiple workspaces for different customer bases. Readers who only have access to the destination workspace (workspace 2) cannot access the linked content because the hyperlinks redirect them to the source workspace (workspace 1), which they do not have access to — even when the linked articles have already been replicated to workspace 2. Example: Article A is replicated from workspace 1 to workspace 2 Article A contains hyperlinks pointing to Article B in workspace 1 Article B has also been replicated to workspace 2 However, the hyperlinks in the replicated Article A still point to Article B in workspace 1 Readers in workspace 2 cannot access workspace 1, so the links break for them Expected behavior: When an article is replicated to a destination workspace, any hyperlinks pointing to articles that also exist in the destination workspace should automatically update to point to the correct articles within that workspace. Impact: This is causing a poor reader experience for customers who are scoped to a specific workspace and do not have access to the source workspace.

Zendesk is deprecating API tokens, which are currently required for the Document360 Federated Search integration. Requesting alternative authentication support to ensure the integration continues working after API tokens are permanently deactivated. This is important to avoid disruption to existing Zendesk Federated Search integrations and provide a seamless transition to new authentication.

When testing internal links in the editor, users currently cannot preview links that point to unpublished (draft) destination articles by clicking Preview, and then the link returns a 404. Authors need the ability to navigate between draft articles during the editing workflow to validate link structure and content flow before publication. This would allow content teams to test entire unpublished article hierarchies without having to publish articles prematurely.

The customer bulk-imported readers as part of onboarding a large user base. A portion of them have not activated their accounts. With no bulk-send option, the customer would have to manually trigger "Send Activation Email" individually for every unactivated reader, which is highly tedious and doesn't scale for accounts with large reader lists. Add a bulk action to select multiple readers (e.g., via checkbox selection or filter, such as "not yet activated") and send activation emails to all of them in a single action, similar to existing bulk actions like deactivate/delete/convert to user.

When using the compare tool for two versions of an article, neither article version's title (H1) is displayed. And as far as I can tell, there's no way to discover the history of an article's title. Once changed, you cannot see what it was changed from . Even when looking through Team Auditing to see when a title is changed, there is no record of what it was changed from . Another issue, which may be related, is that when you filter the Team Auditing list to show only instances of article title changes, clicking on a recently changed article's title results in a 404 error. Why would that be? There should be some way to be able to see the history of what an article's H1 has been. Even event notifications sent to Slack are missing the information of the article's previous title.

I want to be able to add comments to glossary entries, for example. This will help me add context to why and how an entry was created. For example, I'm just describing a UI feature and saw that there is a glossary entry for its counterpart. However, I can no longer figure out how I created this glossary entry. Having this info would help me easily create the new entry with the same surrounding context, instead of guessing and possibly causing a mismatch. This could be supplemented by metadata, like created/updated by or a status dropdown for Draft, Approved, etc.

Currently, users do not have an option to check, in bulk, whether activation emails have been sent to Readers or not. Raising this request to support the following in bulk: Identify Readers for whom the activation email has not been sent. Identify Readers for whom the activation email was sent but not delivered. This would help administrators efficiently track activation email status in bulk and take the necessary follow-up actions.