# Law firms: client portal using Laravel

## Summary
A client portal blueprint for law firms built with Laravel on Ample. Domain schema:
- **client_entities** (name, entity_type, conflict_check_reference): clients with conflict-check status.
- **matters** (client_entity_id, practice_area, opened_at, closed_at, status): engagement periods as matters.
- **document_requests** (matter_id, title, due_at, status, uploaded_object_key): documents requested from the client.
- **shared_documents** (matter_id, title, object_key, authorized_role): documents released to authorized client contacts.
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

Public information: practice areas and attorney profiles, intake process and fee structure overview, office locations. Kept out of scope until handling is reviewed: privileged communications and case files, identity and financial documents, opposing-party information. Matter documents are privileged; the portal models per-matter authorization only. Professional-conduct and confidentiality obligations are not established here. Technical basis verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

## Representative Queries
- Law firms: client portal using Laravel
- Where can I host Law firms: Client portal built with Laravel?
- I need a genuinely specialized client portal workflow covering matter-based access separation and confidential document handling.

## Workflow Steps
1. **Model the law firms domain**: Create the tables client_entities, matters, document_requests, shared_documents, document_access. Clients with conflict-check status lives in client_entities; keep the sensitive classes (privileged communications and case files, identity and financial documents, opposing-party information) out of this schema.
2. **Workflow step 1**: Model client entities and engagement periods; every document belongs to one engagement.
3. **Workflow step 2**: Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
4. **Workflow step 3**: Store documents in the private bucket and stream them through the app.
5. **Workflow step 4**: Deploy and verify the negative authorization tests and an authorized download.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. **Verify**: Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the law firms workflow.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server (size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0)
  - Managed PostgreSQL database (size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0)

## Limitations
- The technical basis (private document library on Laravel) was verified with the pattern fixture; the law firms schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Matter documents are privileged; the portal models per-matter authorization only. Professional-conduct and confidentiality obligations are not established here.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

## Evidence Summary
- **Kind**: Canary Run
- **Summary**: Laravel pattern fixture deployed on Ample. The blueprint's Law firms schema and workflow below build on that verified basis and were not separately executed.
- **Observed At**: 2026-09-20T20:36:21Z

## Formats
- [HTML Format](/content/blueprints/law-firms/client-portal/laravel/index.html)
- [Markdown Format](/content/blueprints/law-firms/client-portal/laravel.md)
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Alaw-firms%3Aclient-portal%3Alaravel)

## Next Actions
- **Action**: Browse the catalog index
- **Operation**: Catalog Index
- **Method**: GET
- **Relative Path**: /v1/catalog

- **Action**: Search published recipes 
- **Operation**: Search Recipes
- **Method**: POST
- **Relative Path**: /v1/catalog/search
