Search
Overview
Search is the central full-text search across all modules. It is permission- and brand-filtered: only what you would be allowed to open anyway can be found.
That is not a correction applied to the display — it takes effect during the search itself. A result you may not see is never produced in the first place; otherwise the result count alone would reveal that something exists.
Core tasks
Search. Type a term; the result list shows the number of hits and groups them by result type. The core supplies customers and tasks; installed modules add their own types — products, quotes, contracts, projects, knowledge articles or templates, for instance.
Jump to a result. Clicking opens the record in its place within the application.
Search from the keyboard. The command palette reaches the same search without leaving the page — the quicker route when you are in the middle of something.
Fields in detail
Search has one input field and a few switches.
| Field | Values / format | What it does |
|---|---|---|
| Search term | text | What is searched for. Names, numbers, participants and content are searched — an invoice number finds the invoice, a customer name everything about that customer. |
| Type | selection of data kinds | What it is narrowed to — customers, documents, tasks, files, knowledge. |
| Brand | one of your brands | Which brand it is narrowed to. |
| Period | date range | Which period. |
What you may not see is not found. The permission cut sits inside the search, not in the display of results — there is no route to data through search that is denied to you elsewhere. That is why the same search can return different numbers of hits for two people without anything being broken.
Settings & permissions
- No permission of its own. The page is reachable by every signed-in person; filtering happens
through the permissions on the data being searched.
- Brand scope. Across several brands, only results from brands you hold a permission for appear.
- Which types appear depends on the module. Every module registers its own searchable content. A
disabled module returns no results — and does not show up as an empty type either.
- The index follows the data. Changes are picked up on save; there is no nightly run to wait
for.
FAQ & troubleshooting
I cannot find a record that clearly exists. Check in this order: do you hold the permission for that data? Is the brand right? Is the owning module active? Only after that is a missing index entry the likely cause.
A colleague finds more than I do. That is normal with different permissions or brand assignments — not a fault.
The search could not be executed. A notice replaces the results. Retry the search; if it persists, the cause lies in the search service and belongs with your administrator.
I am looking for a term inside a document's content. What is searched is the content the modules have registered. Whether the full text of an uploaded file is included depends on the setup — see Documents.