Search

Goal

Find parties and catalog items quickly, and understand how list screens filter data.

Who it is for

Clerks and anyone with catalog.view and/or party.view.

Preconditions

• At least one of catalog.view or party.view for the spotlight search API (GET /api/search).
• Neither permission → 403. Search engine unavailable → 503.

Steps

1. On entity list screens, use the built-in filter/search fields (status, customer, dates, SKU, etc.).
2. CRM users can use CRM search (/crm/search) when the CRM module is on.
3. Integrators / advanced clients may call GET /api/search (items + parties) or GET /api/search/token for a Meilisearch tenant token when configured.
4. Open a result row to the detail/edit form.

Result

You land on the right master data or document without browsing every page.

Hard stops

No catalog/party view permission; search service down (503); module-specific search requires that module.

Note

There is no separate global “command palette” Help screen — search is embedded in lists and domain UIs.

Related

• Customers list
• Items
• Permissions model