Feature Request

This request was raised on behalf of Jon Currently, when we choose to switch to different IdP with SSO configuration, we have to manually remove the SSO users and then reconfigure the new SSO and add the users back as SSO users. It would be better if we have an option to change the IdP from the SSO settings itself so that we don't have to manually remove and then add the users. Thank you.

It would be good if new categories which are added to the knowledge base portal are added to the Reader Group(s)( content access) automatically. With this, we can make sure that all the contents are visible to the readers and we can save a lot of time.

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

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.

Our Document360 auto-signs off. We then need to reauthenticate. If we have multiple Doc360 tabs open, we must either close them and loose our place or log in for each tab. But even then we are taken back to the home page where we have to select the KB again. I want to be able to login from one tab and have all my other Doc360 tabs recognize that login.

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.

Now when you remove a contributor account (because someone left the company etc), all places where that contributor appears in history is not labeled. That person should still be listed as a contributor, in analytics, and history. "Deactivated" can appear beside the name.

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.

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

Hi team, One of our customer requested the following feature. When we add new reader, activation email is valid for 7 days. Most of their readers fail to log in resulting in manual work of resending the activation link. This would be easier work for small numbers, but they usually add 100+ readers and it becomes difficult task. They would like to get an option to automate this in a way that should send reminders if users have not logged in after 7 days. And to be controlled by Admin/Owners.