Filament Employees Laravel Package

Product Decisions This Supports

• HR/people-ops admin build vs buy: Supports using a Filament-native package for employee profiles, attendance, shifts/days off, payroll account/salary administration, applications, notes, and account-linked employee records instead of building these admin workflows from scratch.
• Platform roadmap and upgrade planning: v5 establishes the current compatibility line for Filament v5, Laravel 12/13, Livewire 4, and PHP 8.2+. Teams on Filament v3 should plan to remain on the v3 branch unless they are ready to upgrade the surrounding stack.
• Ecosystem dependency decision: v5 requires tomatophp/filament-accounts, filament-types, and filament-meta at ^5.0, so adoption is a coordinated package-ecosystem decision, not an isolated install.
• Data model ownership: Employee profiles now use tomatophp/filament-meta via HasMeta on IsEmployee. This affects how profile metadata is modeled, migrated, and validated, and should be reviewed before relying on the package for employee records.
• Release readiness and QA prioritization: The release includes fixes across payroll account models and salary, attendance without shift/department, notes authors, config-driven user/account models, migrations, and optional shift days off. These areas should be treated as higher-risk integration points during upgrade testing.
• Vendor health signal: Added factories, a full Pest suite, PHPStan level 0, CI, and README setup guidance improve confidence for engineering evaluation, but host-application integration and payroll/attendance correctness still require project-level validation.

When to Consider This Package

Consider this package when:

• You are building or extending a Filament-based internal HR/people-ops admin panel and need employee, attendance, shift, payroll-account, application, and notes workflows.
• Your application is on, or can move to, Laravel 12/13, Filament v5, Livewire 4, and PHP 8.2+ for the v5 line.
• You already use, or are willing to adopt, the tomatophp/filament-accounts, filament-types, and filament-meta ^5.0 ecosystem.
• You want config-driven user/account models and metadata-backed employee profiles rather than fully bespoke models.
• You need accelerated admin CRUD and workflow scaffolding, and can invest in integration testing around attendance, shifts, payroll, and account setup.

Look elsewhere or defer when:

• You are on Filament v3 and are not ready to upgrade; the v3 branch is the relevant line, not v5.
• You cannot accept coordinated major-version constraints across the Filament/Tomatophp package set.
• You need a standalone HR/payroll system with compliance, tax, benefits, or time-clock integrations that are not evidenced in this release.
• Your requirements are primarily complex payroll/legal compliance rather than Filament admin workflow acceleration; validate scope carefully before adopting.
• You cannot allocate migration and QA effort for employee metadata, payroll account/salary behavior, attendance rules, and config-driven models.

How to Pitch It (Stakeholders)

For executives: This package can accelerate delivery of an internal HR/people-ops admin experience inside Filament, covering employee records, attendance, shifts, payroll account administration, applications, and notes. The new v5 release aligns it with the current Filament v5 / Laravel 12–13 stack and adds stronger engineering signals through factories, Pest tests, PHPStan, and CI. The main trade-off is platform coupling: v5 requires PHP 8.2+, Livewire 4, and coordinated ^5.0 Tomatophp packages. Treat the upgrade as a platform decision with targeted QA on payroll and attendance, not a drop-in patch.

For engineering: v5 is a major compatibility release. It moves the employee profile to filament-meta via HasMeta, requires the ^5.0 account/types/meta packages, and continues the Filament v3 line separately on the v3 branch. The release also fixes several payroll, attendance, notes-author, config-model, migration, and UI issues. Recommended approach: confirm the host app is on the v5 support matrix, update the dependency set together, validate metadata migration/backfill for employees, run integration tests around attendance without shift/department, optional days off, payroll account/salary, config-driven user/account models, and migration rollbacks, and avoid assuming the package’s internal test suite replaces host-application acceptance testing.