--- title: "Search History Log" slug: "search-history" description: "How to use the Search History log, which tracks every search result executed in the system for auditing purposes." status: "new" updated: 2026-10-02T13:32:47Z published: 2026-10-02T13:32:47Z canonical: "docs.revealdata.com/search-history" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Search History Log Logikcull’s **Search History** **log** makes it easy to audit the searches performed within your projects. You can access the Search History log by navigating to ![project settings icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Project-Settings_Icon(1).png) **Project Settings** > **Search History**. ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Search History log_Sep26(1).png) The log itself is filterable by users and date ranges via the **User** dropdown or **Start Date** / **End Date** fields, and can be searched using keywords from the search query itself. Clicking ![download CSV icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Download to CSV_Icon.png) **Download CSV** will export the contents of your Search History log to a spreadsheet file. Filters can be applied beforehand so that you’re exporting only the information you’re interested in auditing. ## How entries are logged Each entry represents a filter applied or removed through the Filter Carousel, a search performed in the Search screen, a re-executed saved search, or a bulk action. Only searches made on or after 9/28/2026 (the date the Search History log was implemented) are captured in the table. Similar to a locked search, search entry records will not change after they are logged, even if the search results change due to added, culled, or newly tagged documents. Re-running the same search from the search log may display different results than the number displayed in the “Results” column of the log. ## Search Execution Details popup Click an entry to open up its **Search Execution Details** popup, which displays all the information about each search, including the columns in the Search History log. ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Search History Details_Sep26(2).png) The below table lists each logged data point and its description. | Data | Description | | --- | --- | | **Date** | The date and time the search was executed. | | **User** | The person who ran the search. | | **Search** | The entire search represented as a single query, including filters added in the Filter Carousel. You can copy the search query and paste it into your search bar to re-execute the search. Re-executing searches may produce a different number of results than what was logged in the table. See the [Blank search queries](/logikcull/docs/search-history#blank-search-queries) section for searches that show asterisks ( * ) or dashes ( – ). | | **Search source** | Where the search was performed: - **Search bar** – Searches performed through the search bar, Advanced Search, or Bulk Keyword search. - **Saved search** – A re-executed saved search. - **Filter panel** – Filters added or removed through the Filter Carousel. - **System action** – A bulk action performed by the user on all search results. | | **Project** | The project the search was executed in. | | **Results** | The number of results in the search at the time it was run. | | **Applied filters** | The filters used in the search, shown when the search can't be written as a query. | | **Execution method** | The type of search performed: - **Manual** – A search performed by the user. - **Saved** – A re-executed saved search. - **Bulk** – A bulk action performed by the user on the entire search results, such as: - Tagging - Custom field (coding) updates - Culling or unculling - Bulk redactions - Assigning authorized users (permissions) > [!NOTE] > Note > > Bulk actions are only recorded in the Search History log when performed using the **Select all in search** option in the **Bulk Actions** dropdown. > > ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Select All in Search_Sep26.png) | | **Audit UUID** | A random, unique numerical ID given to each log entry. | ## Blank search queries ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Asterisk and Dash search query_Sep26.png) Certain searches cannot be represented as a search query and contain placeholder symbols in the Search column. ### Searches with an asterisk Searches with an **asterisk** ( * ) are “match everything” searches where no keywords or filters are used, so all documents in the project are returned. This happens when users clear the search bar or remove all the checked filters in the Filter Carousel. ### Searches with a dash Searches with a **dash** ( – ) are searches that the log cannot write out in search syntax. There is no query that can be copied and pasted back into the search bar. Dashes will appear in the Search History log if the search is comprised of any of the following: - A filter by upload, download name, authorized users, or suggested tags (these store internal IDs that aren’t compatible when pasted into search syntax). - A scoped search, such as a search limited to a review set or one started from an Ask AI question. - A company filter set to "No company name". - More than 200 filter values in total. However, you can still see the filters used by opening the search execution details if you want to recreate the search manually, shown below. ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LGK_Dash search query_Sep26.png)