Deep Search crosses module boundaries — leads, companies, invoices, employees, products — so operators can locate a record without knowing which app area owns it.
Please note:
- Results exclude modules disabled for the tenant and records outside your permission scope — see Roles, permissions, and RBAC.
- Saved searches reset when you leave the page; pin frequent views from Read your dashboards and reports instead.
Search behavior
| Input | Matches | Result ranking |
|---|---|---|
| Name or title | Primary display fields | Exact match first |
| Email / phone | Contact fields | Normalized match |
| Code / SKU | Product, asset, order codes | Prefix and exact |
| Free text | Notes and descriptions | Lower weight |
Results exclude modules disabled for the tenant and records outside your permission scope.
Run a deep search
- Open Reporting → Deep Search or use the global search shortcut when configured
- Enter at least two characters
- Filter by module type if the result set is large
- Open the record from the result row
Saved searches are not required for basic use — filters reset when you leave the page.
How search scopes results
flowchart TB
Query[Search query] --> Index[Cross-module index]
Index --> Modules{Enabled modules}
Modules --> Perms{User permissions}
Perms --> Results[Ranked result list]
Results --> Record[Open record detail]
Use Deep Search during support handoffs when a customer references an invoice number but the agent is unsure which module created it. Supervisors tracing user sessions may prefer Use Eye activity for live context.