- What is oliuz/teamwork and what does it do?
- oliuz/teamwork is a Laravel Composer package for adding team management to an application. It provides models, migrations, and traits for teams, members, invitations, roles, and permissions, simplifying membership and access control. It is framework-coupled to Laravel and tracks Laravel major versions.
- How do I install oliuz/teamwork in a Laravel application?
- Install it with Composer using composer require oliuz/teamwork, then publish and run any migrations and configuration the package provides. Confirm the package's composer.json constraints for PHP and illuminate/support before installing, especially on Laravel 8 estates. Run your application test suite and smoke-test service-provider registration, config publishing, and published assets after installation.
- Which Laravel versions does oliuz/teamwork 9.0.0 support?
- The 9.0.0 release note states that it added support for Laravel 9 and dropped Laravel 6 and 7. Laravel 8 support is not explicitly stated in that note, so you must verify the illuminate/support constraint in the package's composer.json. Applications on Laravel 6 or 7 are hard-incompatible with this release.
- Does oliuz/teamwork still support Laravel 8?
- The release note only says Laravel 9 support was added and Laravel 6 and 7 were dropped, leaving Laravel 8 ambiguous. Check the composer.json require constraints for the exact illuminate/support range before adopting v9. If Laravel 8 is not permitted, either pin to the last compatible package major or upgrade the application to Laravel 9 first.
- How do teams, members, and invitations work in the oliuz/teamwork package?
- The package provides models, migrations, and traits for teams, members, invitations, roles, and permissions. Teams contain members, invitations handle joining a team, and roles plus permissions support access control. Exact API surface and behavior still need verification against the package source and README.
- How do I publish oliuz/teamwork migrations and config?
- Use Laravel's vendor:publish command to publish the package's configuration and migrations, then run php artisan migrate. Verify whether v9 changed the config schema or published assets, since a major bump permits changes the release note does not enumerate. If you published artifacts from v8, confirm they remain valid under v9.
- Will upgrading to oliuz/teamwork 9.0.0 break my existing code?
- A major version bump permits breaking changes, and the 9.0.0 release note does not enumerate whether the package's own public API, config schema, or published assets changed. Laravel 6 and 7 applications are definitely broken by this release. For Laravel 9 applications, adopt v9 in a branch, run unit and integration tests, and smoke-test service providers, facades, helpers, and config publishing before rollout.
- How should I test team invitations and roles with oliuz/teamwork?
- Use Laravel's standard testing tools to cover membership creation, invitation acceptance, role assignment, and permission checks. Test service-provider registration and published configuration in a fresh application boot. Run the suite on a canary service before broad adoption, and rehearse a rollback to the prior package version.
- Is oliuz/teamwork safe for production and actively maintained?
- Maintenance cadence appears tied to Laravel's annual major cycle, so expect each Laravel major to require a corresponding package major and old framework support to be dropped. The maintainback policy, security-fix window for older majors, and test matrix are not stated in the available input and should be confirmed. Budget a yearly dependency-review and upgrade window rather than assuming long-term support.
- What alternatives exist for Laravel team and invitation management?
- Alternatives include Laravel Jetstream's team features, building team and invitation logic in-house, or combining a permissions package such as spatie/laravel-permission with custom team models. Evaluate each against your Laravel and PHP version constraints, public API stability, and maintenance policy. Verify composer.json constraints and test coverage before standardizing on any option.