Weave Code
User Admin Bundle Laravel Package
nucleos/user-admin-bundle
A Symfony bundle that adds ready-made administration screens for NucleosUserBundle, with list, create, edit, and delete actions for users and groups. Manage roles, permissions, profiles, and account settings from a configurable SonataAdminBundle backend with minimal configuration.
NucleosUserAdminBundle provides a ready-to-use administration interface for NucleosUserBundle in Symfony applications. Built on SonataAdminBundle, it lets administrators manage users and groups without creating custom CRUD screens.
- User and group CRUD with searchable, filterable listings
- Role and permission management for accounts
- Configurable admin forms with validation
- Seamless integration with Symfony and Sonata Admin
- Extensible admin classes for project-specific needs
Frequently asked questions about User Admin Bundle
- Can I use NucleosUserAdminBundle in a Laravel application?
- No. NucleosUserAdminBundle is a Symfony bundle, not a Laravel package, and it is not framework-agnostic: it depends on Symfony, Sonata Admin, and NucleosUserBundle. There is no realistic integration path for a Laravel codebase short of rewriting the surrounding application. If you are on Laravel, treat this repository as a reference for the user and group admin surface and use Laravel-native tooling such as Filament or Nova instead.
- What does NucleosUserAdminBundle actually do?
- It provides a ready-made back-office for managing users and groups: list and filter them, create and edit records, and assign group membership. It is essentially an admin layer that configures Sonata Admin classes over the Doctrine entities exposed by NucleosUserBundle. It does not ship its own user model or authentication system.
- How do I install NucleosUserAdminBundle?
- Install it with Composer inside an existing Symfony application, register the bundle in your kernel, and configure the Sonata Admin services to point at your concrete User and Group entity classes. You also need to wire security roles so the admin screens are reachable. The bundle itself is small; the real setup work is Sonata Admin configuration and its asset pipeline.
- Which Symfony and PHP versions does NucleosUserAdminBundle support?
- That is not clearly documented in the available metadata, so verify it against the repository's composer.json and tag history before committing. The release data also shows an inconsistent forward-dated release, which makes the published version timeline unreliable at first glance. Treat any version claim as unverified until you have read the constraints yourself.
- Do I have to use NucleosUserBundle, or can it manage my own User entity?
- NucleosUserBundle appears to be a hard requirement, since this bundle is an admin layer over that package's user and group domain model. You can point the admin at your concrete entity classes, but those classes are expected to follow the bundle's structure. If your application already has a custom user entity or authenticator, expect friction or a rewrite before this fits.
- Which Sonata Admin versions are supported, and how tight is the coupling?
- The bundle is built on Sonata Admin and inherits its asset pipeline, configuration style, and release cadence. Version pinning against Sonata majors is likely to be your dominant upgrade constraint, and there is little visible evidence of how quickly this bundle has tracked new Sonata releases. Check the Composer constraint against Sonata's release timeline before adopting.
- Does it support roles, RBAC, or per-object permissions?
- What it covers natively is the bundle's group model plus whatever the underlying user entity exposes, not a general RBAC or per-object permission system. If your access control is role-based or object-scoped, plan to build that yourself on top of Sonata's security integration. Confirm the actual granularity against the source before assuming it exists.
- Is NucleosUserAdminBundle production-ready and actively maintained?
- The adoption signals are weak: five stars, zero dependents, and no visible production user base, which means little field validation in real applications. There is also a forward-dated release that should be checked against the actual Packagist and GitHub tag history. Expect a small maintainer base, expect Sonata major upgrades to be the main pain point, and budget for owning patches.
- What are the alternatives to NucleosUserAdminBundle?
- On Symfony, compare EasyAdmin plus a hand-rolled user and group CRUD, or extend an existing identity provider's admin screens. On Laravel, the equivalents are Filament, Nova, or a thin custom CRUD over your users table. The deciding factor should be admin framework lock-in rather than this bundle's feature list, which is deliberately small.
- How hard is it to remove NucleosUserAdminBundle later?
- There is no incremental migration path into or out of it; adoption is greenfield-only, and removal means unwinding entities, templates, and services from Sonata conventions. Contain the coupling by keeping schema ownership and domain entities outside the bundle's assumptions. Because the admin UI is the highest-churn part of an application, weigh that exit cost against simply building the screens yourself.
Weaver
How can I help you explore Laravel packages today?