Skip to main content
Each recipe extends an existing FLEX Theme installation. Import the classes shown in its snippet and replace application resource/model/service classes with your own.

1. Require a category before querying records

Users can find the Customers category first, then enter a query inside it. This avoids calling every root-searchable resource for each root query.

2. A PHP-controlled search without settings UI

3. Only Customers and Orders

The default native root adapter also receives these configured sources. A custom provider must enforce its own resource allowlist.

4. One explicit customer source

This explicitly chooses one source instead of automatically discovering all registered resources. Source and record policies still apply.

5. A source below a parent resource

This assumes native Filament parent-resource registration and a tenant-enabled application. Parent models are re-resolved and authorized; the relationship to each ancestor is verified. Do not populate the selected parent from an unchecked client ID.

6. Search more than one panel

7. Add an authorized help command

8. Open a category from a native action

Here customers is a registered custom source ID. For native resources, derive the source ID in PHP instead of guessing it. See the quickstart event examples.

9. Persist favorites in the database

Run the package migrations and configure a shared lock backend when using multiple servers. History and favorites explains the store contract.
The theme no longer replaces the native global-search view. Your existing native provider remains configured on the panel. Remove or disable FLEX shortcuts separately if your replacement uses different hotkeys.