Help & setup

Setup and help, by role

The administrator, the responsible attorney, paralegals and clients: for each, the setup checklist in order, what the role does, where it lives in the console, and what is locked today — with who unlocks it.

Create your firm workspace Firm sign in

The firm's administrator

Creates the workspace, pays, invites the team, sets the firm's identity and policies, and holds the keys. Administration confers no approval authority: an administrator who is also the responsible attorney holds that role separately.

Setup checklist

Create the firm workspace
Your firm's name and a work email; a sign-in link finishes it. Nothing is charged.
Add your second factor
An authenticator app, enrolled at first sign-in; the console and every staff page require it.
Set the firm's identity and support line
A display name, a logo or accent colour, and a support email or phone — the portal, every invitation and every reminder carry them.
Invite the team and set each role
Attorneys and paralegals, as many as you have; a member's access ends with one recorded control.
How it works — Invite the team and set each role
Ask the responsible attorney to confirm responsibility
Approvals and deliveries need an attorney-level role, the firm's current terms and that confirmation, given once in the console by the attorney — not by you.
How it works — Ask the responsible attorney to confirm responsibility
Choose how the firm pays
A membership by card in the console, or pay as you go on each matter; a cancelled plan runs to the end of the paid month.
How it works — Choose how the firm pays
Enter the conflict registers
Declined parties, prior affiliations and the joint-representation policy, before the first matter.
How it works — Enter the conflict registers
Set the records policy
How many years after a matter closes its records are kept, and the disclosure switch for new shares.
How it works — Set the records policy
Set what the platform enforces
The engines each surface may use, and a two-attorney release threshold for a large outflow.
How it works — Set what the platform enforces
Mint read keys and register webhooks (optional)
Each key scoped to exactly what it may see; each webhook signed with its own secret.
How it works — Mint read keys and register webhooks (optional)

What this role does

Subscribe by card from the firm console and cancel there; a cancelled plan runs to the end of the paid month. How it works — Subscribe by card from the firm console and cancel there; a cancelled plan runs to the end of the paid month.
Set what the platform enforces for the firm — the engines each surface may use, and a two-attorney release threshold for a large outflow — and see what no setting moves. How it works — Set what the platform enforces for the firm — the engines each surface may use, and a two-attorney release threshold for a large outflow — and see what no setting moves.
Choose how many years after a matter closes its records are kept (1 to 25, or none); nothing is deleted by itself, and every deletion leaves a receipt. How it works — Choose how many years after a matter closes its records are kept (1 to 25, or none); nothing is deleted by itself, and every deletion leaves a receipt.
Issue read keys scoped to exactly what each may see, and register signed webhooks. How it works — Issue read keys scoped to exactly what each may see, and register signed webhooks.

Where it lives

The console's own names and addresses, once signed in.

Firm settings /firms/manage: Team, roles, branding, the subscription, single sign-on, API keys.
Team & permissions /admin/team: The team hub.
Billing & integrations /admin/billing: The subscription, exports, keys and connections.
Firm control /admin/firm-control: What the platform enforces for the firm.

The responsible attorney

Decides. Confirms responsibility once, approves each consequential act from its receipt card, decides conflicts, reviews and signs off on client work. The platform is software: the professional judgment is the attorney's.

Setup checklist

Add your second factor
An authenticator app, enrolled at first sign-in.
Confirm attorney responsibility
Given once in the console; approvals and deliveries wait for it.
How it works — Confirm attorney responsibility
Approve the firm's clause text
Each variant in the playbook is approved by one of your attorneys, version by version, before the estate-plan lane uses it.
How it works — Approve the firm's clause text
Decide the conflict findings
An undecided blocking finding holds the engagement until it is cleared.
How it works — Decide the conflict findings
Run the engines on a draft
Review, Redline, Cite Check and the Opposing Counsel Pass™ from Ask & run — work product for your own judgment, with what each engine received kept on the record.
How it works — Run the engines on a draft
Approve from the receipt card
Each consequential act is confirmed once, by a single-use approval bound to the fingerprint of exactly what you reviewed.
How it works — Approve from the receipt card

