Frequently asked questions
Two ways to browse — start with platform-wide questions (billing, security, Claude subscription, getting started), then dive into the connector you care about. Same answers, organised the way our customers actually ask.
ProLaw FAQ
ProLaw — Big Law practice management, reached read-only through the on-prem Windows agent (no VPN). Everything below is ProLaw-specific; for platform-wide questions, see the Platform tab.
ProLaw Q&A
6 questionsHow does Claude reach ProLaw if it's on our own server?
Through a small Windows agent your IT installs on a machine that can reach the ProLaw SQL Server. It dials OUT over HTTPS (443) and waits for work — no inbound ports, no VPN. Claude asks; the agent runs a read-only query locally and returns just the answer.
Is it read-only? Can Claude change anything in ProLaw?
Read-only, full stop. All 7 tools are parameterised SELECTs; there is no write path in the agent. Claude cannot alter a matter, a time entry, or any record.
If it's one connector, how does each attorney see only their own matters?
Row-level scoping is enforced inside the agent from each user's ProLaw initials. Non-managers are force-scoped to their own matters/time; managers get firm-wide visibility. The filter is on the SQL, not the prompt.
What credentials does the agent use, and where do they live?
A scoped read-only SQL login (or Windows service account) your IT controls, stored on the agent machine. Cohesive360 never sees or stores your ProLaw credentials; we hold only the agent's bearer token (hashed).
How do we get it set up?
By request, not self-serve. We generate an agent token; your IT installs the Windows agent (unzip → setup → run as a service); we do a short read-only check with your DBA before go-live.
Which ProLaw versions are supported?
It reads the ProLaw SQL database directly, so it works across versions with the standard schema (Matters, Transactions, Clients, Professionals). We validate queries against your DB during onboarding.