Staff on Case for Every CMS and Filevine Medical Providers Import

Portal 2026.4.5 makes Staff on Case work the same way no matter which case management system your firm runs on, brings Filevine medical providers into Quilia automatically, and rounds out the public v2 API for integration partners.

Staff on Case for Every CMS portal

Staff on Case auto-assigns the right attorney and paralegal as a case is imported from your CMS, based on per-firm rules you configure once. The feature now covers every supported CMS adapter — six in this release — instead of being Filevine-only.

• Now supported: Filevine, MyCase, Neos, CasePeer, SmartAdvocate, and Clio
• Where to configure: Settings → Integrations → Staff on Case
• What it does: Maps the staff fields from your CMS to Quilia roles so newly imported cases land with the correct team already attached — no manual member adds, no missed assignments

Filevine Medical Providers Import portal

For Filevine firms, Quilia now imports the Meds collection from each case directly into the providers list and auto-links matches against your existing providers_list. Imports happen automatically every time a Filevine case is brought in or synced, with a manual sync button for on-demand pulls.

• Manual sync button: Lives on the case Treatment → Providers tab; runs the import inline and reports imported, matched, and queued counts in a toast
• Per-case-type configuration: Admins map the Filevine Meds section, the PersonLink field that holds the provider contact, and an optional Dropdown field (e.g. "Type of Treatment") to use as specialty under Settings → Case Types → Integration → Filevine Medical Providers Import
• Idempotent re-syncs: Imported people are keyed by their Filevine contact ID so repeat syncs upsert in place — no duplicate provider rows

Filevine Activity Feed Clarity portal

Every note Quilia posts to a Filevine case now wraps with a Quilia Activity Feed heading and footer. Quilia-origin posts are now visually distinct in the Filevine activity feed, so attorneys can tell at a glance which entries came from Quilia versus the rest of the case timeline.

Notifications

• No next appointment nudge: PI clients who have had medical appointments but no upcoming one scheduled now receive a daily push notification reminding them to book. Delivered at 10:00 local time, capped at once per 7 days per client, so it stays useful and doesn't become noise.
• Product updates opt-out: Settings → Notifications now has a "From Quilia" section with a Product Updates toggle. Users who only want case-related communications can opt out of product update emails directly from the app.

Faster Dashboard

The shared client bundle that ships on 68 of 90 portal routes is roughly 220 KB lighter (compressed). CMS brand icons in the sidebar now lazy-load on demand instead of bundling all 18 brands up-front, and the unused Reports section was removed from the dashboard. Cold starts and first-session loads will feel snappier.

v2 Public API Expansion

For integration partners building against api.quilia.dev/v2, this release lands the last set of endpoints needed to retire the legacy /api/v1/* surface:

• GET and POST /v2/cases/{id}/members — manage staff and clients on a case
• GET and PUT /v2/cases/{id}/incident — read or upsert the case incident details (partial fields don't clobber unset values)
• GET and PUT /v2/cases/{id}/damage — read or upsert property damage; the schema is generic and forward-compatible beyond cars
• POST /v2/cases/{id}/providers — add a provider to a case with shared cross-org provider matching and auto-link
• POST /v2/staff is now fully idempotent with an invite: 'send' | 'skip' | 'auto' mode, safe for sync integrations to call repeatedly

The legacy portal.quilia.com/api/v1/* endpoints will sunset on Thursday, 16 July 2026 and now advertise Deprecation: true and Sunset headers in every response, with a Link header pointing at the v2 successor. External consumers should migrate before the sunset date.

Bug Fixes and Stability

• Phase messages: Drag-and-drop reorder on the Phase Messages sidebar now persists across reloads. Previously the order would silently revert to alphabetical on the next page load. Failed reorders now surface a toast and revert the visible order instead of failing silently.