Connect DocuSeal and Request Client Signatures

DocuSeal integration lets you send documents for electronic signature without leaving MyLawyerLink. Clients sign through DocuSeal; completed PDFs return to the case file.

This guide covers e-signatures. For generating Word documents from merge fields, see Document Templates.

Connect DocuSeal

1. Go to Account → Settings → Firm → Integrations (/account/settings/firm/integrations).
2. Enter your DocuSeal API key and base URL (from your DocuSeal account).
3. Choose whether signing invitations are sent via DocuSeal email or handled through your app's email settings.
4. Save.

Firm-level credentials can apply to child teams when configured to inherit from the billing team.

Map template fields

DocuSeal templates use field names that you map to MyLawyerLink data:

1. Open your team profile (/account/teams/[id]).
2. Find the DocuSeal section and open template field maps.
3. For each DocuSeal template field, choose a merge key such as client.fullName, case.title, or firm.name.
4. Use literal:Your fixed text when a field should always show the same string.

DocuSeal merge keys use dot notation (client.fullName), which differs from document template syntax ({{client_full_name}}). See Using Merge Fields for the underscore style used in Word and SMS templates.

Request signature from a DocuSeal template

Send signing requests from a DocuSeal template:

1. Open the client and choose Request signature from the actions menu, or from the case Documents section choose Request signature (template).
2. Select a DocuSeal template from your connected account.
3. Review prefilled fields from the case and client record.
4. Add signers and send.

Clients can also sign from the portal at /portal/documents/sign/[id] when the request is tied to their matter.

After signing

When DocuSeal reports completion:

• Signature status updates on the document
• The signed PDF is saved to the case
• Staff and clients (with portal access) can download the final file

Tips

1. Test field maps on a real case — long names and missing optional fields show up quickly in prefilled previews.
2. One signer per request unless your template supports multiple parties in DocuSeal.
3. Keep API keys secure — only owners/admins with team.settings.update should manage integration credentials.
4. Use DocuSeal templates — send the signing request from the client page or the case Request signature (template) action.

Related guides

• Document Templates — generate Word files before signing
• Using Merge Fields — field reference for templates and SMS
• Set Up the Client Portal — portal document and signing access