Parker works from the matters, contacts, and records you already keep in Clio — so the first thing a firm does is grant it read-only access through Clio's developer portal. You'll register an application, set its permissions, and generate four credentials to hand off securely. Nothing about your Clio data changes; Parker simply gains the ability to read what it needs.
Before you begin. You'll need admin access to your firm's Clio account to register a developer application. Open Clio in another tab and follow along — by the end you'll have four credentials to hand to the Parker team, and your firm will be ready to connect.
The ten steps
- 01 Navigate to the Clio Developer PortalGo to developers.clio.com and sign in with your Clio account. You'll land on the Developer Apps screen, which lists any applications already registered.
- 02 Click "New App"In the top-right corner of the Developer Apps screen, click the blue New App button to begin a new registration.
- 03 Name the application "Parker AI"In the Name field (required), enter Parker AI. This is simply a label for your own records — the Description can be left blank.
- 04 Set the Website URLScroll down to Website URL (required) and enter https://hireparker.ai. The Support URL and icon fields are optional — leave them empty.
-
05
Add the two Redirect URIsIn the Redirect URIs field (required), add the following two entries, one per line:
http://127.0.0.1http://127.0.0.1/callback - 06 Accept the Developer Terms of ServiceUnder Agreements, tick the box to accept the Developer Terms of Service. This is required before the app can be saved.
- 07 Set permissions to Read — but only where Parker needs itIn the Permissions table, check the Read box for the case and work-product data Parker drafts from, and leave the sensitive financial and administrative scopes unchecked entirely. Leave every Write box unchecked. See the breakdown below.
- 08 Click "Save"With Read checked across the permissions Parker needs and the terms accepted, click Save at the bottom of the form to create the application.
- 09 Click "Generate"On the saved app screen, click Generate next to the Secondary Secret to produce your full set of credentials.
- 10 Copy your four credentialsCopy the App ID, Client ID, Client Secret, and Secondary Secret, then submit them securely to the Parker team — that's how you hand off the connection.
A closer look at permissions
Step 7 is the one worth slowing down on. Clio's permission model is granular — you grant Read or Write on each category of data independently. Parker never needs Write on anything; it produces drafts for your review, it doesn't change records in Clio. And it doesn't need Read on everything either.
The principle is simple: grant access to what Parker drafts from, and lock down everything that would be costly to expose if a credential were ever compromised. Your firm's trust ledgers, billing, and bank data have nothing to do with writing a demand letter or a discovery response — so they stay out of scope entirely.
Grant Read access
These are the categories Parker reads to do its work — case facts, parties, records, and the timeline of a matter:
- Matters — the cases themselves, the spine of every workflow.
- Contacts — clients, opposing parties, providers, and witnesses.
- Documents — medical records, repair orders, pleadings, and exhibits for review.
- Notes — case notes that carry context Parker should reflect.
- Communications — correspondence and logs that feed chronologies.
- Calendars & Tasks — deadlines, hearings, and case events.
- Custom Fields — intake data plaintiff firms store on the matter.
- Practice Areas — so Parker frames work to the right area of law.
Leave unchecked
These are high-value-if-breached and play no part in drafting work — so Parker gets no access at all:
- Billing & accounting — bills, bill themes, and activity rates.
- Trust & bank accounts — trust accounting and bank balances, the most sensitive client-funds data in the system.
- Payments — client payment records and payment profiles.
- Users & firm administration — internal account and permission settings.
Why restrict at all? Read-only already protects your records from being changed. Skipping the financial and admin scopes goes a step further — it shrinks the blast radius. Even in the unlikely event a credential leaked, there would simply be no path to your firm's trust ledger or bank data, because that access was never granted.
What happens next
Once you've handed off the four credentials, the Parker team completes the connection on our side. From there, Parker works from your matters inside the tools your firm already uses — Slack, Telegram, Outlook, 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.