Laravel · Vue/Inertia · cabinet
Laravel Client Cabinet
Client:
NDA
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
Related services and solutions
Services
A Laravel backend you can maintain
APIs, admin panels, client cabinets and integration hubs on Laravel — with logs, tests and a clear structure.
Services
Client cabinets on Laravel or Bitrix24
An external product cabinet on Laravel or a cabinet on top of Bitrix24 when the data already lives in the CRM.
Ready-made solutions
Laravel Client Cabinet
An external cabinet for clients: requests, statuses, messages, documents, invoices, notifications.
Ready-made solutions
Bitrix24 Client Cabinet
A cabinet on top of CRM data: requests, deals, invoices, statuses, messages.