Weave Code
User Bundle Laravel Package
kimai/user-bundle
Symfony bundle that adds user management to Kimai, including user entities, roles, authentication integration, and admin screens for creating, editing, and organizing users within the time-tracking application.
Kimai User Bundle provides the user, team, and permission management foundation for Kimai applications. It integrates with Symfony Security to handle user data, roles, and access control while keeping user administration modular and reusable.
- User management with entities, repositories, and profile data
- Role and permission handling for fine-grained access control
- Team and organization structures for grouping users
- Symfony integration for security, forms, and dependency injection
- Extensible foundation for custom Kimai user workflows
Frequently asked questions about User Bundle
- Is kimai/user-bundle compatible with Laravel?
- No. It is a Symfony bundle built for the Kimai time-tracking application and depends on Symfony Kernel, Security, Doctrine ORM, Twig, and form types. It is not a Laravel package, and installing it in a Laravel app would require a substantial bridge. That bridge would cost more than using Laravel-native auth and permission tooling.
- Can I install kimai/user-bundle with Composer in a Laravel project?
- Composer may resolve it only in a compatible Symfony environment, but the bundle expects the host application to provide schema, security configuration, routing, and Kimai domain entities. In Laravel it is effectively unusable without reimplementation. Use Laravel authentication and spatie/laravel-permission instead.
- What Laravel versions does kimai/user-bundle support?
- None. It does not target Laravel at all; its published constraints are Symfony 5.x-era with Doctrine ORM 2.x and PHP 7.4 to 8.0. It is archived with a last release of 2022-11-26, so current Laravel and PHP stacks are outside its scope.
- What PHP and Symfony versions does kimai/user-bundle require?
- The bundle is aligned with Symfony 5.x, Doctrine ORM 2.x, and PHP 7.4 to 8.0. Modern targets such as PHP 8.2+, Symfony 6 or 7, and Doctrine 3 are outside its published constraints. Expect resolution conflicts if you try to use it on a current stack.
- Does kimai/user-bundle provide roles, permissions, and teams?
- It exposes the user, role, team, and user-preference domain for Kimai, but those entities carry relations into Kimai core concepts such as timesheets, activities, projects, and customers. It is not a standalone roles and permissions library. For Laravel, use spatie/laravel-permission plus your own team or tenant model.
- Can I use kimai/user-bundle for authentication in Laravel?
- No. It integrates with Symfony Security, not Laravel auth guards, middleware, sessions, or password brokers. You would need to write a bridge, and a bridge to a user module is more work than using Laravel native auth scaffolding. Treat it as a reference design only.
- Is kimai/user-bundle maintained and safe for production?
- It is archived, last released on 2022-11-26, and is a read-only subtree split from the Kimai monorepo. Security fixes for Symfony 4 and 5-era dependencies will not flow through this package, so you inherit the CVE surface and own remediation. For production Laravel work, do not adopt it as a dependency.
- What are the best Laravel alternatives to kimai/user-bundle?
- Use Laravel built-in authentication scaffolding for identity, spatie/laravel-permission for roles and permissions, and a small team or tenant model if you need scoping. If you run Kimai itself, use the actively maintained Kimai monorepo instead of this split. These paths cost days, not weeks, and carry a maintained security posture.
- Does kimai/user-bundle include tests or documentation?
- No. There is no public API contract, no documentation, and no tests published with the split. The repository is an internal module published for packaging reasons and has zero standalone dependents. That makes it a poor candidate for external adoption.
- Why does kimai/user-bundle have BC breaks compared with FOSUserBundle?
- It was designed as a Kimai-specific replacement for FOSUserBundle, so its user model and Symfony integration differ from the general-purpose bundle. The BC breaks reflect Kimai domain needs and are not aimed at Laravel or general Symfony reuse. Do not assume drop-in compatibility with FOSUserBundle or any Laravel user model.
Weaver
How can I help you explore Laravel packages today?