The controls, and how they work.
A law firm holds its clients' most sensitive information and their money. This page describes the controls FirmsVault enforces today, in plain terms, so your team can judge them for itself.
Each firm's records, kept apart in the database itself.
Separation between firms is enforced by the database, not only by the application: firm-owned tables carry row-level security rules, so a query that is not running on behalf of a firm cannot read that firm's rows. Every product — matters, documents, billing, trust, AI search — works inside that boundary.
- Row-level security on firm-owned tables
- AI search limited to the asking user's own firm and permissions
- Client Portal users see only the matters they were invited to
- For a separate environment altogether, see dedicated deployment
Who can sign in, and what they can do.
- Two-step sign-in with an authenticator app or a passkey, plus recovery codes
- Firms can require two-step sign-in for staff, and separately for clients
- Stronger verification before sensitive actions
- Repeated failed sign-ins to an account are slowed and recorded
- Signed-in sessions can be signed out
- Firm roles — owner, attorney, paralegal, legal assistant, reception, billing — checked on every action
Approvals where the stakes are real
Trust money
The person who requests a trust transfer, refund or disbursement cannot approve it. High-risk adjustments need two different approvers.
AI actions
AI-proposed actions wait in an approvals queue. Nothing is sent, filed or changed until someone authorised approves it.
Support access
FirmsVault support cannot open a firm's workspace unless the firm approves the request, and access ends when its approved time runs out.
Sign-ins, failed attempts and two-step sign-in changes are recorded automatically, with time and source.
Trust ledger entries are corrected by reversal rather than edited; approvals record who decided and when.
Uploaded files are held in quarantine until a malware scan passes, and only then can anyone open them. A file whose scan cannot complete stays quarantined.
Connections to FirmsVault are encrypted in transit. Dedicated environments get their own encryption keys and secrets.
What we say, and what we don't.
No system can promise it will never have a security incident, and we don't. We describe controls we can show you, and we do not list certifications or attestations on this site that we cannot evidence.
For your security review
We will walk your team through the architecture and controls and answer your questionnaire from what the product does today. Single sign-on (SAML or OIDC), SCIM and customer-supplied encryption keys are not available today — please raise them early if you need them.
Start a security conversationBring your security team to the conversation.
We will cover the controls, the deployment options and your questionnaire with the people who built them.