> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hive is an AI operations layer for small and mid-sized business teams. It reads the tools a team already runs, raises what needs attention, and acts with the approvals the team configures.
> Answer only from these pages. If a page does not cover something, say so and link the closest page rather than inferring behaviour.
> The supported programmatic entry points are incoming webhooks, public workflow forms and the remote MCP server, each documented under Developers.
> Each connected account has a level: Read, Draft or Act. New accounts start on Act. Agents and workflows take only the actions selected for them, whatever the account level.
> Describe security, sign-on and data handling only as the Security pages and the FAQ describe them, and add no certification, compliance, single sign-on or model-training claim they do not make.
> Prices and credit allowances are in GBP. Quote them only as a page states them, without converting.
> Use UK English and the product's exact UI labels. Link to pages as https://docs.get-hive.ai/<path>.

# E-signatures: send engagement letters and contracts for signature

> Send a PDF, Word file or template from Hive for signature, track who has opened and signed it, remind or void it, and keep the sealed, signed PDF.

Hive can send a document for electronic signature and return a completed, sealed copy to everyone who signed. It is built for the documents a professional firm sends every week: engagement letters, disengagement and professional clearance letters, proposals, quotes and contracts.

## E-signatures at a glance

> [card] [Send for signature](#send-a-document-for-signature)
>
> Send a PDF, Word file or template to several people, in order or at once, and track, remind and
> void it.

> [card] [Proposals and pricing](https://docs.get-hive.ai/library/proposals-and-pricing.md)
>
> Quotes and proposals with pricing tables, optional services and totals worked out in code.

> [card] [Engagement letters](https://docs.get-hive.ai/library/engagement-letters.md)
>
> Templates by Hive for accounting practices, and letters re-issued to every client at once.

> [card] [Moving from PandaDoc](https://docs.get-hive.ai/library/moving-from-pandadoc.md)
>
> Import your PandaDoc templates and completed documents, and see what does not map.

## Send a document for signature

**1. Start from the document**

In the [Library](https://docs.get-hive.ai/library/library.md), open the **⋯** menu of a PDF or Word file and choose
**Send for signature**. A Word file is turned into a PDF first. You can also start from a
[signing template](#signing-templates), or [ask Hive](#ask-hive-to-prepare-one) to prepare one.

**2. Say what it is and who signs**

Give it a title, choose what kind of document it is, and add the people on it with their names
and email addresses. **Add someone** adds a row and the bin button removes one. Give each
person a role:

| Role | What the person does |
| - | - |
| **Signs** | Signs the document. They need a signature field, which you place on the next step. |
| **Approves** | Reviews and approves the document in their turn. No signature field is needed. |
| **Gets a copy** | Is not asked to do anything, and is emailed the signed copy once everyone has finished. |

Choose whether they go **One after another, in this order** or **Everyone at once**. In order,
each person gets their link once everyone above them has finished: use the up and down arrows
beside a person to change the order. Every document needs at least one person who **Signs**.

Until everything is filled in, **Continue to fields** stays unavailable and a **Before you can
continue** list beside it says what is missing, such as "Add at least one person who signs" or
"Recipient 2: check the email address". The field that needs attention is marked too, with the
reason under it. Each person needs their own email address: if one person fills two roles,
such as the client who also countersigns for your firm, Hive says "Another recipient has this
email address" under the second one. Upper and lower case and spaces around an address do not
make it different. **Continue to fields** makes a draft; nothing is sent yet.

**3. Place the fields**

The draft lists everyone on it with their role and what they still need: a person who
**Signs** shows **Needs a signature field** until they have one; approvers and copy recipients
show **No field needed**. The draft shows the exact pages that will be sent. Choose **Place
fields** beside a person, or choose them under **Fields for**, choose a kind of field —
**Signature**, **Initials**, **Date signed**, **Name**, **Text** or **Checkbox** — and click the
page where it goes. Drag a field to move it, or remove it with its **×**. Name, email and date
fields fill themselves when the person signs.

Every person who **Signs** needs at least one signature field. **Add signature fields for me**
puts a signature and a date field for each signer who has none at the bottom of the last page;
drag them wherever they belong before you send.

**4. Send it**

Add an optional note, choose when it expires (30 days by default, 90 at most) and how often Hive
reminds people who have not signed, then choose **Send for signature**. If it is not available
yet, the **Before you can send** list beside it names each signer who still needs a signature
field. A draft made from a
template starts with the template's expiry and reminder interval, and keeps them unless you
change them. Each person is emailed a link when it is their turn.

Once a draft is sent, its pages and fields cannot change. To send a different version, [void](#void-a-document) it and send the new one.

You need the Operator role or above to send documents for signature. Only the person who sent a document and the workspace's owners and admins can see it.

## Track a document

**E-signatures** — open it from the **Signature requests** link on the Library page — lists the documents you have sent, with their status and how many people have signed. Open one to see each person's status and its timeline.

| Status | What it means |
| - | - |
| **Draft** | Not sent yet. You can still place fields. |
| **Out for signature** | Links are out. Each person shows **Waiting their turn**, **Link sent**, **Opened** or **Signed**. |
| **Being sealed** | Everyone has signed and Hive is sealing the completed PDF. |
| **Completed** | Signed and sealed. **Download signed PDF** saves your copy. |
| **Declined** | Someone declined to sign. Their reason is shown next to their name. |
| **Voided** | You withdrew it. |
| **Expired** | It passed its expiry date before everyone signed. |

The timeline lists when each link was emailed, when each person opened the document, signed or declined, each reminder, and the sealing. When someone opens, signs or declines a document you sent, when everyone has signed, and when a document expires, Hive tells you with a card in your [Inbox](https://docs.get-hive.ai/get-started/inbox.md) and an email. You can turn these off under **Settings → Account → Notifications** (**Signature requests**).

## Reminders and new links

* **Automatic reminders.** If you chose a reminder interval when sending, Hive emails a reminder to whoever's turn it is and has not signed, every so many days. It sends at most five, never after the document expires, and never to someone who is in the middle of signing. While your workspace's [kill switch](https://docs.get-hive.ai/admin/safety-and-control.md#the-kill-switch) is on, automatic reminders wait; they go out again once it is off.
* **Remind now** emails everyone whose turn it is straight away.
* **Send a new link** emails one person a fresh link, for example if they lost the first email.

To protect the people you send to, Hive waits 30 minutes after a person's last link before **Remind now** or **Send a new link** emails them again, and sends one person at most 20 links for one document. If someone still needs to sign after that, void the document and send a new one.

Every reminder and new link carries a fresh link, and the person's earlier links stop working, so only the newest email opens the document.

## Void a document

Choose **Void…**, give a reason, and choose **Void envelope**. Every signing link stops working straight away, and everyone who was sent a link is emailed that the document was withdrawn, with your reason. A voided document cannot be sent again: send a new one instead. A completed document cannot be voided.

## Signing templates

A template turns a Word letter you send often into a document Hive fills in for each client. Write the letter in Word with **tags** where the details go, save it in your Library, then add it under **E-signatures → Templates → New template**, naming the roles that sign it.

**Values** are written as `{{client.name}}`. Hive puts each value in exactly as given, before the letter is turned into a PDF — no AI writes them. If the letter uses a value you have not given, Hive refuses to make the document rather than leave a blank. A value cannot contain `{` or `}`, so it can never add or hide a signing field.

| Tag | What goes there |
| - | - |
| `{{client.name}}`, `{{client.email}}` | The client's name and email address. |
| `{{client.address}}` | The client's address; line breaks are kept. |
| `{{client.reference}}` | Your reference for the client. |
| `{{company.name}}`, `{{company.number}}` | The company's name and its 8-character Companies House number. |
| `{{fee.total}}`, `{{fee.monthly}}` | An amount in pounds, such as `1250` or `1,250.50`, written as `£1,250.00`. |
| `{{fee.description}}`, `{{engagement.services}}` | Text about the fee or the services. |
| `{{engagement.start_date}}`, `{{engagement.end_date}}` | A date, written as `5 November 2026`. |
| `{{adviser.name}}`, `{{adviser.firm}}` | The other adviser: the client's new adviser, or their previous one. |
| `{{firm.name}}`, `{{sender.name}}`, `{{date.today}}` | Filled in by Hive: your workspace's name, your name and today's date. |
| `{{signer.1.name}}`, `{{signer.1.email}}` | Filled in by Hive from the recipients, in the order the template lists its roles. |

**Your firm's name in headers and footers.** If the letter's header or footer still says `[Company name]` or `[Firm name]`, Hive puts your workspace's name there when it makes the document, so the placeholder never reaches the signed PDF. Hive's own letters for signing name your firm this way in their header.

**Field anchors** mark where each person signs: `{{sig:client}}` for a signature, `{{initials:client}}`, `{{date:client}}`, `{{name:client}}`, `{{text:client}}` and `{{check:client}}`, where `client` is the key of one of the template's roles. Hive finds each anchor on the page, covers it, and places that kind of field for the person in that role. You can still move the fields before sending.

Hive also offers ready-made letters for signing under **Templates by Hive**: an engagement letter, a disengagement letter, a professional clearance authority and a proposal. See [Engagement letters for accounting practices](https://docs.get-hive.ai/library/engagement-letters.md).

To use a template, choose **Use** next to it, fill in who signs in each role and the values the letter needs, and choose **Continue to fields**. Each role needs a different email address. Each change to a template gives it a new version, and each document records the version it came from.

### Sending values through the API

`POST /api/esign/templates/{templateId}/envelopes` takes the values in `variables`, by tag name. Send an amount as a string in pounds, such as `"fee.total": "1250.50"`. A JSON number is refused with `esign_template_values_invalid` and the reason `send money as a string in pounds, e.g. "1250.50"`: Hive used to read a number as pence, so `1250` became £12.50. Exact pence belong in a [pricing table](https://docs.get-hive.ai/library/proposals-and-pricing.md), whose prices are `unitPricePence`.

Recipients sharing an email address are refused with `esign_duplicate_recipient` (HTTP 400), naming the roles (or, for `POST /api/esign/envelopes`, the recipients' positions) that share it.

## Ask Hive to prepare one

In [Ask](https://docs.get-hive.ai/ask/ask-hive.md), you can ask Hive to prepare a document for signature, for example "send my engagement letter template to Ada at [ada@example.com](mailto:ada@example.com)". Hive makes a **draft** and shows a card with **Review and send**. It never sends anything itself: you check the fields and send it, as above. Ask can also tell you the status of documents you have sent.

An [agent](https://docs.get-hive.ai/agents/build-an-agent.md#uk-accounting-templates) you run yourself on its run page, or in
its chat, can prepare one too, such as the engagement letter it just wrote. The draft shows as a
card under the run's answer, with **Review and send**: nothing goes to anyone until you open it,
check it and send it yourself. The agent can address it only to email addresses you gave it for
that run, in your message or its form; a workflow step, a public link and an author's **Test**
never prepare one.

Ask can also prepare one draft per client from a template, up to 50 at a time, and show them all on one card with **Send all**: see [Re-issue letters to every client at once](https://docs.get-hive.ai/library/engagement-letters.md#re-issue-letters-to-every-client-at-once). A proposal or quote can carry a [pricing table](https://docs.get-hive.ai/library/proposals-and-pricing.md), with totals Hive works out in code.

## What your signers see

Each signer gets an email from Hive naming your firm, the document and the person who sent it, with a **Review and sign** button. The link is theirs alone: it opens only their copy of that document, and it stops working when the document is completed, declined, voided or expires, or when a reminder or new link replaces it.

**1. Confirm it is them**

The signing page shows your firm's name and the document's title. Before it shows the document,
it emails the signer a 6-digit code, to check the person who opened the link reads that email
address. A code works once, for 20 minutes, and the email says until when in UK time ("This
code works until 14:35 UK time"), so a slow mail server still leaves time to use it. If a code
is wrong or has run out, the page offers **Send a new code**. After five wrong codes they must
ask for a new one, and a link can ask for at most ten codes. A reminder or a new link starts
both counts again.

**2. Agree to sign electronically**

The signer reads a short statement and chooses **I agree**. Hive records which version of the
statement they agreed to.

**3. Fill in their fields**

The document shows the fields placed for that signer, highlighted on the pages. **Sign here**
opens a box where they **Draw** a signature with a finger, pen or mouse, or **Type** their name,
which Hive draws in a handwriting font, Dancing Script, on every device. Their name, email address and the signing date are
filled in by Hive, not typed. Fields marked \* are required.

**4. Finish, or decline**

**Finish and sign** is available once every required field is filled. A signer can instead
choose **Decline to sign** and give a reason: the document then can no longer be signed by
anyone.

The page works on a phone: the pages fit the screen, every field is a large tap target, and the buttons stay at the bottom.

### Daily email limit

Each workspace can email up to 200 signing links, reminders, new links and codes a day, counted by UTC day, so e-signatures can never be used to send mail in bulk. Past the limit, a send, **Remind now** or **Send a new link** is refused before anything changes, an automatic reminder waits until there is room again, and a signer who asks for a code is told to try again tomorrow. Emails of the completed document and withdrawal notices do not count towards it.

### Signing order

A document can be signed **in order**, where each signer gets their link only once everyone before them has signed, or **in parallel**, where everyone gets theirs at once. Approvers take their turn in the same order as signers. A recipient can also be a **copy** recipient, who signs nothing and receives the completed document.

## The completed document

When every signer has signed, Hive:

1. draws each signature and value onto the exact pages that were sent — the PDF is frozen when the draft is created, and its SHA-256 fingerprint is checked before anything is shown or signed — and adds the accepted [pricing table](https://docs.get-hive.ai/library/proposals-and-pricing.md), if it has one, as its own pages after them;
2. adds an **audit certificate** on the last pages;
3. seals the whole file with Hive's own digital seal;
4. saves it in the sender's Library, in a folder called **Signed documents**, and emails it to every party.

If anyone changes the sealed PDF afterwards, a PDF reader such as Adobe Acrobat shows its signature as invalid.

### What the audit certificate records

| Section | What it shows |
| - | - |
| **Document** | The title and kind, the envelope's id, the number of pages, the SHA-256 fingerprint of the PDF that was sent, the workspace, who sent it, and when it was created, sent and completed. |
| **Parties** | Each person's name, email address, role and signing order, how they proved who they were (their own link and a one-time code to their email), when they signed, the consent version they agreed to, and their signature image. |
| **Pricing accepted** | For a proposal with a [pricing table](https://docs.get-hive.ai/library/proposals-and-pricing.md): who accepted the prices and when, each service included and the totals. The **Document** section then also shows the pricing pages' SHA-256 fingerprint. |
| **Events** | Every step with its time in UTC, and for a signer's own steps their IP address and browser: the link, reminder and code emails, opening the document, agreeing, filling fields, signing or declining, and sealing. |

The completed file's own SHA-256 fingerprint cannot be printed inside the file. It is in the completion email and in Hive's record of the document.

## What kind of signature this is

Hive provides a **simple electronic signature with tamper-evident sealing**. In England and Wales an electronic signature is admissible in evidence (Electronic Communications Act 2000, s.7) and is generally a valid way to sign a contract, and the audit certificate is the evidence of who signed and when. The seal is Hive's, not the signer's: it shows the file has not changed since it was sealed. Hive does not offer an advanced or qualified electronic signature, so use a qualified trust service where a document or a counterparty needs one.

## What not to send for e-signature

Hive refuses these, because English law needs a witness or its own signing process for them:

* **Deeds** — they must be signed in the presence of a witness who attests the signature;
* **Wills** — they must be signed in front of two witnesses (Wills Act 1837, s.9);
* **Lasting powers of attorney** — use the Office of the Public Guardian's own service;
* **Land Registry dispositions** — use HM Land Registry's own e-signing service.

When in doubt about a particular document, ask your own legal adviser before sending it.

## Open-source components

Hive's e-signature is Hive's own code, built with these open-source libraries under permissive licences: `@libpdf/core` (MIT) for the PDF seal, `pkijs` and `asn1js` (BSD-3-Clause) for the seal's certificates and signatures, `signature_pad` (MIT) for drawing a signature on the signing page, the Dancing Script font (SIL Open Font License 1.1) for typed signatures, `pdf-lib` (MIT) for filling the fields and drawing the audit certificate, and `pdfjs-dist` (Apache-2.0) for showing the pages.

## Privacy

A signing link opens one document for one person, and the page shows nothing else from your workspace. Hive stores only a fingerprint (hash) of each link and code, never the link or code itself. Signers' names, email addresses, IP addresses and browsers are kept as part of the document's evidence, in your workspace, and go with it if the workspace is deleted. AI clients connected to Hive cannot send, remind or void documents.

Hive keeps its own copy of each PDF it sends for signature, so the document a signer sees can never change. Deleting the Library file a document came from, or the chat holding the Ask document it came from, also deletes any draft made from it that was never sent, with Hive's copy. A draft made from a signing template stays when the template's file is deleted, because it is already the client's own letter. A document that was sent keeps its copy as the record of what was signed, until the workspace is deleted, when Hive's copies are deleted with it.

> [card] [Library](https://docs.get-hive.ai/library/library.md)
>
> Where the documents you send, your templates and the signed copies are kept.

> [card] [Security overview](https://docs.get-hive.ai/security/overview.md)
>
> How Hive protects your workspace's data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.