- What does Filament Organizational Shield actually do?
- It is a Filament plugin that adds organizational hierarchy based access control to your admin panel. Resources, queries, and actions are scoped by department, team, or branch so users only see and manage data relevant to their position. Instead of building custom scoping logic into every resource, you configure the hierarchy once and let the plugin enforce it.
- How do I install iracode-com/filament-organizational-shield?
- Install it with Composer using the package name iracode-com/filament-organizational-shield. Then publish and review the package configuration and register the plugin in your Filament panel provider. Check the repository README for the exact install command and any required migrations or assets.
- Which Laravel and Filament versions are supported?
- The package targets Laravel applications running Filament, but version constraints can change between releases. Check the requirements section of the composer.json on Packagist or the repository before installing. That is the most reliable way to confirm compatibility with your Laravel and Filament versions.
- How do I configure departments, teams, and branches?
- The plugin is built around organizational hierarchy levels such as department, team, and branch. You define how those levels relate to your users and records, typically in the published package configuration and through your existing models. Start by mapping your current organizational structure to the levels the plugin supports.
- How does it scope Filament resources and queries?
- It applies hierarchy based scoping to Filament resources and their underlying queries so records outside a user's organizational scope are filtered out. That means list tables, relation managers, and similar data views respect the same boundaries. The goal is to avoid writing per-resource scoping code yourself.
- Can I restrict Filament actions and bulk actions by hierarchy?
- Yes, the package is described as scoping actions as well as resources and queries. Actions and bulk operations can be limited to records within the user's department, team, or branch. This prevents users from acting on records they would not be allowed to view.
- Does it work alongside Spatie Laravel Permission or Filament Shield?
- Hierarchy scoping and role-based permissions solve different problems, so they are often used together. Role and permission packages decide what a user is allowed to do, while this plugin limits which records they can reach. Keep your policies and permissions in place and layer organizational scoping on top.
- How do I test organizational access control in my application?
- Write feature tests that authenticate users at different hierarchy levels and assert which records appear in Filament resource queries and tables. Cover actions and bulk actions as well, since those are scoped too. Testing with at least two branches or departments quickly reveals scoping gaps.
- Is it safe to use in production and will it affect performance?
- The plugin adds constraints to Filament queries, so the main performance concern is whether your hierarchy columns and foreign keys are indexed. Review the generated query scopes and add indexes on department, team, and branch identifiers. Test against realistic data volumes before relying on it in production.
- What are alternatives to Filament Organizational Shield?
- You can implement similar behavior with Filament's built-in multi-tenancy, global query scopes, and Laravel policies, or with a permissions package such as Spatie Laravel Permission combined with custom scoping. The trade-off is more custom code but full control. This plugin is worth considering when your hierarchy maps cleanly to departments, teams, and branches.