Deep Search unlocks your organisation's institutional memory in LiveDiligence, making your collective knowledge instantly available at your fingertips. Here is how it works.
Accessing search
If search is enabled on your account, click the blue search button at the top of any LiveDiligence page to access it.

Types of search
Deep search allows for two distinct types of search:
- Transaction search: use to find transactions that contain your search terms.
- Content search: use to find content that contains your search terms.

Transaction search
Transaction search makes it easy to locate transactions containing the content you need. It searches through all transactions you have access to and provides a list of those that match your search term. Results are ranked based on how many matches are found in each transaction.
You can click on any of these results to open the transaction in a new tab.
For example: Searching for Ireland
returns 15 transactions

To explore matching transactions in more detail, select them using the checkboxes and click "Set Filter." This creates a transaction filter for your selected items, which you can then investigate further using content search.

Content search
Content search uses the full power of LiveDiligence structured data to deliver unprecedented search detail with all results classified and fully traceable to itβs exact location.
For example: Searching for liquidated damages
returns 27 results across different content types

Search Techniques
Deep search supports various search techniques that can help you target specific results:
Technique | Format | What It Does | Best For |
Single word | Sungrow | Finds all instances of this word | Basic searches |
Multiple words | Sungrow SG350HX | Finds content with EITHER term | Broader results |
Exact phrase | "Sungrow SG350HX" | Finds this exact phrase in order | Specific equipment or terms |
AND operator | +Sungrow +SG350HX | Finds content with BOTH terms (any order) | Related concepts |
Exclusion | Sungrow -SG350HX | Finds first term WITHOUT second term | Narrowing results |
Note: searching for special characters and symbols (e.g. Β£,β¬, /, %) is not yet supported, but will be coming soon.
Sorting results
Search results can be sorted as follows:
- Best match (default): Results are ranked by relevance, showing items with the most matches to your search terms first.
- Date created: Results are sorted by the date when the transaction or item was originally created. You can choose to display results from newest to oldest or oldest to newest.
- Last updated: Results are sorted by the date when the transaction or item was most recently modified. You can choose to display results from newest to oldest or oldest to newest.

Filters
- Transaction: Limit to specific transactions
- Content Type: Narrow to risks, Q&A, etc.
- Publish Status:
- "Work in Progress" - latest drafts
- "Latest Published" - approved content
- Tip: Select only one of these options to reduce duplicate results
- Last Modified/Published/Created: Narrow to recent work
- Risk Level: Find content tied to specific risk levels
- Risk Status: Filter by approval status (e.g., "waiting")
- Organisation: Filter by content author organisation
Controlling visibility of search content
Search is currently only available for internal users (i.e. members of your organisation). We plan to expand access to external users like clients soon.
You can control what content is available to users via search. This control is applied at the individual transaction level and can be implemented in two ways:
1. Transaction-Level Visibility In Transaction Settings, use "Search & Transaction List (Home) Area Visibility" to control overall access:
- Private: Only internal users with transaction roles can see search results
- Visible with permission: Users with internal transaction roles AND users with organisation roles (with permission to view non-private transactions) can see search results

Note: Internal viewer roles cannot see search results from private transactions.
2. Section-Level Visibility In role permissions, you can hide specific sections of the transaction document. Any section set to "Hidden" for a role will not appear in that user's search results, even if they have overall transaction access.

This two-tier approach lets you control both who can find your transaction and which specific content they can see within it.