# How to Review Crawled Knowledge Documents After you set up a [knowledge base as a Data Source](/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources.md) and [complete a crawl](/aisera-platform/adding-data-to-your-tenant/data-ingestion/how-to-set-up-knowledge-base-crawls.md), you will need to review and commit any knowledge documents and sections that were added, modified, or deleted since the previous crawl. Completing this process makes the documents available for use by the app. To view the documents that need review, go to **AI Workbench > Review**, and select the **Knowledge Review** tab. The **Knowledge Review** page lists all new, modified, and deleted knowledge documents from the most recent crawl. It displays articles at the document level. Click any knowledge document row to review its sections. ### **Knowledge Review Filters** Filters can be applied to the **Knowledge Review** page to allow for easier location of documents. The default primary filters are **Change State** and **Review Status.** Once custom filters have been applied, they can be saved by clicking the **Funnel** icon and selecting **Save as New Filter** for later use. #### **Change State** **Change State** marks the current status of the document in relation to the previous crawl. * **Added** - The knowledge document did not exist in the previous crawl, and was brought into the platform via the most recent crawl of the knowledge base. * **Modified** - The knowledge document already existed in the previous crawl, but there was some change made to the document at its section title or content level. * **Deleted** - The knowledge document existed in the previous crawl, but was removed from the knowledge base and no longer exists after the most recent crawl of the knowledge base. #### **Review Status** **Review Status** communicates the current readiness of a document for use by the app. 1. **Needs Review** - The knowledge document needs an administrator’s manual approval. 2. **Reviewed** - The knowledge document change was either automatically or manually approved, or manually rejected. 3. **Committed** - The knowledge document was approved and committed to the platform either automatically by the system or manually by an administrator clicking on **Commit Changes.** ### **Reviewing Knowledge Documents** **Added** and **Deleted** knowledge documents will be automatically marked as **Reviewed**. Modified documents will need to be manually reviewed. To review a document, select a document from the list of documents that have the status of **Needs Review.** This will lead to the knowledge document section titles and their respective content. For each item select one of the following: * **Approve** - Aisera keeps all phrases associated with the old section and accepts the new section. * **Reject** - Aisera keeps all phrases associated with the old section and does not accept the new section. * **Reassign** - Manually reassign the new section copy to the section it was in from the previous crawl. ## Reviewing Knowledge Documents You will only be required to review knowledge documents that are under the status **Needs Review**. Any other documents that show as **Reviewed** have either been approved or rejected, and any documents that show as **Committed** have been both reviewed and committed to the platform under **Commit Changes.** Only Modified documents will need to be manually reviewed. Documents that are **Added** or **Deleted** during a crawl are automatically set to **Reviewed**. For **Modified** change type knowledge documents, there are three scenarios. ### Section Content Changes In the document that needs review from the most recent crawl, a section title has stayed the same, but the section content has changed. * In **Knowledge Review**, the section will be approved automatically, and the status will also be automatically be set as **Reviewed**. * An administrator will need to click **Commit Changes** and retrain the app for the changes to take effect. * Any existing knowledge intents from the previous crawl that shared the same title will be updated with the correct content. ### Section Title Change In the document that needs review from the most recent crawl, a section title has changed, but the section content remains the same. * In **Knowledge Review**, the section will be approved automatically, and the status will also automatically be set as **Reviewed**. * An administrator will need to click **Commit Changes** and retrain the app for the changes to take effect. * Any existing knowledge intents from the previous crawl that shared the same content will be updated with the correct section title and knowledge intent name. ### Section Title and Content Changes In the document that needs review from the most recent crawl, both the section title and section content have changed. * In **Knowledge Review**, the system will not know whether it is the same section. An administrator will need to either **Approve**, **Reject**, or **Reassign** the section. The status will then be set to **Reviewed**. * An administrator will need to click **Commit Changes** and retrain the app for the changes to take effect. * Knowledge intents that were created from sections that no longer exist will be deactivated. Any existing knowledge intents that are **reassigned** will be updated with the correct name of the reassigned section title. ### **Committing Changes** Committing changes commits all reviewed knowledge documents to the platform. To do this, on the **Knowledge Review** tab of the **Review** page click on **Commit Changes**. ### Retraining Committing documents to the Aisera platform makes them accessible to Aisera apps for training and fulfillment, but the app will only use the documents *after it has been trained on them.* To train an app, ensure you have selected the correct Aisera app by either selecting the desired app under **Settings > AiseraGPT** or selecting the app in the selection menu at the top of the screen. Go to **AI Lens**. Select **Retrain** in the top right corner to begin a retrain. Allow time for the bot to retrain before testing. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/data-ingestion/how-to-review-crawled-knowledge-documents.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.