Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
ProLaw in Claude — without opening your firewall
ProLaw runs inside your firm's network, so Cohesive360 reaches it through a small outbound-only Windows agent — no VPN, no inbound ports. Claude gets 7 read-only tools across matters, time & WIP, and the client/professional directory. Every read is a parameterised SELECT under a scoped read-only login, per-attorney row scoping is enforced inside the agent, and your ProLaw data never leaves your network.
Inside your firewall, no VPN
ProLaw's SQL database never leaves your network. A small Windows agent runs on a machine that can reach ProLaw and dials OUT to Cohesive360 over HTTPS — no inbound ports, no VPN, no firewall changes. Claude asks; the agent reads locally and returns just the answer.
Read-only by design
Seven read-only tools — matters, time, WIP, clients, professionals. Nothing here writes, edits, or deletes a ProLaw record. The agent runs parameterised SELECTs as a scoped read-only SQL login your IT controls.
Per-attorney scoping
Each attorney sees only their own matters and time entries; managing partners get firm-wide visibility. Row-level scoping is enforced inside the agent from the calling user's timekeeper initials — not something the model can talk its way around.
Capabilities
3 workflow areas. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Matters
Read · 2 toolsSearch the matter directory by matter id or client name, and pull a single matter's header — client, billing attorney, responsible attorney, open/closed dates, description.
Matters
Read · 2 toolsSearch the matter directory by matter id or client name, and pull a single matter's header — client, billing attorney, responsible attorney, open/closed dates, description.
What you can ask Claude
- “Find my open matters for client Smith”
- “Pull the header on matter 24-PI-0142 — who's the billing attorney and when did it open”
- “Which of my matters opened this quarter”
Underlying tools (2)
search_mattersget_matterTime & unbilled WIP
Read · 3 toolsReview time entries (your own, or firm-wide for managers) over any date range, and aggregate unbilled work-in-process by matter — the 'what's stuck in WIP' partner report.
Time & unbilled WIP
Read · 3 toolsReview time entries (your own, or firm-wide for managers) over any date range, and aggregate unbilled work-in-process by matter — the 'what's stuck in WIP' partner report.
What you can ask Claude
- “Show my time entries for last week”
- “What's my unbilled WIP by matter right now”
- “As a manager: pull all attorneys' time on the Doe matter this month”
Underlying tools (3)
list_my_time_entriessearch_time_entriesunbilled_wipClients & professionals
Read · 2 toolsList clients (scoped to the caller's matters unless they're a manager) and look up firm professionals — handy for resolving a timekeeper's initials to a name.
Clients & professionals
Read · 2 toolsList clients (scoped to the caller's matters unless they're a manager) and look up firm professionals — handy for resolving a timekeeper's initials to a name.
What you can ask Claude
- “List my clients whose name contains 'Holdings'”
- “Who is timekeeper MAS — give me the full name”
- “Show the firm's professionals”
Underlying tools (2)
list_clientslist_professionalsLimits and roadmap
What the ProLawconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Writes (create/update matters, time entries). v1 is read-only by design. Posting time or editing a matter would be a separate, explicitly-scoped release with draft-for-review safeguards — not a silent agent-side write.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Documents stored on a file server. ProLaw document files that live on a Windows share are covered by the separate File Server connector — the same on-prem agent pattern, pointed at your document folders.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Outbound-only agent — no inbound access
The agent opens no ports and accepts no inbound connections. It dials out to Cohesive360 over HTTPS (443) on a long-poll. There is nothing for an attacker on the internet to connect to; your ProLaw server is never exposed.
Read-only SQL login
The agent authenticates to ProLaw as a scoped read-only SQL login (or a Windows service account) your IT provisions. Every query is a parameterised SELECT — no write path exists in the agent, so Claude cannot alter a matter, a time entry, or anything else.
Per-attorney row scoping, enforced server-side
Non-managers are force-scoped to their own matters and time entries by their timekeeper initials, inside the agent. A manager flag grants firm-wide visibility. The model can't override the filter — it's applied to the SQL, not requested by the prompt.
We store no ProLaw data
Cohesive360 transports the request and streams the result back to Claude; we don't persist matter data, time entries, or query results. Audit logs record the tool name and timestamp only — never the payload.
What ProLaw via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your ProLawtenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.