What this role does

Approve each consequential act from a receipt card — the fingerprint of exactly what you reviewed — confirmed once, by a single-use approval bound to it. How it works — Approve each consequential act from a receipt card — the fingerprint of exactly what you reviewed — confirmed once, by a single-use approval bound to it.
Decide each conflict finding; an undecided blocking finding holds the engagement until it is cleared. How it works — Decide each conflict finding; an undecided blocking finding holds the engagement until it is cleared.
Review, redline, cite-check and run the Opposing Counsel Pass™ — work product for your own judgment, with what each engine received kept on the record. How it works — Review, redline, cite-check and run the Opposing Counsel Pass™ — work product for your own judgment, with what each engine received kept on the record.
See how every computed date was reached, and confirm it before it reaches a calendar. How it works — See how every computed date was reached, and confirm it before it reaches a calendar.

Where it lives

The console's own names and addresses, once signed in.

Review & decisions /admin/review: Findings, the redline, the cite check, the decision record.
Drafting desk /admin/drafting: The plan's documents in the desk's own editor.
Ask & run /admin/workspace: The engines, each run kept with what it received.
Matter command center /admin/matter: Every matter's overview, sources, people, tasks, documents and activity.

Paralegals and staff

Does the work of the matter: adds clients, screens names, asks for documents, keeps the sources, works the tasks and the calendar. A paralegal cannot approve, deliver or decide a conflict.

Setup checklist

Add your second factor
An authenticator app, enrolled at first sign-in.
Add a client
The conflict screen runs first, then the matter lands in the workstation with the client's portal invitation ready.
How it works — Add a client
Ask the client for documents
What each item is and why; see where every upload stands.
How it works — Ask the client for documents
Keep the sources
Upload to the matter: every version kept, read beside the original, a passage found in it.
How it works — Keep the sources
Work the tasks and the calendar
Team tasks, client items and deadlines, with the feed your calendar subscribes to.
How it works — Work the tasks and the calendar

What this role does

Screen every name against the firm's own records at every door — clients, parties, fiduciaries and the declined register. How it works — Screen every name against the firm's own records at every door — clients, parties, fiduciaries and the declined register.
Ask clients for documents — what each item is and why — and see where every upload stands. How it works — Ask clients for documents — what each item is and why — and see where every upload stands.
Keep every version of every source, read its text beside the original, and find a passage in it. How it works — Keep every version of every source, read its text beside the original, and find a passage in it.
Work issues, drafts and decisions in one place, each engine's own page a click away. How it works — Work issues, drafts and decisions in one place, each engine's own page a click away.

Where it lives

The console's own names and addresses, once signed in.

Matters /admin/matters: Every file in the firm.
Client intakes /admin/intakes: Invite a client to the intake; read it once sent.
Tasks & calendar /admin/tasks: Tasks, client items and deadlines.
Florida source library /admin/authority: The Florida source library.

Your clients

A portal under your firm's name. A client answers the decisions you put to them, uploads what you asked for, reads where things stand in your own words — and can ask your firm to delete their records.

Setup checklist

Open the invitation
The firm's emailed invitation signs the client in by a link; no password to make.
How it works — Open the invitation
Answer the decisions the firm asked
Each decision is answered once; the answer is on the record.
How it works — Answer the decisions the firm asked
Upload what the firm asked for
Each request says what the item is and why.
How it works — Upload what the firm asked for
Read where things stand
In the firm's own words, with the shared documents pinned to the version shared.
How it works — Read where things stand
Ask for deletion, if ever needed
From Security & data; the firm answers on the record.
How it works — Ask for deletion, if ever needed

What this role does

A portal under your firm's name: they answer the decisions you put to them and read where things stand in your own words. How it works — A portal under your firm's name: they answer the decisions you put to them and read where things stand in your own words.
A shared link gives exactly the version you shared — never a later one. How it works — A shared link gives exactly the version you shared — never a later one.
They can ask your firm to delete their records, and read your answer on the record. How it works — They can ask your firm to delete their records, and read your answer on the record.

