Feature Request

When accessing a knowledge base article using a URL that contains a heading fragment (for example, #section-id), the fragment is not retained if the user is redirected through the JWT reauthentication flow. After login, the article loads at the top of the page instead of the intended heading, which impacts deep-linking to specific sections. This currently occurs because URL fragments are handled on the client side and are not available during the server-side authentication and redirect flow used for JWT. Preserving the fragment across reauthentication would provide a more consistent navigation experience for users, even when sessions expire.

It would be good if it can possible map a specific email domain (@ xyz.com ) to a particular reader group through SSO.

A team account with a specific configuration in the admin portal to only specific articles and categories, has the same access in the knowledge base site as well. In an ideal case, the access needs to be different or the option to have complete KB Site access regardless of their access in the portal.

We want the option to move readers from one reader group to another in a batch. While the export option is already available in the reader group section, adding either an import option or a move option would greatly simplify managing bulk reader transfers between groups.

If editing access is provided to an editor for specific categories / articles in the knowledge base - they shouldn't be able to create additional categories / articles (which should instead be created from the admin and then assign to relevant editors). The need for this to be implemented with high priority is also related to all the technical URL/slug dependencies resulting from the creation of new articles/categories, and that makes it is essential to have a content role that limits users from creating new categories/articles independently.