How Ajax Works With Elite 3E
3E support is in early access. Released entries go into Elite 3E as pending time cards through 3E's API, over a connection your own firm sets up with us.
For 3E Cloud, the setup happens in your own Entra tenant
3E's API is enabled by the customer, in the customer's own Microsoft Entra tenant. Your admin registers the connection, gives it access to the 3E API, and sends us the credentials. It's the same app registration your firm does for any connected application, and we do it together on a call.
It's your tenant, so your IT can restrict the connection or kill it like any other app. For on-prem 3E, the connection uses a service account on your side instead of the Entra setup.
What shows up in 3E
Released entries arrive as pending time cards and go through the same review-and-post step your billing team already runs for any other time. Ajax also reads your client, matter, and timekeeper data on a schedule, so as files open and close the predictions keep up.
Where the entries come from
Ajax runs on each lawyer's machine and watches what they're working on, email, documents, research, calls. It drafts a time entry with the narrative and the client and matter filled in, and the draft sits in that lawyer's private queue until they review it and release it. It learns from each person's edits, so the narratives come out sounding like that lawyer, and once it has the firm's matter list learned, about 92% of drafts land on the right client and matter.
Hundreds of law firms run this on Clio, MyCase, and the rest of our direct integrations. For a 3E firm, the entries go to 3E instead.
FAQ
Is the 3E integration live today?
It's in early access. We set up the 3E connection with your admins ourselves when your firm comes on.
Do entries post into 3E automatically?
No. They arrive as pending time cards and your billing team posts them the same way they post anything else.
What does our Azure admin have to do?
An app registration in your Entra tenant with access to the 3E API, then send us the credentials. We walk through it together.
What about security?
Drafts are private to each timekeeper until they release them, raw captured data is deleted automatically on a rolling basis, customer data is encrypted with TLS in transit and AES-256 at rest, and Ajax is SOC 2 Type II certified and HIPAA compliant. Sign-in supports SAML single sign-on and SCIM provisioning through your identity provider. The questions legal IT teams ask us most are written up here.
You can book a demo here. Ask for the 3E walkthrough.
