Feature Request

When updating an article and setting its status to “None” under Configure Category Settings during publish, the system behaves correctly. However, when the same article is forked and republished, the status is unexpectedly changed to “Updated” after the publish event—even though the UI indicates “None” prior to publishing. Expectation - -> When an article is forked, the new version should inherit the previous status by default. -> The publish modal should display the current (inherited) status rather than defaulting to “None.” -> The system should respect the user’s selection during publish and not override it post-publish. -> Status should only change if the user explicitly selects a different option.

Current Behavior When using the Share Article option, the generated link follows the format: https://projectdomain/shared/articleID This link differs from the standard URL format used for articles published on the knowledge base site. Published articles typically follow a more readable structure such as: https://projectdomain/docs/articlename The current shared article link format uses a system-generated article ID instead of the article slug/title, which results in a non-descriptive URL. This makes it difficult to manage and reference shared links, especially in environments where URLs are used within applications or documentation workflows. Use Case For on-premise users, URLs are often embedded or referenced directly within the product or internal systems. Since the current shared links use a different structure (/shared/articleID), they do not align with the standard documentation URLs already used in these systems. Expected Enhancement Shared article links should follow the same URL structure as published articles, for example: https://projectname.document360.io/docs/articlename

A user has asked if it is possible to choose a point in an article to listen from. Currently it starts from the beginning of an article only but the user would like to highlight a section part way through and listen from there. Could this be added to future developments?

Currently, the featured image is rendered only for public projects. The customer wants to have the featured image for the public articles in the mixed projects.

We are receiving warnings indicating that multiple articles have a low text-to-HTML ratio. We would like to address this issue to improve the SEO performance of our knowledge base. Thanks.

Introduce the capability for admins and owners to view, export, and download article comments after publication in the portal.

I'd like to propose to build API functionality to fetch info about and manage the lists of article followers. For example: GET /articleId endpoint to fetch list of email addresses following an article POST /articleId and/or PUT /articleId endpoints to add new emails to the list of followers This is somewhat related to one of the analytics request ( https://feedback.document360.com/feature-request/p/analytics-for-the-follow-an-article-feature ), bc I agree with what's written there: "I am sure this data is already available in the platform as notifications are sent to users who follow the article. It is just a matter of extracting that data and sharing it." I'm also adding my vote to the requests asking for the options to: customise the followers notification email and create a way to include details about WHAT changed in the article ( https://feedback.document360.com/feature-request/p/customise-email-template-for-follow ) create followers analytics (link above) Article follow option has great potential as a customer facing functionality. Let's materialise this potential!

Having a report or view that lists all articles with generated private links (including article titles and total count) would significantly improve our ability to govern and manage those links effectively.

We request an enhancement to allow configuring an expiration time for generated shared links. At present, links need to be manually deleted, but an expiry option would enable links to automatically become inactive after a specified duration.

When publishing and article, there is an option to add other articles from Doc360 at the bottom of the soon-to-be published article. That is a handy feature, but was wondering if you would also please consider a way to add URLs from outside Doc360 such as a SharePoint URL or website URL? It would be helpful as sometimes we want to relate to other resources as well.