Feature Request

I would love to see multi-factor authentication using either Google or Microsoft authenticator.

As an Admin, I need to be able to check that certain roles and permissions are functioning as I expect without having to have someone else test these for me. Example 1: I'm an Admin. I set up a contributor role that does not allow publishing. As an Admin, I can see and use the Publish button. I want to confirm that the contributor role does not have access to the publish button. I want to click on my Profile icon within Doc360 and select "Impersonate" and select a role or specific user to impersonate. Example 2: I am an author. I add a private note in an article I'm working on. I set the permissions of the note only to other authors. I want to preview the article and impersonate a Reader of the knowledge base to ensure that they cannot see this private note.

Instead of having to create Groups manually in Document360, SCIM should be used to synchronise Azure Groups to Document 360, allowing for easier membership adminsitration.

We need the KB Assistant to show only content approved for a certain Reader Group automatically (or we need Reader Group filters to be visible and customizable specifically for the KB Assistant). We cannot think of a scenario where a user within a Reader Group should see more within the KB Assistant than the standard KB.

One of the customer has mentioned that they are reporting a moderate vulnerability because the sub resource integrity (SRI) checks are not being performed on Document360 for their hosting at support.nvoq.com . The customer would like to include the SRI checks in our testing process.

We cannot export any content unless it is published. Since private publishing is unfortunately limited to enterprise accounts, we cannot share any private content with our customers. This requires us to export content in PDF. Yet it requires extra effort too. We need to publish the article very quickly, export it and unpublish it without anyone seing it. This entire process must be optimized.

There any many customers who have similar products related to each other and they want these products to be documented as part of the same KB. Thus clients are expecting to use multiple JWT tokens. Kindly facilitate this

Please add an option for review the self sign up request. When it comes to private document portal enabling self sign up is not a good idea and at same time, it's difficult to import more users into portal. So if there is an option for review and approve/deny sign up request, it would be great to manage users.

Currently, the API key can be regenerated only through a manual process inside the document360 portal. This makes this key un-secured. This key has an unlimited lifetime and if we won't regenerate it, then someone with access to it will permanently have access to our documentation. If we will have the option to regenerate this API key through an API, then we could regenerate it automatically once a week and automatically update our codebase with the new key, which will make it much more secure, and allow anyone who has this key only a max of 1 week access.

One of our customer has raised a request to include an option on the login page that would help the users to enforce the password strength while setting up their Document360 user account.