Feature Request

It'd be really helpful if there was an option to expand and collapse the table of contents included on the right side of the articles. For example, initially the Table of contents will show only the titles with marked with H2, and when we click one of those titles, the titles marked with H3 should appear. It will improve our user experience by a lot if we want to move quickly within the same article. (See https://bhn.document360.io/docs/20964 )

Display 'Cmd+K' on the site as the Search shortcut for Mac users instead of the incorrect 'Ctrl+K' that only applies to Windows. Or alternatively change the search shortcut to '/' which can be used universally across all operating systems.

We have content we'd like to document and share with customers as an article link WITHOUT requiring a private KB setup. The URL of this article should only be accessible if they have the direct link BUT it should not be searchable and crawled for SEO.

Notification should be sent to the readers as well on the updating article, newly added article, etc through email. Readers should have the capability to view the difference between the previous and updated one.

Issue Summary: When we accessed the default V1 workspace, and click "Open site" button, it redirects us to the homepage of V1. When we accessed the other V2 workspace, and click "Open site" button, it still redirects us to the homepage of V1. When we navigate to API documentation, and click "Open site" button, it still redirects us to the homepage of V1. When I access API documentation, it redirects me to the first article and not the homepage of API docs. In order to navigate to the homepage of the "API Documentation" , the only possibility is to add a custom URL and then insert the API homepage URL (or) after navigating to the API docs page, clicking on the home button.

I would request you to add a feature for downloading a particular category only. In simpler words, the user should be able to download a category (topic node) along with the sub-topics/articles under that category.

Is there a way to read a doc and then at the bottom of the document have a forced acknowledgement that the reader has read it (more for policy docs)?

If user session is timeout, he should have a message that will log him out. Otherwise, he may continue update the current article, without knowing it has no effect.

When users are navigating around the in-app assistant for our private KB, they are not asked to sign in. This is working as we expect and is exactly how we'd like it to work, as they are already logged into our system. However, if they click to 'full screen' an article from the in-app assistant, it opens in a new tab and makes them sign in to view it. This is a bizarre experience for users and we'd like them to be able to view the article full screen/in a new tab, without needing to sign in. Thanks!

Once a customer gives feedback about an article, they can no longer see the feedback option. This doesn't sound right. We should be able to enable feedback after a certain period... or maybe after the content has been updated. It can't be like feedback can be given only once for the entire customer/article lifetime.