Parker works from the cases, contacts, and documents you already keep in MerusCase — so the first thing a firm does is register Parker as an app through MerusCase's own 3rd Party Apps page. You'll create the app, let MerusCase generate its credentials, and hand two of them off securely. Nothing about your MerusCase data changes; Parker simply gains a way to connect.
Before you begin. You'll need admin access to your firm's MerusCase account to reach 3rd Party Apps. Open MerusCase in another tab and follow along — by the end you'll have two credentials to hand to the Parker team, plus a link for whoever will authorize the connection.
The eight steps
- 01 Open Tools & SettingsIn the top-right corner of MerusCase, click the gear icon to open Tools & Settings.
- 02 Select "3rd Party Apps"Near the bottom of the settings panel, click 3rd Party Apps. This opens a page with two tabs: My Apps, which lists apps available to connect, and App Publisher, where you'll register Parker.
- 03 Click the "App Publisher" tabSwitch to the App Publisher tab, then click + New App to begin a new registration.
- 04 Name the application "Parker AI"In the App Name field, enter Parker AI. You can enter the same value in Brand, and leave Description, Demo URI, and Logo URI blank — none of those are required.
-
05
Set the Redirect URIIn the Redirect URI field, enter
https://api.meruscase.com/oauth/authcodeCallback. This is a special value MerusCase recognizes — it tells MerusCase to manage the OAuth exchange on your behalf, so there's no callback server for your firm to stand up. - 06 Click "Save"With the name and redirect URI in place, click Save at the top of the form. MerusCase creates the app and assigns it an App ID.
- 07 Click "Show Secret Key & Auth Request URL"Reopen the app from the App Publisher list and click this button. MerusCase reveals the app's secret key and generates a unique authorization link for your firm.
- 08 Copy your credentials and share the authorization linkCopy the App ID and Secret Key, then submit them securely to the Parker team — that's how you hand off the connection. Separately, send the Auth Request URL to whichever team member should grant Parker access to the firm's cases.
A closer look at authorizing access
Step 8 has two parts, and it's worth keeping them straight. The App ID and Secret Key identify the application — they're what the Parker team uses to talk to MerusCase's API at all. The Auth Request URL is different: it's what lets a specific person at your firm grant that application access to your firm's data.
MerusCase doesn't offer the same category-by-category permission table you'd see in some other case management tools. Instead, access is scoped to whatever the person who clicks "Allow this App to Access My Firm" can already see. That makes the choice of who authorizes the app the main lever your firm has:
Who should open the Auth Request URL
- A firm administrator, or someone with access matching what Parker should see — since Parker inherits that person's visibility into cases, contacts, and documents.
- Someone expecting the confirmation screen — opening the link prompts a MerusCase login, then a screen asking them to confirm Allow this App to Access My Firm. Clicking through generates the token.
Keeping the credentials safe
- Never share the Secret Key outside the handoff to Parker. Treat it like a password — it authenticates the app itself.
- Revoking access — the person who authorized Parker, or a firm administrator, can revoke the connection at any time from App Publisher by opening App Users on the Parker AI row.
- If a Secret Key is ever compromised, use Reset Secret Key on the app's configuration screen to invalidate it and issue a new one — just remember to share the new key with the Parker team.
Why MerusCase handles the token exchange. Using https://api.meruscase.com/oauth/authcodeCallback as the redirect URI means MerusCase stores the resulting bearer token for you rather than returning it to a server your firm would otherwise need to run. It's the convenience path MerusCase documents for firms connecting a single outside app — which is exactly this setup.
What happens next
Once you've handed off the App ID and Secret Key, and someone at your firm has opened the Auth Request URL and confirmed access, the Parker team completes the connection on our side. From there, Parker works from your cases inside the tools your firm already uses — Slack, email, Gmail, and more — across whatever practice areas you handle. There's no platform to migrate onto and nothing new for your team to learn.
And because every firm runs in an isolated environment with Zero Data Retention, your clients' information is never stored by the model provider or used to train any model. Attorney–client confidentiality was a design constraint from day one.