Roles or Groups
Reddishye opened this issue · comments
In the context of web application development using Laravel Jetstream, the necessity for predefined roles or groups is a significant consideration for enhancing user management and access control efficiency. Jetstream, a scaffolding package for Laravel, offers a robust authentication and team management system. However, its default team-based system often does not align with the requirements of many applications, which are better served by a more traditional role-based access control (RBAC) system.
The team feature in Jetstream, while well-intentioned, is frequently underutilized or unnecessary for many projects. This feature allows users to group into teams, where each team can have specific permissions and roles. However, this model is not always applicable, especially in applications where individual user roles and permissions (not grouped by teams) are more relevant. For instance, a blogging platform or a corporate website may require roles like 'Admin', 'Editor', and 'Viewer', which do not benefit from being segmented into teams.
Despite the existing capabilities of Jetstream's team feature, there is a noticeable demand within the community for a more straightforward, predefined roles system. This need is evident from multiple requests and discussions in community forums and on GitHub, where developers express a preference for a simpler and more direct way to manage user permissions and roles without the overhead of team management. Ignoring this demand could be seen as an oversight, as it is a clear call from the community for features that align more closely with the common requirements of web applications.
Implementing a predefined roles system in Jetstream would not only meet community demand but also enhance the package's flexibility and appeal. It would simplify the developer's task by providing a ready-to-use solution that can be easily integrated and managed within a variety of projects, without the need to modify or disable the teams feature. This approach would allow developers to focus more on the unique aspects of their applications rather than on customizing basic user management functionalities.
In conclusion, while Jetstream's teams feature has its merits, the overwhelming feedback and repeated requests from the Laravel community clearly indicate a strong preference for a more traditional roles system. It would be prudent for the maintainers of Jetstream to consider this feedback seriously and adapt the package to include predefined roles or groups as a standard feature, thereby aligning more closely with the needs and expectations of the developer community.
We don't have any plans for this sorry.
Ok, thanks at least for responding, although would be lovely to see this feature on Jetstream, same as a premade seeder to create and modify api permissions