File-request that clients finish
Send a branded request instead of asking them to guess a folder structure on a consumer drive.
For legal teams
Collect and send matter files under your firm brand. Expiry, revoke, watermark, and an access trail partners and insurers can understand.
Clients and counsel get a portal that looks like your firm. They upload to a file-request or download a share with a real identity. Your object storage holds the matter files. Audit answers who opened what.
File-request · Watermark · Expiry and revoke · Firm hostname
Discovery subsets, signed engagements, KYC packs, and expert reports move between firms, clients, and counsel every day. Outlook size limits push people to consumer links. Those links outlive the matter. Forwarding erases who was authorised.
Legal secure file exchange is the job: a branded place to request files from a client, send a pack to opposing counsel, expire it when the hearing ends, and show an insurer or privacy officer the access history.
Bridge is built for that motion: share, file-request, and a workspace when counsel need a standing room. Guest MFA, max downloads, revoke, and view-only watermark.

Put the portal on a hostname clients already trust. Connect Azure Blob, GCS, or S3 in a subscription your IT or MSP already governs. Federate Entra so lawyers use the same work identity. Invite external counsel as guests with Microsoft or Google work login, a one-time email code to the invited mailbox, or passkey / TOTP when you require MFA.
Per-matter hygiene: set expiry when you create the share. Revoke when a secondment ends. Use view-only plus watermark for drafts you want attributed. Keep the matter file in iManage, NetDocuments, or SharePoint if that is already the system of record. Bridge is the governed handoff at the edge.
Local DLP can block obvious extension and regex mistakes on the way in.
Where do files live? In your cloud storage, not in Trustholm Postgres. Where do identities live? In your IdP, plus platform MFA for guests. Can we export who accessed a matter pack? Yes, hash-chained audit to CSV or SIEM.
Keep the matter file in iManage, NetDocuments, or SharePoint if that is already the system of record. Bridge is the governed handoff at the edge.
The same path fits accounting firms, corporate development advisors, and consultancies that collect client evidence under their own brand. The keyword on this page is legal because that is the search intent. The product motion is identical: branded request, branded send, expiry, audit.
Regulated healthcare or payment programmes should read the enterprise path and confirm retention, SIEM, and local DLP during onboarding.
Fewer forever links. Clearer authority. A portal that still looks like the firm.
Send a branded request instead of asking them to guess a folder structure on a consumer drive.
Max downloads, revoke, and erase from your bucket after expiry. Legal hold on the share skips that erase.
Watermarked view is a deterrent and an attribution aid. Partners see the draft under your brand.
Request Bridge access for one file-request motion. We will scope firm brand, storage, guest MFA, and what the access trail must show.
Yes. File-request plus guest access is the motion. They can upload a folder or a file. They return a signed PDF without joining your Entra tenant.
In the object storage you connect. Email is notification. Bridge is the transfer system.
It is a deterrent and an attribution aid. Treat it that way in policies and engagement letters.
Retention days are tenant-configurable. Legal hold can skip audit purge. Confirm the numbers during onboarding.
Keep the matter file in your DMS. Use Bridge for the external handoff you currently run through email and consumer links.
Request Bridge access with legal or professional services in the notes. Scope one matter type, brand, storage, and IdP first.