Feature Request

We request an on-demand CSV export for all articles, with an option to filter the export by category. The CSV should include: Whether each article has been approved(Review completed) The date of the most recent approval (Date of the recent workflow status change) The user who reviewed/approved the article ( Reviewer details ) The primary requirement is to provide a clear audit trail of which articles have been approved, when they were last approved, and who approved them, for compliance and audit purposes. We follow an 11–12 month review and sign-off cycle for existing published articles. Thank you.

Provide a UI to allow for multiple articles to have the tags edited.

It would be great to have the possibility to update reader users in the reader tab in bulk. Right now, to edit or delete, a lot of manual work is required to singularly change each user.

I would like the ability to add Decision Trees directly to the main left-sidebar navigation (Table of Contents), treating them as first-class citizens alongside standard Articles and Categories. The Problem: Currently, Decision Trees appear to be accessible primarily via embedding or through links/buttons on a parent page. This creates a discoverability issue: 1. Users cannot easily see the Decision Tree in the site hierarchy (TOC) to understand it exists. 2. Users must first navigate to a parent "landing page" to find the entry point for the tree. 3. This disrupts the flow for users who expect all key resources to be navigable from the sidebar. The Desired Solution: In the Category Manager, I would like to be able to add a new item and select "Decision Tree" as the page type (similar to how we currently choose "Article," or "Category Page"). - Behavior: When a user clicks this item in the left sidebar, it should open the Decision Tree view directly in the main content area. - Result: This would allow users to "drill down" into a specific domain (e.g., "Data Security") directly from the navigation menu, rather than having to route through a generic landing page first.

The Tasks card on the dashboard only shows tasks for the current calendar week (Sunday–Saturday), not a rolling 7-day window. This means a task assigned on a Friday with a due date the following Tuesday won't appear on the dashboard until Monday, leaving almost no reaction time before it's due. Tasks assigned near the end of a week, or with due dates just past the week boundary, can sit invisible on the dashboard for days before ever surfacing. A few of our customer's are dashboard-driven and they rely on the dashboard (not the full Tasks view) to react to newly assigned work. The current week-based logic undermines that workflow, since tasks can be invisible on the dashboard for extended periods depending on when in the week they're assigned. Requested at minimum: change the dashboard Tasks card filter from "current week" to a rolling 7-day window. Ideal/preferred solution: let users choose the bucket shown on the dashboard Tasks card, e.g.: Overdue Next 7 days Next 14 or 30 days All tasks (fallback/last resort)

Allow the user to select multiple values using checkboxes

The ability to copy an entire content tree within Document360 would significantly enhance efficiency and flexibility in content management. This feature would be especially valuable when creating new documentation based on existing structures, enabling teams to quickly replicate templates, workflows, or topic hierarchies without manual duplication. It would also support the creation of tailored content sets for different user groups—such as internal teams, external clients, or regional audiences—while maintaining consistency across versions. Implementing this functionality would streamline content development, reduce errors, and improve scalability for growing documentation needs.

Ability to link directly to specific sections (anchors/headings) within an article when configuring decision trees. Currently, decision trees only allow linking to the article root or external links. This feature would enable users to create more granular navigation paths by directing readers to the exact section of interest within an article.

Integration with Azure DevOps so we can build a KB around releases, pipeline setups, artifacts etc.

Currently, inline commenting is limited to the Draft stage, which restricts reviews after publishing. Enabling this would help reviewers share suggestions or highlight required updates when they notice issues later. This would reduce the need to move articles back to draft and support a smoother post-publish review workflow.