- How do I install awcodes/filament-quick-create in a Laravel Filament panel?
- Install it with Composer using composer require awcodes/filament-quick-create. Then register the plugin in your panel provider by adding QuickCreatePlugin::make() to the panel's plugins() array. You also need a custom Filament theme, and you must add the package's views to your theme CSS with an @source directive pointing at vendor/awcodes/filament-quick-create/resources/**/*.blade.php before rebuilding assets.
- Which Filament versions does filament-quick-create support?
- The package maintains a strict one-to-one release mapping with Filament: 2.x for Filament 2.x, 3.x for Filament 3.x, 4.x for Filament 4.x, and 5.x for both Filament 4.x and 5.x. That means every Filament major upgrade is a paired upgrade with this plugin. It has kept pace through Filament 5, but plan for the dependency to ride your upgrade train.
- How do I include or exclude specific resources from the Quick Create dropdown?
- By default the dropdown lists all resources registered with the current Filament context, filtered by create authorization. Use includes() to whitelist specific resources or excludes() to filter them out. The two methods are not designed to be used together, so pick one approach per panel to avoid unexpected results.
- Does Quick Create respect Filament's create authorization and policies?
- Yes. The plugin does not reimplement authorization; it inherits Filament's own create checks and only lists resources the current user is allowed to create records for. If a user lacks create permission for a resource, that resource simply will not appear in the dropdown. This inherited authorization is the main reason the package is considered safe to add to an existing panel.
- How do I customize the Quick Create label, icon, sorting, or where it renders?
- The plugin exposes a fluent config surface, including label(), sort(), sortBy('navigation'), rounded(), hiddenIcons(), and slideOver(). You can also change the render location with renderUsingHook(); the default hook is panels::user-menu.before. Because everything is a chainable modifier, you can scope and soften the feature without forking the package.
- Does Quick Create work with resources that have custom create pages or wizard forms?
- Resources with modal-friendly create forms open in a modal inside the panel; resources that are not modal-friendly redirect to the resource's create page instead. Resources with mount() side effects, multi-step wizards, required query parameters, or custom post-create redirects may not behave identically in the modal path. Test those flows explicitly, since the failure mode is silent divergence in business logic rather than an error.
- How do I add the Quick Create view path to my Filament theme CSS?
- Filament requires a custom theme for panels, so set that up first following the Filament styling docs. Then add the line @source '../../../../vendor/awcodes/filament-quick-create/resources/**/*.blade.php'; to your theme CSS file. After that, rebuild your assets so the plugin's Tailwind classes are compiled into the theme.
- Can I conditionally hide the Quick Create dropdown, for example per tenant or during onboarding?
- Yes, use the hidden() modifier with a closure, for example hidden(fn () => Filament::getTenant()->requiresOnboarding()). Tenant-aware logic is your responsibility rather than the plugin's. Confirm that tenant scoping and per-panel resource registration behave as expected in your setup, especially on multi-panel or multi-tenant applications.
- How do I add keyboard shortcuts or a create-another option to Quick Create?
- Use keyBindings() to configure keyboard shortcuts for opening the menu or specific resources, and createAnother() to keep the modal open for creating multiple records in a row. Related modifiers such as alwaysShowModal() let you force the modal path instead of redirecting to a create page. These are chainable on the plugin instance in your panel provider.
- Is filament-quick-create safe to use in production and actively maintained?
- It is a thin, purely additive header widget with no migrations, config file, or domain-layer changes, so rolling it back means removing the plugin line and running composer remove. The main risks are version coupling to Filament internals and a small ecosystem footprint: a single primary maintainer with community PRs and a modest star count. Recent patch releases fixed Livewire and cachedMountedActions issues, so pin versions and re-test after Filament patch bumps.