Apps and integrations: how it works

Availability

Before you start

• Start with the available web app and a compatible outside-AI connection. Credentials, named-matter scope, expiry, underlying access and the client tool’s compatibility remain prerequisites; there is no assumption that every outside model can connect.
• Before sharing client material, your firm must review the outside AI tool’s privacy, retention and training terms. A BRON credential controls access to the record; it does not govern how an outside model handles what it receives.
• BRON for Mac is the collection surface for accepted device scopes, on macOS 15 or later. It is not a cloud-account collector; Office and iPhone/iPad surfaces retain their stated development availability.
• A matter grant, permitted abilities and expiry define the tool’s access. The web app remains the available place for drafting and citation review while the Word and Outlook add-ins are in development.
• Web app: a BRON account at your firm. BRON runs in the browser.
• BRON for Mac: for the person answering a firm's request. It needs macOS 15 or later. See Evidence collection: Collector.
• Your own AI tools: an API key or a standard sign-in (OAuth 2.1), issued for named matters. Each is marked client-safe or attorney-class and lists what the tool may do.
• Signature invitations and other outbound email: switched on for your firm during onboarding.
• Imports: an export file from Clio or Filevine, and a licensed attorney at the firm to commit it.
• The iPhone and iPad app, the Word add-in and the Outlook add-in: in development. There is nothing to install.

How it works

Let a compatible AI tool read source-linked testimony, search authorized matter records and propose follow-up work. Your firm chooses its access and reviews what happens next. Draft and review in the web app; collect accepted device sources with BRON for Mac. Word, Outlook and the iPhone and iPad app remain in development and cannot be installed.

Can my firm’s AI compare the notice accounts and prepare the next evidence request for review?

What it reads from

• The matter's documents, facts and deadlines
• The keys and grants the firm has issued
• The firm's approval rules
• Privilege classification and review

Who can do what

• Counsel can let an outside AI inspect both notice accounts and propose the next evidence request. Source citations and review qualifications return with the reading; the proposal uses the common approval process.
• A firm administrator issues an attorney-class key, which can read work product. A client-safe key cannot reach work-product tools.
• The matters on a key can only narrow what the granting attorney can reach.
• An outside tool can read, add notes, upload documents and propose actions. It cannot send, file, sign, serve, calendar or move money, and it cannot approve its own proposal.
• A proposal from a tool is approved by someone at the firm with authority for that act, through the same single-use approval as any other act.
• A licensed attorney commits a Clio or Filevine import before the matters are created.

What it produces

• The firm's approval queue
• Notes on the matter
• Uploaded documents, waiting for privilege review
• Calendar files (.ics) and signature requests

Limits

• The Word and Outlook add-ins and the iPhone and iPad app are in development and cannot be installed.
• BRON for Mac is for the person answering a firm's request. It runs on macOS 15 or later.
• Calendars get an .ics export. Sync with Google or Outlook calendars is not connected.
• Outbound email, including signature invitations, is switched on for each firm during onboarding.
• An answer your tool receives shows which document and page a statement came from. It does not check that the statement is true.
• BRON controls what a key can read and stops a proposal from running on its own. It cannot control what your AI tool writes about what it read.
• Your firm must review the outside AI tool’s privacy, retention and training terms before giving it client material. BRON’s access controls do not set those terms.

What BRON will not do

• Let an outside tool approve its own proposal.

  A proposal is a request to a person. The approval exists only once someone at the firm gives it, and it covers that one action, on that matter, with the exact details they saw. A tool never holds an approval it could replay.

• Let a tool choose how much privileged material it reaches.

  The privilege level belongs to the key, set when the attorney grants it. A tool asking for more in its request changes nothing, and a document it uploads stays unreadable to it until privilege is reviewed.

• Answer an unreadable source with an empty list.

  A matter with no undisputed facts and a list of facts that would not load are opposite statements, and the empty one looks safer. Your tool is told which one it got.

• Average how well an answer is supported.

  One unsupported statement among many supported ones makes the answer unsupported, with the counts shown. An average would let many sound facts cover for one invented one.

When something goes wrong

• The source-and-status envelope describes what the tool received. It neither controls the outside model’s prose nor establishes that its answer or legal analysis is correct.
• An outside model may misread a source. Access to a matter and permission to propose do not allow the tool to serve, sign, file, calendar or move money.
• If part of the matter cannot be read, your tool is told the read failed. It does not receive an empty list and a zero.
• An empty result is never offered as proof that something does not exist.
• If an answer cannot say how far it was checked, it says so. An answer is only as supported as its weakest item.
• If a tool's proposal arrives with an override or an approval attached, BRON removes it before recording the proposal.
• A document a tool uploads stays unclassified, and outside tools cannot read it until a licensed attorney reviews privilege.

See it in action

• Apps and integrations on the product page