- How do I install panservicesas/filament-users in a Laravel app?
- Install it with Composer, then register the plugin on your Filament panel and publish any config or assets the package ships. The main prerequisite is that your panel's auth guard points at the same provider as the User model the resource queries. Installation is low effort; the real work is deciding who may impersonate whom and confirming your authorization layer is actually consulted.
- Which Laravel and Filament versions does filament-users support?
- The package is a Filament panel plugin pinned to Filament's resource and action APIs, so its supported Filament major must match the one in your app. Exact version ranges and the stated support window are not documented in the overview and should be confirmed with the maintainer before committing. Pin the package with a caret constraint and commit your lockfile so Filament upgrades stay a coordinated change.
- Does filament-users integrate with Spatie roles and permissions?
- The package is built for managing users with role and permission support, but it is a presentation-layer plugin rather than a domain package. It assumes your Laravel app already owns the User model, auth guards, and role and permission wiring, so it does not replace your permission tables or authorization logic. If your roles are modelled differently, expect to adjust the shipped resource.
- Is impersonation in filament-users safe for production?
- Version 2.5.2 adds a confirmation modal before impersonating, which removes an obvious single-misclick path, but a confirm dialog is UX rather than a control. There is no evidence in the release of audit logging, session-scoped impersonation tokens, or a return-to-admin affordance. Treat impersonation as a compliance-relevant feature and add your own logging of actor, target, and timestamp regardless of what the package provides.
- Does the filament-users UserResource enforce Laravel policies and gates?
- This is one of the key questions to resolve with the maintainer: whether the resource consults your Gates and Policies or whether panel access alone gates it. The package is opinionated and ships a pre-built resource, so verify the behaviour rather than assuming it. If your authorization layer is bypassed, add policy checks or override the resource before exposing it to staff.
- Can I customize the columns, form fields, and actions in filament-users?
- Yes, the UserResource can be overridden or subclassed, but each override is a coupling point that can break on package releases. Version 2.5.2 changed field behaviour, making email copyable and disabling the record URL, with no config flag mentioned. Keep overrides small and covered by tests so minor upgrades do not silently change admin behaviour.
- Can I disable impersonation or other actions in filament-users?
- The overview does not document a config switch for turning impersonation off, so confirm this with the maintainer before relying on it. If no flag exists, remove or gate the action in a resource subclass and retest on each upgrade. For regulated environments, disabling impersonation entirely is often simpler than auditing it.
- Is filament-users a good fit for multi-tenant apps or SSO user stores?
- It is a poor fit when the user domain is non-trivial: multi-tenant scoping, soft-deleted users, and external identity providers all conflict with the resource's assumptions. If auth is delegated to SSO or OIDC and your local users table is a projection, the create and edit flows may write to a table your IdP treats as read-only. In those cases you end up maintaining a fork of a resource class you could have written yourself.
- How do I migrate from a custom user resource to filament-users?
- Do not delete and replace your hand-rolled resource in one step, especially if operators have muscle memory around the existing impersonation flow. Install the plugin alongside, gate it behind a feature flag or a separate panel path, and run both for a sprint. Then deprecate the bespoke resource once the impersonation changeover has been validated.
- Who maintains filament-users and how often is it released?
- The package is published by panservicesas, and the release cadence, support window, and bus factor, whether a single maintainer or a team, are not stated in the overview. Because the plugin is pinned to Filament's APIs, your Filament upgrade is gated on this package's release schedule. Ask the maintainer directly and factor the answer into your upgrade planning.