Weave Code
Control Laravel Package
orchestra/control
Orchestra Control adds a Laravel admin control panel to Orchestra Platform, providing resource-based CRUD scaffolding, navigation menus, and extension hooks so you can build consistent back-office interfaces quickly.
Orchestra Control provides the administrative control panel for Orchestra Platform, giving Laravel applications a central place to manage users, roles, extensions, and application settings. It builds on Orchestra’s foundation and authorization layers, so admin screens stay consistent, secure, and easy to extend.
- Central dashboard for day-to-day administration
- User, role, and permission management
- Extension and package management
- Configurable navigation and admin menus
- Blade-powered, customizable UI
Frequently asked questions about Control
- Which Laravel versions does orchestra/control support?
- Version 5.0.0 of orchestra/control targets Laravel 7, so it is not a fit for modern Laravel releases out of the box. Laravel 7 is end-of-life, so adopting this package means inheriting the framework patch burden. If you are on Laravel 8 or newer, stop and evaluate Filament, Nova, or Backpack instead of forcing this package onto a newer framework.
- How do I install orchestra/control in a Laravel application?
- Install it with composer require orchestra/control:^5.0, then publish the service provider configuration and views and run the migrations. After that you can reach the control panel at /admin or /orchestra. The package is not standalone, so orchestra/foundation and orchestra/authorization must already be present and configured in the same application.
- Is orchestra/control a standalone admin panel I can drop into any Laravel app?
- No. orchestra/control is the control-panel layer of Orchestra Platform and depends on orchestra/foundation and orchestra/authorization for its memory and ACL layers. It consumes Foundation's authorization bindings to render screens for users, roles, permissions, and extensions. The real decision is whether to adopt or retain Orchestra Platform, not whether to add an admin panel.
- What happens if my application already uses the /admin route prefix?
- Route ownership is a hard gate: /admin and the admin.* route name prefix must be free before you install. If they are already in use, collisions can land silently rather than failing loudly. Reconcile middleware groups, prefixes, and route names against your existing application before committing to the package.
- How does orchestra/control v5 sync roles and ACL permissions?
- Version 5 replaces Orchestra\Control\Command\Synchronizer with Orchestra\Foundation\Jobs\SyncDefaultAuthorization, which runs as a queued job. That shifts permission state from a deploy-time command to an eventually consistent background process. Correctness now depends on queue health in every environment, including CI, rather than on a deploy step's exit code.
- Does Orchestra Control's ACL integrate with Laravel's native Gate and policies?
- The release notes do not clearly state whether the ACL bridges to Laravel's native Gate and policies or uses a bespoke authorization model. This must be verified before commitment, because the answer determines whether application code carries a second, parallel permission model. Also confirm how ability caches are invalidated after a sync job runs.
- How do I upgrade orchestra/control and orchestra/foundation safely?
- Upgrade both packages together in the same branch and lockfile, since Control and Foundation must move in lockstep. A partial upgrade fails at the dispatch site where SyncDefaultAuthorization is invoked. Sweep app/, database/, routes/, config/, deploy scripts, CI workflows, seeders, and runbooks for references to Command\Synchronizer and the control:synchronize command before merging.
- What are the alternatives to orchestra/control for a Laravel admin panel?
- For Laravel 8 and newer, Filament, Laravel Nova, and Backpack for Laravel are the common choices and are actively maintained. orchestra/control only makes sense if you have already committed to Orchestra Platform on Laravel 7. It is a poor fit for consumer-facing surfaces, auth-only needs, or teams standardizing on a modern admin stack.
- Can I customize the Orchestra Control admin UI, menus, and extensions?
- Yes. The package ships Blade-powered views that can be published and customized, plus configurable navigation and admin menu registration. It also includes resource-based CRUD scaffolding and extension hooks so back-office screens stay consistent with the rest of Orchestra Platform. Customization work is tied to Orchestra conventions, so your team should be fluent in them.
- Is orchestra/control actively maintained, and what is the long-term risk?
- Adoption is near zero with no dependents and no community corpus, so troubleshooting means reading vendor source rather than searching forums. It is unclear whether a maintained line exists beyond v5.0.0, and the release notes leave supported PHP versions and ACL migration idempotency unanswered. Before committing, confirm who maintains the repository, whether a security policy exists, and what the exit cost would be if the platform is abandoned.
Weaver
How can I help you explore Laravel packages today?