> ## 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>.

# Moving from PandaDoc: import templates and signed documents

> Bring your PandaDoc templates and completed, signed documents into Hive in a few clicks, see what does not map, and send everything from Hive from then on.

Hive does what a firm usually pays PandaDoc for: proposals and quotes with pricing tables, letters and contracts from templates with merge values, sending for signature to several people in order, tracking, reminders, voiding, and a sealed, signed PDF with an audit certificate. This page shows how to bring your PandaDoc templates and your completed documents across, and what changes on the way.

The import only **reads** from PandaDoc. Nothing is sent, changed or deleted in your PandaDoc account, and no one you have sent documents to is contacted.

## What each PandaDoc feature becomes

| In PandaDoc | In Hive |
| - | - |
| Templates with tokens | [Signing templates](https://docs.get-hive.ai/library/e-signatures.md#signing-templates) with values such as `{{client.name}}` |
| Pricing tables, proposals and quotes | [Pricing tables](https://docs.get-hive.ai/library/proposals-and-pricing.md), with totals worked out in code |
| Roles and signing order | Template roles, signed [in order or at once](https://docs.get-hive.ai/library/e-signatures.md#signing-order) |
| Signature, initials, date, text, checkbox | The same fields, placed for each role |
| Sent, viewed, completed, declined, voided | [Tracking](https://docs.get-hive.ai/library/e-signatures.md#track-a-document), [reminders](https://docs.get-hive.ai/library/e-signatures.md#reminders-and-new-links) and [voiding](https://docs.get-hive.ai/library/e-signatures.md#void-a-document) |
| Completed PDF and certificate of completion | A [sealed PDF with Hive's audit certificate](https://docs.get-hive.ai/library/e-signatures.md#the-completed-document) |
| Engagement letters for accountants | [Engagement letters](https://docs.get-hive.ai/library/engagement-letters.md), including re-issuing to every client at once |

## Before you start

* You need to be an **admin** or the **owner** of your Hive workspace.
* Connect **PandaDoc** on the [Integrations](https://docs.get-hive.ai/integrations/connect-an-app.md) page with your own PandaDoc API key. Hive reads only what that key can see, and only through your own connection: another member's PandaDoc connection is never used.

## Import

**1. Check first**

Open **E-signatures**, then **Templates**. Under **Moving from PandaDoc**, choose **Check what
will import**. Hive lists your PandaDoc templates and completed documents, and for each template
what it cannot bring across and why. Nothing is imported yet. One check lists as many items as
one import would bring across; if there is more, choose **Check what will import** again and
Hive lists the next ones.

**2. Import**

Choose **Import from PandaDoc**. Each item shows **Imported**, **Already imported**, **Not
imported** (with the reason) or **Could not import** (with the reason).

**3. Run it again until it is done**

One run imports up to 50 templates and 10 completed documents, and looks through up to 2,000
documents and 1,000 templates in PandaDoc. If there is more, Hive says so: run it again from the
same page and it carries on after the last item that run handled, so items that could not be
imported do not hold up the rest. If you leave the page, the next run starts from the beginning,
skips everything already imported, tries again anything that could not be imported, and moves
on the same way. If PandaDoc asks Hive to slow down, the run stops, keeps what it has imported, and you can
try again a few minutes later.

Everything the import files goes into a private folder in your [Library](https://docs.get-hive.ai/library/library.md) called **Imported from PandaDoc**.

## Templates

Each PandaDoc template becomes a signing template, ready to use, made from a Word file called *template name* **(from PandaDoc).docx**.

> [!WARNING]
>
> PandaDoc does not let other tools download a template's wording. The Word file Hive makes is an
> **outline**: it holds the template's values, its pricing lines and a tag for each of its fields, but
> not your text. Open the template in PandaDoc, copy its wording into the Word file, move each
> tag to where it belongs, and delete Hive's notes. Until you do, a document sent from the template
> contains only the outline.

What comes across:

* **Roles** keep their names and signing order. A template whose roles all sign at the same step is signed at once; otherwise in order. Hive sends to at most 10 people.
* **Tokens** become values where Hive has a match, and every other token is listed as not brought across:

| PandaDoc token | Hive value |
| - | - |
| *Role*`.FirstName` (or `.Name`) | `{{signer.N.name}}`, the full name of the person in that role |
| *Role*`.LastName` | Covered by the full name above when the first name is used |
| *Role*`.Email` | `{{signer.N.email}}` |
| *Role*`.Company` (the first one) | `{{company.name}}` |
| `Sender.FirstName`, `Sender.Company` | `{{sender.name}}`, `{{firm.name}}` |
| `Document.CreatedDate` | `{{date.today}}` |

* **Fields** for signature, initials, text and checkbox become the same fields for the role they belong to. A PandaDoc date field becomes **Date signed**, which Hive fills in when the person signs. Drop-downs, radio buttons, file requests, payment and stamp fields have no equivalent and are listed.
* **Pricing tables** come across when they map exactly: priced in pounds, whole quantities, VAT at 20%, 5% or 0%, at most one discount per line, and totals that come out the same when Hive adds them up. A line with no tax in PandaDoc is set as zero-rated, and the report says so. Hive offers one pricing table per document, so only a template's first table is used. The outline lists the lines; add the table when you send, as described in [Proposals and pricing](https://docs.get-hive.ai/library/proposals-and-pricing.md). A table that does not map exactly is listed instead of being changed.

Hive never imports a template for a deed, a will, a lasting power of attorney or a Land Registry document: [these cannot be signed electronically](https://docs.get-hive.ai/library/e-signatures.md#what-not-to-send-for-e-signature).

## Completed documents

Each completed PandaDoc document is filed as two PDFs: *document name*.pdf and *document name* **(signed, with certificate).pdf**, PandaDoc's signed copy with its certificate. Hive keeps them exactly as PandaDoc made them and does not seal them again.

Each run that imports documents also files **PandaDoc import record** *date and time*.csv, even when the run stops with an error, a spreadsheet with one row per signer: the PandaDoc document id, its name, when it was completed, each person's name, email address, role and signing time, and the Library files it went into. Imported documents you open from the Library are read like any other Library file; they do not appear in your **E-signatures** list, which shows documents sent from Hive.

Files over 50 MB are not imported, and are listed.

## Running it again

Hive remembers each PandaDoc template and document by its PandaDoc id. A later run skips everything already imported and downloads nothing for it. If you delete an imported file from the Library, the next run imports it again. If you archive an imported template but keep its Word file, the next run makes the template again: delete the Word file as well if you do not want it back.

Run the import from one admin account. What it imports goes into that admin's private folder, so if a second admin runs it, the items the first admin already imported show **Could not import** rather than being filed twice.

## Privacy

The import runs only when an admin starts it in the Hive app; AI clients connected to Hive cannot start it. It reads through the PandaDoc API key you connected and stores what it imports in your own private Library folder, where you choose who else can see it.

> [card] [E-signatures](https://docs.get-hive.ai/library/e-signatures.md)
>
> Send documents for signature, track them and keep the sealed copies.

> [card] [Proposals and pricing](https://docs.get-hive.ai/library/proposals-and-pricing.md)
>
> Pricing tables with exact totals and options the client chooses.


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