Feature Request

We would like to have an option to embed Document360 via an iframe instead of injecting the widget script. Currently, the script-based integration makes it hard to work in environments with stricter CSP or isolation requirements. An iframe-based solution (e.g., a hosted HTML endpoint) would allow better separation and simpler integration on our side. This should support full widget functionality within the iframe, without relying on access to the parent window. Related requests: “iframe option - Private projects” and “Support for Document360 Widget in Nested Iframe Scenarios” Those highlight similar needs, but this request is for a more complete and supported iframe-based integration approach.

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

To be able configure SSO for the "open article" link in the knowledge base assistant so that user do not need to sign in again to the knowledge base after clicking the link.

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.

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.

Hello! Is there a way to give clients access to a specific article or category for a pre-defined period of time? (for example, from Jan 1st 2023 to Dec 31st 2023?) It's like setting an expiry date after which the content will not be available in the client's account. This would be very crucial as we scale our project. Otherwise, it will be very challenging to manage user access. Thank you!

Currently, when access to a page-type category is restricted for a specific Reader or Reader Group, the associated articles under that category are also restricted and become inaccessible to that Reader or Reader Group. Since the system treats a page-type category as an article, the customers expect the restriction on the page-type category to apply only to that specific category and not to cascade to the related articles.

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.

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.

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.