- What is coringawc/filament-acl used for?
- coringawc/filament-acl is a Filament plugin for managing roles and permissions inside a Laravel admin panel. It helps define access controls, assign roles to users, and protect Filament resources and pages with per-resource permissions. It is aimed at developers who want an integrated ACL workflow rather than only code-level policies.
- How do I install coringawc/filament-acl?
- Install it with Composer using composer require coringawc/filament-acl, then follow the package README for any required migrations, config publishing, and Filament panel registration. Exact steps can vary by package version, so check the repository instructions for your Laravel and Filament versions. After installation, clear caches and verify the plugin appears in your panel.
- Does Filament ACL support per-resource permissions?
- Yes, the package is described as solving ACL per-resource permissions in Filament. That means you can define permissions around individual Filament resources rather than relying only on broad role checks. You should still verify the exact API and behavior in the package documentation for your version.
- Which Laravel and Filament versions are supported by coringawc/filament-acl?
- The repository and package metadata are the authoritative source for supported Laravel and Filament versions. Check the composer.json requirements and README before installing, because Filament major versions can have different plugin APIs. If your app uses an older Laravel or Filament release, verify compatibility first.
- How do I assign roles and permissions to users with Filament ACL?
- The plugin provides an integrated workflow for creating roles and permissions and assigning them to users in Filament. You typically manage these records through the admin panel or seed them in your application. Then enforce them on resources and pages according to the package's authorization setup.
- Can Filament ACL protect custom Filament pages as well as resources?
- The overview says it protects resources and pages, so custom Filament pages can be part of the ACL workflow. The exact method for registering page permissions may depend on the plugin version and your panel configuration. Check the README for page-level authorization examples.
- Do I need to publish migrations or config after installing Filament ACL?
- Installation may require publishing and running migrations for roles and permissions, and possibly publishing config. Follow the package README because exact publish tags and migration steps are version-specific. Always run migrations in a local or staging environment before production.
- How should I test role and permission behavior with Filament ACL?
- Test role and permission behavior with Laravel feature tests that act as users with different roles. Assert that authorized users can access Filament resources and pages while unauthorized users are denied. Use factories or seeders to create roles and permissions consistently in your test database.
- Is coringawc/filament-acl suitable for production Laravel applications?
- It is designed for Filament admin panels, so it can be suitable for production when installed and configured correctly. Review migrations, permission seeding, and access policies in staging first. Also confirm compatibility with your Laravel and Filament versions before deploying.
- What alternatives exist to Filament ACL for Laravel admin permissions?
- Alternatives include building ACL with Laravel gates and policies, using Filament's built-in authorization features, or combining Filament with a role and permission package. The best choice depends on whether you need per-resource UI management or only code-defined policies. Compare maintenance and Filament integration before switching.