Law Office Reference Public

Getting Started

Enable the Law Office module, run the module migrations, grant the 25 permissions by role, review the Philippine practice-area catalog, and load or remove the demo dataset.

Guide version: r1 Module version: 1.0.0 Updated: 2026-08-20 Estimated time: 3 min 9 views 0% helpful
Introduction

Getting Started

An administrator's first-run checklist: enable the module, build its tables, grant access by role, check the reference catalog, and (optionally) load the demo dataset to explore.

1 · Enable the module

  1. The module_law_office setting ships enabled by the core seed migration. Confirm it under Settings → Manage Modules → Law Office (category Operations).
  2. Run the module migrations so the 21 law_* tables exist on every database:
    php erpat migrate:modules
    On a multi-tenant install this applies the per-module migrations_law_office set to the main database and every active tenant.
  3. Reload the dashboard — a Law Office group appears in the left menu with Command Center, Intakes, Matters, Parties, Docket, Reports and Settings.

2 · Grant permissions (Roles editor)

The module declares 25 permission keys, grouped under “Law Office: …” categories. A practical starting split:

RoleGrant
Managing partnerEverything, including law_office_intakes_decide, law_office_conflicts_decide, law_office_deadlines_verify, law_office_restricted_view, law_office_reports.
Handling lawyerlaw_office, parties/matters + CRUD, law_office_docket + law_office_docket_manage, law_office_deadlines_verify, tasks + documents manage.
Paralegal / stafflaw_office, parties + create/update, intakes + create/update, law_office_conflicts (run searches), docket manage, tasks + documents manage. No verify, decide, or restricted-view.
Firm administratorlaw_office + law_office_settings (+ reports if desired).
????
Three keys are deliberately scarce. law_office_deadlines_verify (a deadline becomes firm-trusted), law_office_conflicts_decide (a conflict is dispositioned), and law_office_restricted_view (sees restricted matters firm-wide). Grant them to named lawyers only.

3 · Review the reference catalog

The migrations seed a Philippine starter catalog: 10 practice areas (Litigation, Corporate & Commercial, Labor, Family, Criminal, Taxation, IP, Property, Immigration, Special Projects) and 22 matter types (Civil Case, Special Proceeding, Appeal, NLRC Labor Case, Annulment, Ejectment, Tax/CTA Case, Notarial Services, …). Litigation-type matters automatically expose court/branch/docket fields. Curate the lists under Law Office → Settings.

4 · Check the module settings

SettingDefaultMeaning
Matter reference formatMAT-{YYYY}-{####}Pattern for auto-issued matter references.
Intake reference formatINT-{YYYY}-{####}Pattern for intake references.
Deadline reminder ladder10,5,3,1,0Days-before-due offsets on which the daily sweep reminds the assignee (0 = due day; overdue is flagged separately).

5 · Load the demo dataset (optional, reversible)

php erpat db:seed LawOfficeDemo            # load (idempotent — safe to re-run)
php erpat db:seed LawOfficeDemo --dry-run  # preview
php erpat db:seed LawOfficeDemo --remove   # soft-delete every demo row

The demo seeds 8 parties (with aliases), 6 matters (one restricted), a hearing, a verified and a draft deadline, a task, a metadata-only document, and two intakes — one carrying a recorded conflict search whose hit was cleared with a waiver. It is also available from the Bulk Database Seeder modal.

6 · First real walk-through

  1. Register a party (Parties → Add) — the module derives the normalized conflict-search key and phonetic code automatically.
  2. Open an intake (Intakes → Add) and add the prospective client and known adverse parties to its party list.
  3. Run the conflict search from the intake's Conflict Check tab, review the hits, and record a disposition with a written rationale.
  4. Accept the intake — a matter opens, matched parties carry over, and the intake links to it permanently.
  5. Docket a hearing and draft a deadline, then have a permitted lawyer verify the deadline citing its source document.

The full daily procedures live in Operations.

Was this guide helpful?

Report a content problem