Skip to content
N1
Laravel · Vue/Inertia · cabinet

Laravel Client Cabinet

Category: Cabinets Stack: Laravel, Vue/Inertia, PostgreSQL, Redis Timeline: 2–6 weeks
Problem

Clients had nowhere to see statuses, requests and invoices on their own; everything went through support.

Constraints

Role-based access control, data security, connection to CRM data.

What I did
  • Authentication and roles
  • Requests and statuses
  • Messages
  • Invoices and documents
  • CRM integration
  • Action logs and basic security
Architecture
Frontend (Vue/Inertia) Laravel API Service layer PostgreSQL / Redis CRM exchange
Result

Part of the requests moved to self-service, the load on support dropped.

What can be reused
Cabinet skeleton Roles and access CRM exchange layer