01 · Who can sign in
Identity and SSO
Lawyers sign in with the firm account. The access gateway checks role and matter-team membership before a workspace opens.
Developers
Connect the firm’s systems without opening the workspace.
FederatedOne keeps the AI workspace on dedicated infrastructure. A technical team connects identity, documents and the firm’s existing controls. Client documents do not leave the site, and they are not shared across clients.
For a technical team
The application is shared. The client’s files are not.
LegalApp services and the on-premises model can be shared. They hold no client documents between requests. Each client has its own container: document store, search index, encryption key, access list and audit log.
A developer’s work is to meet the systems the firm already runs, then leave the boundary where it is. No search, answer or export crosses from one client container into another.
What gets connected
Three places a firm system meets the workspace.
02 · Where files come from
Email and documents
Documents arrive by upload or email. Scans are converted to text, then classified and tagged inside that client’s container.
03 · What stays recorded
Conflicts and the audit log
The conflicts register can be connected. Every view, query and export is logged, and security events can be sent to the firm’s SIEM over encrypted transport.
How people reach it
Office VPN, remote access, and a closed path for support.
Connectivity
Private paths in. Nothing public by default.
01
Office networkA site-to-site IPsec VPN between the firm and the dedicated environment. Application traffic stays on HTTPS over that VPN.
02
Remote professionalsA client VPN with multi-factor authentication for people working away from the office.
03
Support accessOpened only on request and approval, from a management zone, with the session logged.
04
Outbound trafficBlocked by default. The exception is approved legal research. There is no direct path from the public internet into a client container.
Still to confirm with the firm
The connection is part of the scope, not a public kit.
Identity provider, mail and document system, conflicts register, backup, legal hold and retention exceptions are agreed with the firm. The same applies to access between matter teams that share one client container.
This page describes how those connections are intended to work. It is not a published API, SDK or sandbox. A working integration is scoped with the deployment.
See LegalAppA good place to begin