Wow, one step at a time. Why don't you start with:
https://laravel.com/docs/5.6/authentication#authentication-quickstart
and see where that gets you.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Roles will be helpers, clients, admin. I need to know what type of database logic should be in place and what tables. I need to know what type of authorization or role system should be in place. Should it be multiple authentication or something else? How can I build this to integrate and android app later? Or should I just build the application and that can be done later? It will grow by city slowly. Is there a way to simplify the payment system with less steps? Any help in logic, database logic, and way to setup authentication is appreciated.
Client Posts Job
Client Looks for Helper
Helper Finds Job
Helper meets client in person.
Job will automatically close after x days of inactivity.
@swgj32 I hope you will have a user table defined with rolesassigned to each & every user.
Once the user is authenticated & before redirecting the user to a login success page, fetch the associated predefined roles of that user & based on that redirect the user to specific routes which a user can access but restricted with middleware.
Please follow the docs on Middleware
Create & register new Middlewares for each & every kind of user role & using middlewares you can implement role based user access in your app. Also you will have different routesdefined for each kind of user role.
Refer this Assigning Middleware To Routes
I'm using similar approach in my projects.
If my answer helped you, then please mark this answer as solution.
Please or to participate in this conversation.