Skip to main content

Automatic page discovery

Registered pages must pass their native canAccess() check. Pages that do not register navigation are omitted unless you explicitly include them. Resource categories keep their own native eligibility rules.

Include a hidden registered page

The page must still be registered with the panel and pass access checks. includePages() is not an authorization bypass and does not register a new route.

Add aliases

Aliases help match navigation labels. They do not add database columns to a resource’s searchable attributes.

Define search-only groups

Search grouping does not rename or move the native sidebar groups. searchGroups(false) stops group labels contributing to navigation matching.

Bounded fuzzy matching

Accepted distances are 1 and 2. This is bounded matching for catalog labels/aliases, not fuzzy SQL search of every record. Native resource query matching remains native. Long or unsupported fuzzy text falls back to ordinary matching rather than unrestricted edit-distance work.

Limit the navigation catalog

The accepted range is 1 to 200. This is separate from record page size and native resource result limits.

Modify navigation items

$origin is the registered page’s class name for a page item, or the source ID for a source item. Return a SearchItem or null. Source/page access is still checked before an item is presented. For business access rules, prefer authorization rather than filtering navigation items.