Level 104
Single table for me unless there is a compelling reason not to.
Aug 10, 2018
8
Level 2
Admin ,Users ---> separate table VS single table
hi guys. i am new to laravel and i know this is probably a matter of preference.
but i am curious which approach is the best
Level 67
users, roles. Or users, with is_admin flag. A user is a user.
Level 1
@Cronix How amount is a SAAS (Software as a service) system? What are your thoughts on having an admin table for the system managers while users table for tenants (Different organizations subscribers admin users) and other users?
Level 50
@joshuaify My strong opinion is that you shouldn't do it. It can complicate things massively later on. Use roles for authorization instead.
1 like
Level 122
@joshuaify needless complication
Level 3
Also users, roles. Even if there's a single role, it's easier to extend in the future with separate tables, I find.
Level 2
are there any major drawback i should worry bout with any of them .. and which questions or likely situations would require one or the other approach
Level 4
If you decide to build an extra table for the admins you then have to extend the default auth system which is a lot of extra work considering you could simply have a role and do $user->hasRole('admin') when needed.
Another option if you do not want to use roles nor a flag and need extra columns for your admins is to use a one to one relationship. Your admins table can have the user_id as well as the columns you need without messing with Laravel's auth system.
2 likes
Please or to participate in this conversation.