Feature Requests

When replacing an image in the files manager, you would need to then replace it manually in the articles, this increases the workload x10000. This tool would be much useful if it replaces the image everywhere.

Currently, updating article URLs (slugs) requires opening each article individually in the editor, which can be time-consuming, especially when multiple links need to be changed. Suggested Improvement: Add a centralized page or management view where users can: View all article URLs/slugs in one place. Edit and update URLs directly without opening each article. Optionally sort, filter, or bulk-edit slugs for faster management. Why this matters: This enhancement would make it significantly easier to maintain consistent and SEO-friendly article URLs, especially for teams managing large knowledge bases or restructuring content.

Currently, when an article contains a broken link and a user clicks the article from the “Article Links” section, it simply opens the article without showing which specific link is broken. Suggested Improvement: When an article with a broken link is clicked, the system should automatically: Highlight or scroll directly to the broken link within the article editor, or display a clear indication of which link(s) are broken and where they are located in the article. Why this matters: This enhancement would save time for users managing large knowledge bases by making it much easier to locate and fix broken links without manually scanning through entire articles.

We’re seeing 60+ “write this article” prompts for topics way outside our domain — many look bot-generated. This clogs our queue, wastes time, and risks diluting the knowledge base. What we need: Smarter controls so AI suggestions only surface for content we actually want to cover Stronger bot protection to block junk searches from triggering new-article prompts A way to exclude certain topics entirely from the “auto-suggest an article” logic Just because someone searches for something and doesn’t find it doesn’t mean we should create an article — even if it gives a short-term SEO bump. Why this matters: Keeps AI focused on suggesting high-value content without polluting KB quality and brand relevance.

Currently, Helpjuice requires the Email field to serve both as the User ID (login) and as the contact email. This creates challenges where users log in with a system-specific email format that is not a real inbox. Because of this limitation: Admins cannot reach users directly when they have questions about articles. Workarounds (e.g., using feedback forms or manually adding real emails) are not feasible since the login email must remain system-based. Requested Feature: Add a separate “User ID” field distinct from the Email field. The User ID would be used for system login/authentication. The Email field would be used for communication, notifications, and tracking requests. This separation would ensure smoother communication with users while still maintaining system login integrity.

When filtering users, we need to be able to export deactivated users. Having this as an advanced search option would allow us to identify the users and export the list as needed.

It would be very helpful to have the User/IP column also for the articles/categories analytics, so we can better track users usage of the knowledge base. Also, having an overview of the origin of the visit/view would provide more powerful insights.

Once again, a workflow within the article feedback section would be extremely helpful. In this case, when I am reviewing feedback, I click on the article and then the specific feedback that someone is giving on that article doesn't follow to my new location. I have to go back and forth to read the article and then read the feedback multiple times to make sure I am understanding it. I would prefer if I click on the feedback that it takes me to the article and then has the particular feedback on the side of the article somewhere or as a pop up so I can continue review without having to click back and forth between the article and the article feedback section.

I would love it if Accordion and Tab titles would be included in the table of contents. I would also love it if any H1, H2, H3, H4 within the accordions and tabs would be included in the Table of Contents. It just makes sense to give us full control over what we want to include in the TOC. And since we can remove items from the TOC, why not add everything to it and give us the ability to decide what we do and do not want to include. PLEASE - this would be a MAJOR improvement and would help me/us out considerably.

Once we submit an article for review, we can't remove the review state unless we publish it. This isn't ideal in scenarios where the article was disapproved and we just want to get it out of review and submit it again when it's adjusted. In these cases, we have to publish the article and unpublish it to remove the review state. Once the reviewer disapproves the article and the author makes the changes, he can't resubmit it for review. How does the reviewer know they updated it and that they need to review it again? Related to those two points, users without the "unlock publish" ability cannot get articles outside of the review state and cannot re-submit them for review. The only approach right now is to add a comment in the article to notify the reviewer that he needs to check it again. Review comments aren't saved in the editor. We should have a log of the review rounds with the corresponding comments.