Every firm connects Egnyte with its own OAuth application, registered in the Egnyte developer portal. This guide covers registering the app, collecting the credentials, and entering them in Caddi.

You'll need:

Egnyte moved its developer portal to a new platform, so an older Egnyte developer login may not carry over automatically.

Keys issued on Egnyte's older developer portal still work — you don't need to reissue them, just sign in with the matching address.

Some Egnyte domains also expose a Create API Key tile under Admin console → Apps & Integrations, which issues the same pair of credentials and usually skips the approval queue. Either route produces values that work here.

Enter the following values:

Click Save Configuration. Caddi validates the credentials immediately — if something is wrong you'll see an error right away, and nothing is stored until validation passes.

Egnyte has no registered application matching the client ID for that domain. This is the expected error if you try to connect before completing Steps 1–3 — Caddi cannot connect to Egnyte until your firm has registered its own application and supplied the credentials. If you have already registered one, check that the Client ID in Caddi belongs to an app registered against the same Egnyte domain you entered, and that the app shows as approved rather than pending. The address bar will read https://<your-domain>.egnyte.com/puboauth/token, which tells you which domain Egnyte checked the key against.

Three usual causes, in order of likelihood: the app was registered as an Internal Application rather than a Public Application and therefore has no redirect URI; the URI doesn't match https://app.trycaddi.com/oauth-callback exactly; or it was entered with http instead of https.

Your Egnyte plan is not eligible — Trial, Platform Team, and Legacy Connect domains cannot create API keys — or the domain already has five. Delete an unused key, or contact Egnyte.

Egnyte hasn't approved the application yet. Wait for the approval email, then save the configuration again.

You're hitting the 2-per-second or 1,000-per-day ceiling. Reduce how often loops run, narrow the folders they scan, or ask Egnyte to raise the limit.

The Egnyte user who connected doesn't have permission on those folders. Check their folder permissions in Egnyte — Caddi cannot see more than they can.

Egnyte migrated its developer portal. Create an account on the new portal using the same email address as the old one and your existing keys will carry across.

Still stuck? Contact Caddi support with the exact error message you're seeing and the time it occurred.

Caddi provisions the standard Egnyte folder tree for a new matter, applies the right permissions, and records the folder link on the matter in your practice management system.

Caddi reads an emailed document, works out which matter it belongs to, files it to the correct Egnyte folder under your naming convention, and logs the activity.

When a matter closes, Caddi moves the folder to your archive location, applies the retention policy, and updates the matter record.

Caddi generates the Egnyte share link for the documents a client or co-counsel has asked for, with the expiry your policy requires, and logs what was sent.

Caddi creates the client's Egnyte folder set, generates a secure upload link for the documents you need, and tracks what's still outstanding.

Caddi files generated statements into each client's folder and creates the share links for delivery, with nothing landing in the wrong place.

Caddi pulls the documents an examiner has asked for into a single reviewed pack, with a log of exactly what was included.