Filament Wildcard Login Laravel Package

Product Decisions This Supports

• QA and demo velocity: A wildcard/pattern-based login lets QA, designers, and sales engineers enter a seeded or pattern-matched account without juggling per-user credentials. This shortens review cycles for multi-role admin panels and reduces "can you reset my staging password" interruptions.
• Build vs. buy: This is a small, single-purpose Filament plugin. It replaces a custom "login as user" implementation you would otherwise maintain in-house. Adopt it as a dev dependency rather than spending engineering time on impersonation plumbing.
• Roadmap gating on Filament 5: v3.0.0 upgrades the package to Filament 5. This effectively ties the plugin's usable version to your admin panel's framework generation — v3.x for Filament 5 applications, v2.x for Filament 3/4 applications. Treat the Filament major as the decision variable, not the plugin version itself.
• Support-surface reduction: Keeping this out of the production dependency set (dev/staging only) means framework bump maintenance here costs you a Composer constraint change, not a security review.

When to Consider This Package

Adopt when:

• Your team runs a Filament-based admin panel and routinely needs to sign in as different roles/users for review, support reproduction, or seed-data demos.
• Your application is already on, or actively migrating to, Filament 5 — only v3.0.0 is relevant to you. If you are still on Filament 3 or 4, stay on v2.x and do not upgrade.
• You have a clear environment guard (local/staging only) and are comfortable with a pattern-matching login path existing in your codebase behind an environment flag.

Look elsewhere or skip when:

• You need audited, production-grade impersonation. Prefer a first-party impersonation feature with logging, permission checks, and session recording.
• You are mid-migration across Filament majors — the plugin's version now moves in lockstep with Filament, so it will amplify rather than absorb that migration.
• Your admin panel is not Filament, or you need multi-guard/SSO-aware authentication.

Caveats for this release specifically: the v3.0.0 notes are dominated by Dependabot and CI action bumps; the only functional change is the Filament 5 update. There are no stated new features, deprecations, or migration notes. That means the breaking surface is implicit — the plugin now targets a new Filament major — and the upgrade path is only as safe as your Filament 4→5 migration. Verify on a branch before merging; do not treat this as a routine patch.

How to Pitch It (Stakeholders)

For executives: This is a small developer-productivity plugin for our admin panel that removes friction when staff or partners need to review the product as a specific user type. v3.0.0 is a maintenance release that keeps it compatible with the newest version of our admin framework. It carries no new product capability, and it does not change anything customers see. Cost of adoption is low; the only real cost is coordinating the upgrade with our Filament 5 migration.

For engineering: v3.0.0 is a compatibility release — Filament 5 support. There are no new features, no deprecations, and no migration guide; the breaking change is the framework major it now requires. Sequence this after the application is on Filament 5, land it behind the existing environment gate, and confirm the plugin is not enabled in production config. Keep it in require-dev and pin the major version so a future Filament bump cannot silently pull a new plugin major. If we are not yet on Filament 5, take no action and stay on v2.x.