Feature Request

We have an application through which our internal employees impersonate external customer accounts. They would be impersonating different accounts of their external customer during a single session by clicking on a button "" View intern portal as username", after entering the external customer ID. All these external customers might be part of different reader groups. We would like to know if it is possible to reinitialize the token for the internal users based on the users that they are impersonating within a single session.

Our support team has asked for the ability to change the fields in the contact us form to include Account ID. This eliminates the need for support to reach out to the customer before they can even confirm what the problem is to get the Account ID.

API Behavior The widget script should support the authheader property as an optional configuration. When authheader is present, the default headers will be ignored, and only the provided authheader will be used for authentication. Backward Compatibility If authheader is not provided, the script will continue to use the existing default headers for authentication, ensuring no disruption for existing customers.

The ability to have a section like 'Support' on the KB assistant with new or updated articles. Alternatively, an editable section for text/links.