Feature Request

Currently, the "Follow" functionality is implemented for JWT readers. Please ensure that the "Follow" functionality is accessible to JWT readers.

We have a customer setup with two workspaces. Currently, all readers have access to both workspaces; however, Workspace 1 is the primary for some users, while Workspace 2 is primary for others. The customer would like to implement a feature that allows configuration of two separate SSO (Single Sign-On) integrations. Based on which SSO the user logs in with, they should be automatically directed to the corresponding primary workspace: Logging in via SSO 1 should redirect the user to Workspace 1 Logging in via SSO 2 should redirect the user to Workspace 2 To support this, we are requesting a feature that allows specifying a custom landing page or default workspace post successful SSO authentication, based on the SSO configuration used during login.

The customer is requesting a change to the way the Table of Contents is displayed on the documentation page. Right now, it appears nested and collapsible, as shown in the first image due to the usage of different headings used( H2, H3 and H4), which makes it harder to view all the sections quickly. They would prefer it to be fully expanded and flat, like the version shown in the second image.PFA.

A customer has highlighted that they previously had the "Related Articles" section customized to appear in the right-hand navigation of the article view. In the site 2.0 version, this section appears at the bottom of the article, significantly reducing its visibility to end users. Here’s a direct quote from their feedback: "The Related Articles is displayed at the bottom of the article. The end users can’t even make out the presence of this link. Previously in 1.0 we had got it customized and was made visible in the right column. I need the same customization this time as well." Business Need: This customer had this feature customized in the earlier version and is now explicitly requesting its restoration in the current version. The ask is rooted in: Preserving user behavior patterns established in v1.0 Improving UX and knowledge flow Maintaining UI/UX consistency for returning end users Proposed Enhancement: Enable configurable placement of the Related Articles section with the following options: Sidebar (Right) Footer (Current Default) Benefits: Improved Visibility & UX: Users are more likely to see and click on related content when it's in the right navigation. Consistent Experience: Supports continuity for customers migrating from old version who relied on that layout. Increased Content Engagement: Better positioning drives deeper knowledge base usage and inter-article navigation.

In one case, the AI summary introduced a small but significant error. We would like to be able to manually fix the summary text

Whenever we add related articles to a page, we manually organize them alphabetically by article title. It would be great if there was a setting to automatically sort related pages in this way. It would save time manually ordering our pages, work better with dual-linking, and ensure the list automatically updates when we rename an article.

Use Case: Need to automatically update the English content to multiple languages automatically. Pain Points: Currently we need to manually translate in individual langages or use the Bulk operations to translate in multiple languages. But the customers are expecting an automatic publish of articles in multiple languages while publishing an article.

Custom status indicator can be enabled for a customer in the Business plan, still it can be added only with localization feature that is available in Enterprise plan. Therefore, ability to add text for custom status indicator should be provided at the settings such that it can be set along with the background.

Our compliance team needs a way to quickly grab an older revision of a compliance document as well as a current version, to provide to clients on an as needed basis for their compliance audits. Right now we have to save older versions of these documents in their own folder, and constantly move the current one to the old versions folder when a new revision is completed. Can you please include a feature that we can enable on the document settings (per document not global) that we can check off show previously published revisions, so that in the KB article in the left pane where a table of content would be there is a list of previous revisions that the Reader can click on?

Users follow when a page is "recently updated" . Sometimes we make very technical updates, for example small spelling correction, fix link, replace text with a snippet for future use. That is "cosmetic changes", or general editing. In this case it is not helpful for our customer to know that this page was "recently updated". Therefore I would like to request an option on the settings page to mark "exclude from recently updated list" or something like that thanks