Where it lives

The console's own names and addresses, once signed in.

The client's matter /matter/[id]: Where things stand, the decisions, the documents asked for.
Overview /dashboard: The client's account.
Security & data /dashboard/security: Devices, the second factor, deletion requests.

What is locked today

Read from this deployment when the site was built: every surface a firm's work can meet that is not shipped today, with who unlocks it and why it waits.

What is locked today
Surface	Status	Who unlocks it	Why it waits
ChatGPT 5.6 Sol tier and the dual consensus mode	Owner-gated	included in the workstation AI plans	Waiting on the platform owner: the governed OpenAI key (owner gate).
Fable 5 tier (per-document surcharge)	Owner-gated	the per-document surcharge at activation	Waiting on the platform owner: FABLE_DRAFT_SURCHARGE_CENTS (owner prices it).
Citator treatment (Westlaw KeyCite · Lexis Shepard's)	Staged	the firm's own citator entitlement	Built and dormant until a partner provisions credentials: partner credentials from Thomson Reuters / LexisNexis.
Calendar — OAuth push (Google / Microsoft)	Staged	a firm admin	Built and dormant until a firm turns it on: the firm's own OAuth credentials.
Clio — matter link and packet export	Staged	a firm admin connects; the firm's administrators, attorneys and paralegals link and export	Built and dormant until a firm turns it on: the firm's own Clio credentials.
DocuSign / e-signature (scoped)	Staged	a firm admin	Built and dormant until a firm turns it on: DOCUSIGN_BASE_URL · ACCOUNT_ID · ACCESS_TOKEN.
Plaid / bank sync	Staged	a firm admin	Built and dormant until a firm turns it on: the firm's own Plaid credentials.
Stripe (alternate rail)	Owner-gated	the platform's operator (an owner step)	Waiting on the platform owner: STRIPE_SECRET_KEY · WEBHOOK_SECRET (+ tier prices).
Transactional email (Resend) and the delivery ledger	Owner-gated	the platform's operator (an owner step)	Waiting on the platform owner: RESEND_API_KEY (present) + RESEND_WEBHOOK_SECRET (absent — the ledger is blind).
Turnstile on public forms	Owner-gated	the platform's operator (an owner step)	Waiting on the platform owner: NEXT_PUBLIC_TURNSTILE_SITE_KEY (absent); the firm consult door also verifies server-side with TURNSTILE_SECRET_KEY.
Upload malware scanner (quarantine pipeline)	Owner-gated	the platform's operator (an owner step)	Waiting on the platform owner: SCANNER_* (absent); structural checks always run.
External monitor bearer (HEALTH_TOKEN)	Owner-gated	the platform's operator (an owner step)	Waiting on the platform owner: HEALTH_TOKEN (absent).
The governed MCP server: the firm API's reads as tools for an AI assistant, and one tool that files a proposal	Owner-gated	the platform switches the server on; then a firm key (the same scopes, walls, allowlist and limits as the REST API) opens it	Waiting on the platform owner: PLATFORM_MCP_ENABLED — until the platform sets it, /mcp answers 404 to every request.
Single sign-on for a firm: its own identity provider, its own domain, just-in-time membership	Owner-gated	a firm's administrator asks; the platform's administrator activates after the DNS proof; people at the firm's domain sign in through the firm's provider	Waiting on the platform owner: SAML 2.0 turned on for the Supabase project, then SSO_SAML_ENABLED=1 on the deployment, and each firm's provider registered with `supabase sso add` (owner steps, docs/auth/SSO-OWNER-GUIDE.md); Supabase Pro includes 50 single sign-on users a month, then $0.015 each.
The EstateDraftFL app for iPhone and Android: sign in, matters, send a document, notifications, remote revocation	Owner-gated	anyone with an account: a firm's staff (after the platform's second factor) and the matter's own client	Waiting on the platform owner: the owner's Expo project, the sign-in allow-list entry estatedraftfl://auth/callback, Apple (and, for Android notifications, Firebase) credentials through Expo's build service, the store submissions, then MOBILE_APP_PUBLISHED=1 on the deployment (mobile/README.md).

