Search at a glance
Purpose
One search across everything, rather than a search per module. Each area registers what should be searchable about it; finding happens across the boundaries.
The load-bearing decision is invisible and nonetheless the most important: the permission check takes effect while searching, not while displaying. A result you may not see is never produced. If the display did the filtering, the result count alone would reveal that something exists — and that is exactly where many searches in business systems fail.
Scope
- One index across all modules. The core supplies customers and tasks; every module adds its own
result types.
- The index follows the data. Changes are picked up on save; there is no nightly run to wait for.
- Permission and brand filtering inside the index itself.
- A disabled module returns nothing — and does not appear as an empty result type either.
- Reachable from the command palette, without leaving the page.
- An interchangeable search backend. What ships is the database's full-text search; for large
holdings a specialised search service can be placed behind it without the handling changing.
Interplay
The working surface is Search. The same index is also the ground on which the AI platform finds connections — which is why a permission error in search would immediately be a permission error in the AI.
Limits
- Two people find different things. That is not a fault but the consequence of different
permissions and brands.
- What is searched is the registered content. Whether the full text of an uploaded file is
included depends on the setup.
- The index is not reporting. It finds records; figures and totals come from the reporting
module.