Feature Requests

We would like to suggest adding the ability to customize admin permissions or introduce a separate “Customization” role that allows more flexible control over what users can access based on their job responsibilities. Currently, full admin rights are often too broad to assign to every user who needs limited access to certain features. This limitation makes it difficult to delegate tasks without overexposing system-level settings. Introducing a customizable role — or allowing granular permission control — would help teams assign only the necessary rights, improving both security and workflow efficiency.

It would be useful if we could see analytics around Swifty to help us understand the impact it is having on users. Did Swifty return an answer to the user? Was it the right answer? Did the user use a follow-up search/question? Did the user choose to view an article after seeing the answer?

A highly useful implementation would be the ability to assign collaborators with permissions to create, edit, and remove articles or folders only within specific sections. The experience could be similar to that of accessibility: https://help.helpjuice.com/en_US/content-accessibility/what-is-the-difference-between-public-internal-and-private

It would be great if there were a way to hide the 'Created by' indication for each glossary entry."

I'd like to be able to run a report monthly that shows all changes made within a specified timeframe so that I can send that out to the team each month to show updates to SOPs.

It would be very useful to have a "Copy" button on all code blocks within the Knowledge Base (KB) articles. This would allow users to quickly copy the entire code snippet with one click, without needing to manually select and copy the text. It improves usability, especially for longer code samples, and reduces the chance of copying incomplete or broken code.

It would be very helpful to have the ability to embed/transfer articles between different Helpjuice instances. Currently, there is no way to reuse articles across these environments without manually duplicating content. Ideally, this feature would allow an article from one instance to be embedded into another while preserving the formatting and branding of the instance the article is embedded into. This functionality would be especially valuable for organizations managing multiple brands/platforms under separate Helpjuice instances.

Allow users to give feedback on the Swifty results the same way they can on an article so we can review analytics around the questions and answers to identify content we need to improve keywords and content to ensure better results.

Currently, when I search by article title in the Dashboard, the article I'm looking for is listed far down the list of results. Even when I use the exact title. I tried using the 2 keywords (for the article in the example) and still this article is not top of the list, this makes no sense to me and wastes time when I know an article exists. Is there some way to change or improve the search results logic? This is the URL for the example article: https://learn.fotoware.com/troubleshooting-fotostation/where-are-configuration-files-stored-in-mac-os

The ability to sort feedback into buckets of to do, in progress, or done as well as @ the person who reported the feedback and have a conversation with them (without them being subscribed) would be helpful. Also, the ability to assign feedback to particular product managers, or sort based off product manager or product.