Filament Tawk To Laravel Package

Product Decisions This Supports

• Information architecture / UX polish in admin panels: teams can now slot the analytics settings page into an existing navigation group instead of accepting the package's translated default group, keeping the admin sidebar consistent with the rest of the product. This is a small but user-visible customization win that reduces "one odd menu item" complaints.
• Multi-panel and white-label deployments: because navigationGroup() accepts a Closure, the group can be resolved per-panel or per-tenant at runtime — useful if you ship one codebase to several brands or customer-specific panels, and previously required awkward workarounds (custom pages, view overrides, or forking the plugin).
• Build vs. buy: reinforces buying/adopting the package rather than hand-rolling settings screens. Each minor release absorbs a customization request you would otherwise have had to implement and maintain yourself.
• Roadmap signal: the maintainers are responsive to integration ergonomics, not just analytics features. Minor, additive API changes at a steady cadence suggest a healthy, actively maintained dependency — favourable for planning upgrades.
• Low-cost upgrade: no migration, no config change, no breaking API. The default behaviour (translated group) is preserved, so it can be adopted opportunistically — e.g. bundled into the next scheduled dependency bump rather than a dedicated work item.

When to Consider This Package

Adopt (or upgrade to 3.1.0) when:

• You are already running Filament panels and want analytics/settings surfaced inside the panel rather than a separate dashboard.
• Your panel already has a defined navigation grouping convention and you want the package to conform to it — this release is exactly that requirement.
• You run multiple panels or tenant-scoped panels where the navigation group must differ per panel (use the Closure form).
• You are on filament-analytics-core 3.1 or can upgrade to it — this is a hard prerequisite; navigationGroup() will not be available on older core versions, so the upgrade is effectively a paired bump.
• You are standardising dependency versions across a team and want a low-risk, additive minor release to include.

Look elsewhere or defer when:

• You do not use Filament, or you have deliberately decoupled admin UI from the analytics backend (in which case only the core package matters).
• You are pinned to filament-analytics-core < 3.1 for compatibility reasons — adopting this release then requires a coordinated upgrade of both packages, which is a bigger decision than the release note implies.
• You need deeper navigation control (ordering, icons, badges, conditional visibility) — a single group setter may not cover complex requirements, and a custom Filament page wrapper may still be preferable.
• You require long-term support guarantees or a formal deprecation policy; nothing in this release speaks to that, so vet the maintainer's release history first.

How to Pitch It (Stakeholders)

For executives: A routine, low-risk minor upgrade to an admin-panel dependency. It gives us the ability to place the analytics settings screen inside our own menu structure instead of an out-of-place default group — a small consistency and polish improvement for internal users and for clients on white-labelled panels. No migrations, no downtime, no behaviour change unless we opt in.

For engineering: Version 3.1.0 adds Plugin::make()->navigationGroup(string|Closure) to the settings plugin, letting the settings page join one of the panel's existing navigation groups; if unset, the current translated group is retained, so the change is fully backwards compatible. The Closure variant supports per-panel resolution. The one dependency note is that it requires filament-analytics-core 3.1 — treat the two upgrades as a single, paired bump. Recommend folding it into the next regular dependency update rather than scheduling separate work; add a quick check that existing panel navigation renders as expected after the bump.