Knowledge base agent

minimum version 2026 1 prerequisites reach out to your ivanti account manager https //www ivanti com/lp/customers/contact/epg contact us to enable the feature flag enableknowledgerepositories to use sharepoint as an external source the knowledge base agent searches knowledge sources to provide clear and helpful answers, allowing users to solve issues quickly and reduce ticket creation to enable and configure the knowledge base agent, do the following log in to as an open the configuration console and select ai configuration hub > agentic ai > agent settings enable the knowledge base agent using the toggle button an additional toggle button with the same function is available in the upper right corner of the agent page click configure to further set up the agent enable the use internal knowledge source toggle button to allow agentic ai to utilize internal knowledge base for decision making and providing responses to user queries click view knowledge base to view all the knowledge business records only published internal knowledge sources are used for knowledge search enable the use external sources toggle button to allow agentic ai to utilize external resources for decision making and providing responses to user queries click manage external sources to add relevant links to external resources you can connect knowledge sources through external source urls, sharepoint, or both add external source urls to add external source urls, do the following enable the urls toggle and then click configure enter the supported domains in the text field and click add you can specify either a domain or a domain path to include subpages in the search, the configured path can contain up to two subfolders in this case, the search includes content at the specified path and all subordinate paths for example www microsoft com/windows/ → 1 subfolder www microsoft com/windows/security/ → 2 subfolders only publicly accessible content that has already been indexed can be returned if you specify a deeper path than supported, subpages are not included in the search for that path as a result, child pages under that path are not searched to search a section and its child pages, use a higher level path that meets the two subfolder limit, or specify an individual webpage if you want to target a single page for example www microsoft com/windows/security/update/ → 3 subfolders, so subpages are excluded in the search click remove to delete any url from the added list add sharepoint sources to add sharepoint sources, do the following enable the sharepoint toggle and then click configure enter the following details field description source name it is a unique name for your sharepoint source, making it easier to distinguish between multiple configured sources tenant id / client id / client secret refers to the tenant id, client id, and client secret from the azure active directory app registration these are required for integrating sharepoint with microsoft resources for more information, refer to scenario 1 and scenario 2 in importing employees using the azure ad connector docid\ c7gs9inq5rn92tp0k6xk4 sharepoint url actual web address of your sharepoint site that is used to connect and integrate with the agent, allowing access to documents and resources for knowledge search sharepoint region refers to the geographic location where the sharepoint tenant is hosted specifying the region allows faster api queries by targeting the correct tenant location site name specific sharepoint subfolders within your organization when you enter a site name, the search will only look for information in that site, not in other sites for example, https //corp sharepoint com/project here project is the site name, and the agent get results only from this sharepoint’s site note you can use commas to separate site names click add to save the entry under conversation setup > articles used in knowledge summarization , enter the number of most relevant articles that should be used to generate the knowledge summary under conversation setup > max response length , set the maximum length of a response to a knowledge search article allow transfer to live agent enable the toggle button to transfer the interaction to your service desk human agent in case the agentic ai bot cannot solve the user's request along with this toggle, you must also enable the allow transfer to live agent toggle in global settings > escalation handling under advanced settings > knowledge base description , define the scope of the knowledge base agent by detailing the types of queries the agent can handle you can also provide some example queries related to the knowledge base to help the agent better understand the context when users ask queries other than those defined here, the agent considers them out of context and replies to users accordingly modifying the intent description might result in unpredictable agent behavior we recommend that only users with experience in llm prompt engineering make these changes fields marked with an asterisk ( ) are mandatory analytics to view the performance metrics and usage statistics for your knowledge base agent, open the configuration console and select ai configuration hub > agentic ai > agent settings > knowledge base agent > configure > analytics the analytics page provides the performance of the knowledge base agent it helps you monitor the following metrics total kb requests shows how many times users requested or received knowledge article recommendations from the kb agent successful kb article deflections shows the number of user issues resolved through knowledge articles without requiring additional support actions the time range filter allows users to specify the period for which analytics data is displayed metrics on the analytics page are updated based on the selected time range limitations the knowledge base agent does not support attachments associated with internal business objects therefore, the pdf and text files attached to knowledge business objects are excluded from knowledge search results when the use internal knowledge source toggle is enabled, all internal knowledge business objects are referenced however, only published internal sources are used during live agent transfer, a conversation summary should be sent to the live agent at the beginning of the session this functionality is currently not working at the end of a live agent transfer session, users are not informed about what to do next however, when the session ends, the agentic ai is reset and users should initiate a new prompt, even if no live agent was available the agentic ai handles only it‑related issues other line of business (lob) queries, such as hr, facilities, and other non‑it requests are not supported