For the complete documentation index, see llms.txt. This page is also available as Markdown.

Data Sources listing

The data sources listing section displays all materials linked to the current Knowledge Bot. This interface allows users to manage and monitor the content that the chatbot references when generating responses. Items are ordered by the most recent update date, descending.

For each data source, the following details are shown:

  • Data Source: The name of the material, helping identify its origin.

  • File/URL: Displays the name of the uploaded document or the URL of the scraped webpage / Confluence / SharePoint. This allows user to quickly recognize the specific files or pages that have been incorporated into the chatbot's knowledge base.

  • Status: Indicates the current processing status of each item:

    • Success: The material has been processed successfully and is ready for use.

    • Pending: Processing is ongoing; the user must wait until it is complete.

    • Not Refreshed: The material was not replaced or updated successfully through recurrency or manual update.

    • Fail: The material could not be processed.

  • Actions available:

    • File details: Open the details of the data source.

    • Replace: Allows modification or replacement of the data source.

    • Delete: Removes the data source if it is no longer relevant.

Users can also search for specific materials. For hierarchical sources such as Confluence or SharePoint, pages are displayed in a tree view that reflects their structure from Confluence / SharePoint.

Folders in Confluence or SharePoint do not have individual detail pages; they serve only to replicate the structure visually.

Processing statuses influence available actions:

  • If Success, all options are available.

  • If Pending, no actions can be performed until processing is complete.

  • If Not Refreshed, all options are available

  • If Fail, users can Replace or Delete, and a tooltip will explain the failure reason. In this case, the details page is unavailable as no data has been ingested.

Last updated

Was this helpful?