DB design best Practice

No. Just have users table with type column.

You can have just users table and then for different types of users use spatie permissions package

Well, this is similar to my ongoing project. For me, I prefer a different table each of the user type. In my project, I have :

1. Table for Admin
2. Table for Student
3. Table for Academic Staff

Authentication type Oauth (Passport package) Then I control which table to use for authentication through the middleware.

Stick with a single table it's better otherwise you'll be dupplicating the authentication system of laravel..

if you have different relationships for different users go for polymorphic relationships

I would go with a single users table and then have user roles.

There are several ways of doing that.

1. Add the role directly to the users table.
2. Add a foreign key to the users table and have a roles table
3. Use a pivot table to join the user and the role together.

Option 1 should only be used in a system with very few users.

id | username | role
-------------------------------------
1  | user1       | admin
-------------------------------------

Option 2 is for systems with many users

id | username | role_id
-------------------------------------
1  | user1       | 1
-------------------------------------

The role_id references the roles_table

id | role
---------------
1  | admin
---------------

Option 3 is for multi user systems with a possibility to let a user have multipple roles

Users table

id | username 
-------------------
1  | user1       
-------------------

roles table

id | role
---------------
1  | admin
---------------

role_users table

user_id| role_id
-------------------------------------
 1       | 1
-------------------------------------

The other upside to option 3 is that you can use the provided migrations and authentication out of the box.