Skip to main content

Laravel + Filament Implementation Guide

This section documents how to implement the Law Firm Management System using Laravel 11 and Filament v3. It is an implementation guide — not a replacement for the system specification. The API contracts, database schema, and RBAC model defined in the architecture documentation remain authoritative. This guide describes how to realise those contracts in Laravel.

Relationship to Existing Documentation

Existing DocRoleThis Guide
/database.dbmlDomain model — source of truthAdapts for Laravel (see Schema Changes)
/docs/architecture/API contracts, C4 diagramsImplemented by controllers and Filament resources
/docs/guides/architecture/sequence-diagrams/System flowsSame flows, different stack

Key Implementation Decisions

DecisionChoiceRationale
Auth providerLaravel built-inLogto's JWT-bearer model conflicts with Filament's session-based auth
Admin UIFilament v3Eliminates a separate frontend for internal staff
Application serverLaravel Octane (Swoole)Amortises Filament's heavy boot cost across requests
API auth (mobile)Laravel SanctumLightweight token auth alongside Filament sessions
Multi-tenancyFilament HasTenantsLAW_FIRMS is the tenant boundary

Documents in This Guide

Foundation

Architecture

Authentication & Authorization

Filament

  • Panels — Admin, Client Portal, Partner Portal panel setup
  • Resources — full resource inventory per panel

Domain

Infrastructure

Testing