Getting Started

Install/upgrade the plugin and ensure filament-analytics-core is at least 3.1; the new navigation grouping depends on it.
Register the plugin in your Filament panel provider as usual, then chain the new API:
```
->plugin(
    Plugin::make()
        ->navigationGroup('Analytics')
)
```
Look first at your panel provider and the plugin registration block. That is where the settings page’s navigation placement is now controlled.
First use case: move the analytics settings page out of its default translated group and into an existing panel navigation group such as “Reports”, “Insights”, or “System”.

Implementation Patterns

Static grouping for consistent admin navigation:
```
Plugin::make()->navigationGroup('Analytics')
```
Dynamic grouping with a closure when the group depends on panel, tenant, role, or locale:
```
Plugin::make()->navigationGroup(fn () => __('Reports'))
```
Multi-panel apps: call navigationGroup() per panel registration so each panel can use its own group naming convention.
Keep group names aligned with the strings used by your Filament resources and pages. Filament groups by matching navigation group labels, so exact consistency matters.
Pair with existing navigation customisation on the plugin/page where available, such as label, icon, or sort, to keep the settings entry visually consistent with neighbouring pages.
If you already centralise navigation labels in translation files, return the same translation key from the closure rather than hard-coding a string.
Use the closure form when group names differ by tenant or permission context, but keep the closure cheap and deterministic because it participates in navigation rendering.

This only changes the settings page navigation group. If the group still looks wrong, check that other pages/resources use the same group string.
filament-analytics-core >= 3.1 is required. An older core version can silently leave you on the translated default group.
Without calling navigationGroup(), the plugin intentionally keeps its translated default group. That is not a regression; it is the fallback behaviour.
The closure must return a string. Returning null, an array, or a NavigationGroup object is outside the documented signature.
Group matching is label-based. A translated label in one place and a hard-coded English label in another will produce two groups.
In localized panels, prefer fn () => __('...') so the group follows the active locale.
If navigation is cached by your application or Filament panel, clear caches after changing group configuration.
Do not confuse this with parent-item nesting; this sets the top-level navigation group only.
For extension, wrap repeated group logic in your own panel-provider helper or base plugin configuration if several panels share the same rules.