Maica Docs.

Documents built from your Salesforce data.

THE PROCESS

From a record to a signed PDF

Maica Docs connects to your Org, so four steps turn live Salesforce data into a signed PDF. No export, no re-keying, no developer to wire it up.

Step 1

Build your template

Lay the document out in Maica Docs with the blocks you need.

Step 2

Map your Salesforce data

Connect your Org, then point merge fields at your objects and related lists.

Step 3

Generate from a record

Run the template against any record for a branded, signature-ready PDF.

Step 4

Sign and sync back

Collect signatures, then write the signed document back to Salesforce.

The builder

Everything You Need In One Builder.

Lay out the document, point it at your data, and let it adapt to the record it is generated from.

Lay a document out with the blocks you need. Structure it with headings and rich paragraphs, drop in photos or your logo anywhere in the layout, and build repeating tables that give you one row per related record. Add signature fields, page headers, footers and page numbers, set the page once, and every generated copy comes out the same.

Drop a merge token anywhere in the document and it reads live data straight from the record. Pull from the core record, its parents and its related lists, and format any value the way it should read in the finished document, whether that is a date, an amount or a change of case. Everything resolves the moment the document is generated.

Keep a block only when a Salesforce field matches the condition you set, and combine several conditions with AND/OR logic to cover the cases your documents really have. One template can then handle every variation, showing and hiding whatever the record calls for.

Choose A4, Letter or Legal with narrow, normal or wide margins, then set the type in Poppins, Inter, Georgia or Arial with the size, line height and spacing you want. Headers, footers and page numbers repeat on every page, can be suppressed on the first, and can merge in live record data. Table headers, rows and borders come from a set of ready-made colour themes, and your logo drops straight in as a block.

Data mapping

Pull In Related Data, Up And Down Your Org.

Step up through lookups

Walk from Contact to Account and beyond, pulling parent fields in by dot path.

Child lists as repeating tables

Drop a related list in as a table, one row per record, sorted and limited how you like.

Several levels deep

Nest tables inside tables to follow the relationships your document needs.

Format and total each column

Apply date and currency formats, then sum or count a column for a totals row.

Save it as a preset

Keep a relationship tree as a preset and reuse it across every template.

Templates

One Builder, Countless Documents.

A template for every document

Service agreements, care plans and statements, designed once and reused whenever your team needs them.

Generate straight from the record

Add a button to any Salesforce record or call it from a Flow, and the document generates in a click, prefilled from that record.

Built for Support at Home

Produce itemised, transparent Support at Home Statements that keep you compliant and your participants fully supported.

Access and signing

Control Who Builds, Generates And Signs.

Access controls at every layer, from how builders sign in to who opens each signing link, with signed and certified output at the end.

Google & magic-link sign-in

Builders log in with Google OAuth or a one-time email link. No passwords to manage.

Email & domain allowlisting

Grant access by email address or a whole domain, from an admin panel.

Workspaces & roles

Group templates into workspaces and invite members as owner, editor or viewer.

Scoped signing links

Each signing link is tied to a single document and the signer it was issued to.

Per-template Salesforce connection

Each template uses its own scoped connection, so access stays contained.

Written back to Salesforce

The signed document and its status are written back to the record it was generated from.

Order-based e-signature

Signers draw or type on a secure link, in the order you set, and can decline with a reason.

Certificate of completion

When everyone has signed, a certificate records the event timeline, a reference number and a SHA-256 hash.

Built by Maica

Powered By Maica.

Maica Docs works as a product in its own right, but it doesn't stand alone. It's built and backed by Maica, the Salesforce-native platform trusted by care and disability providers. Same team, same foundation.

Good to know

The questions providers ask us most about document generation.

Do we need Salesforce to use Maica Docs?

+

Maica Docs is at its best connected to Salesforce, which is its core strength. You connect once via OAuth and map merge fields to your objects, then every document reads live record data when it is generated.

How do signatures and certificates work?

+

Signers open a secure link and either draw or type their signature. You can set several signers to complete in a fixed order, and any signer can decline with a reason. When everyone has signed, the completed document and a certificate of completion, carrying a reference number and integrity hash, are written back to the Salesforce record.

Do signers need a Salesforce login?

+

No. Each signer gets a scoped link tied to their document, so participants and other external parties can sign without any login or Salesforce access of their own.

Can we match documents to our brand?

+

Set the fonts, margins, line height, headers and footers per template, and drop your logo in as an image block. Each template generates a branded, server-rendered PDF, with a draft watermark while a document is still in progress.

Can we pull in related records, like line items or contacts?

+

Yes. The relationship manager walks up to parent records and down to child lists, several levels deep, and lays a related list out as a repeating table, one row per record, with totals if you want them.

Can documents be generated automatically?

+

Yes. As well as a button on any record, you can call Maica Docs from a Flow, so a document is generated and prefilled the moment a record reaches the right stage, with nobody leaving Salesforce.