ChatGPT 5.6 Sol tier and the dual consensus modeOwner-gated
included in the workstation AI plans
Waiting on the platform owner: the governed OpenAI key (owner gate).
Fable 5 tier (per-document surcharge)Owner-gated
the per-document surcharge at activation
Waiting on the platform owner: FABLE_DRAFT_SURCHARGE_CENTS (owner prices it).
Citator treatment (Westlaw KeyCite · Lexis Shepard's)Staged
the firm's own citator entitlement
Built and dormant until a partner provisions credentials: partner credentials from Thomson Reuters / LexisNexis.
Calendar — OAuth push (Google / Microsoft)Staged
a firm admin
Built and dormant until a firm turns it on: the firm's own OAuth credentials.
Clio — matter link and packet exportStaged
a firm admin connects; the firm's administrators, attorneys and paralegals link and export
Built and dormant until a firm turns it on: the firm's own Clio credentials.
DocuSign / e-signature (scoped)Staged
a firm admin
Built and dormant until a firm turns it on: DOCUSIGN_BASE_URL · ACCOUNT_ID · ACCESS_TOKEN.
Plaid / bank syncStaged
a firm admin
Built and dormant until a firm turns it on: the firm's own Plaid credentials.
Stripe (alternate rail)Owner-gated
the platform's operator (an owner step)
Waiting on the platform owner: STRIPE_SECRET_KEY · WEBHOOK_SECRET (+ tier prices).
Transactional email (Resend) and the delivery ledgerOwner-gated
the platform's operator (an owner step)
Waiting on the platform owner: RESEND_API_KEY (present) + RESEND_WEBHOOK_SECRET (absent — the ledger is blind).
Turnstile on public formsOwner-gated
the platform's operator (an owner step)
Waiting on the platform owner: NEXT_PUBLIC_TURNSTILE_SITE_KEY (absent); the firm consult door also verifies server-side with TURNSTILE_SECRET_KEY.
Upload malware scanner (quarantine pipeline)Owner-gated
the platform's operator (an owner step)
Waiting on the platform owner: SCANNER_* (absent); structural checks always run.
External monitor bearer (HEALTH_TOKEN)Owner-gated
the platform's operator (an owner step)
Waiting on the platform owner: HEALTH_TOKEN (absent).
The governed MCP server: the firm API's reads as tools for an AI assistant, and one tool that files a proposalOwner-gated
the platform switches the server on; then a firm key (the same scopes, walls, allowlist and limits as the REST API) opens it
Waiting on the platform owner: PLATFORM_MCP_ENABLED — until the platform sets it, /mcp answers 404 to every request.
Single sign-on for a firm: its own identity provider, its own domain, just-in-time membershipOwner-gated
a firm's administrator asks; the platform's administrator activates after the DNS proof; people at the firm's domain sign in through the firm's provider
Waiting on the platform owner: SAML 2.0 turned on for the Supabase project, then SSO_SAML_ENABLED=1 on the deployment, and each firm's provider registered with `supabase sso add` (owner steps, docs/auth/SSO-OWNER-GUIDE.md); Supabase Pro includes 50 single sign-on users a month, then $0.015 each.
The EstateDraftFL app for iPhone and Android: sign in, matters, send a document, notifications, remote revocationOwner-gated
anyone with an account: a firm's staff (after the platform's second factor) and the matter's own client
Waiting on the platform owner: the owner's Expo project, the sign-in allow-list entry estatedraftfl://auth/callback, Apple (and, for Android notifications, Firebase) credentials through Expo's build service, the store submissions, then MOBILE_APP_PUBLISHED=1 on the deployment (mobile/README.md).

Status is evaluated against this deployment's configuration by the capability-status service at build time; the catalogue's facts were last reviewed on the date shown.

Still stuck?

The developer pages cover the API, the webhooks and the MCP server; the contact form reaches a person, and every message is recorded the moment it is sent.

Developers Contact us Moving in