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

> ## Agent Instructions
> Flowsign is one word with a lowercase s.
> The REST API base URL is https://my.flowsign.app and every endpoint lives under /api/v1.
> When answering API questions, cite the HTTP method and endpoint path.
> API access needs the Enterprise plan and an API key with the API access permission.

# Library documents in templates and packages

> Prepare a document's fields once in the library, then link it into templates and draft packages so every edit reaches them.

When you choose a library document for a template or a draft package, Flowsign links it instead of copying it. The library document owns its own roles and fields. Change them once in the library and every template and draft that links the document picks up the change.

![The People and payroll folder in the library, with the Employee handbook card showing a badge for two fields](https://mintcdn.com/doc-a97e5290/NKy0rA2sOyfs2N_8/images/guides/library/linked-documents.png?fit=max\&auto=format\&n=NKy0rA2sOyfs2N_8\&q=85\&s=8538352fba63b4286c5840b89de051d8)

A library document with fields, showing its field-count badge.

## Prepare fields in the library

Open a document card's actions menu in the [Library](https://docs.flowsign.app/guides/library/all-files.md) and choose **Prepare fields**. This opens the field editor for the library document, where you add roles and place fields just as you would in a template. **Prepare fields** needs the **Manage the library** permission. The palette's **Merge fields** section adds merge fields to a PDF: see [Merge fields on PDFs](https://docs.flowsign.app/guides/templates/merge-fields-on-pdfs.md#adding-a-merge-field-in-the-field-editor).

Cards with fields show a small badge with the number of fields placed.

Editing a library document's fields or roles always needs **Manage the library**, even when you can edit a template that links it.

## Document details

**Details** in a document card's actions menu opens **Document details**. Anyone who can open the library can use it. It shows the document's type, pages, file size, recipients, fields, location, who uploaded it and when it was created and last updated. **Used in** lists each template that links the document, one per line, or reads **No templates**. With **Manage the library**, the dialog also offers **Prepare fields** (or **Edit document** for a Dynamic document).

![The actions menu on a library document card, with Prepare fields](https://mintcdn.com/doc-a97e5290/NKy0rA2sOyfs2N_8/images/guides/library/linked-documents/prepare-fields.png?fit=max\&auto=format\&n=NKy0rA2sOyfs2N_8\&q=85\&s=23eb3c04f938d1dd253e148abaabf105)

Prepare fields in a library document's actions menu.

If templates already use the document, the field editor shows an alert at the top, for example "2 templates use this document. Saving changes them too."

![The library field editor showing the New starter role, the field palette and an alert that one template uses the document](https://mintcdn.com/doc-a97e5290/NKy0rA2sOyfs2N_8/images/guides/library/linked-documents/library-field-editor.png?fit=max\&auto=format\&n=NKy0rA2sOyfs2N_8\&q=85\&s=3ff41ff9c01d1cbfb8c981b335b17e61)

The field editor for a library document, with its own roles.

## Link a document into a template or draft

Pick the document from the library when adding documents to a template on the template setup screen, or to a draft package. It appears in the document list with **Library** in its **Source** column.

In a template, picking library documents that have roles always opens the **Choose roles** step. It lists every role in the picked documents. For each one, pick an existing template role to fill it, or choose its **New role** option (for example **New role: Client**) to add it to the template as a new role. A template role with the same name is already selected for you. An unnamed role, like the blank one a new template starts with, is chosen for a library role with no match and takes its name. Then choose **Add documents**, or **Back** to change your pick. Anyone who can edit the template can do this.

In a draft package, the same step is called **Choose recipients**. For each library role, pick an existing recipient, or choose its **New recipient** option (for example **New recipient for Client**) to add one. Then choose **Add documents**. A recipient with the same role name is already selected for you.

In a template, **Rename in this template** gives a linked document its own name in that template only. The library and other templates keep theirs. The name can include merge fields: type `{{` to pick one. **Use library name** goes back to the library name. In a package, a linked document can't be renamed.

A linked document can't be edited inside the template's or package's field editor. Its fields come from the library, so you change them there.

## The linked document's menu

A linked document's menu offers:

* **Rename in this template**: name the document for this template only. Templates only.
* **Use library name**: drop this template's own name and go back to the library name. Shown once you've renamed it.
* **Edit in library**: opens the library field editor for the document. Only people with **Manage the library** see this.
* **Choose roles**: decide which of your roles or recipients fills each library role.
* **Detach to customise**: give this template or draft its own copy of the document and its fields.
* **Clear fields**: breaks the link to the library first, then removes every field from this copy. Dynamic documents don't offer this.

![A linked document card with a Library chip and a menu offering Preview, Edit in library, Choose roles, Detach to customise and Clear fields](https://mintcdn.com/doc-a97e5290/NKy0rA2sOyfs2N_8/images/guides/library/linked-documents/linked-document-menu.png?fit=max\&auto=format\&n=NKy0rA2sOyfs2N_8\&q=85\&s=c17a3e1c8beaabab3e08f0c2618dffbd)

The menu on a linked document in a template.

## Choose roles

Each template or draft keeps a map from the library document's roles to its own: template roles in a template, recipients in a package. Roles match by name automatically, and a library role with no match in a template becomes a new template role.

To change the mapping, choose **Choose roles**. The **Choose who fills each role** dialog lists every library role with a picker beside it. Choose a role or recipient for each one, then **Save roles**. Merge fields on the document that read a library role use whichever role or recipient you choose for it.

A role or recipient that fills a library role shows a link icon. Click it to see which documents and roles it fills, and choose one to jump to that document. It can't be removed while it fills a library role: choose someone else for that role first, or remove the document. In the library field editor, a role that a merge field reads from can't be removed either.

![The Choose who fills each role dialog mapping the library role New starter to the template role New starter](https://mintcdn.com/doc-a97e5290/NKy0rA2sOyfs2N_8/images/guides/library/linked-documents/choose-roles.png?fit=max\&auto=format\&n=NKy0rA2sOyfs2N_8\&q=85\&s=9f5341b61854e887cc2c354ca26165a5)

Choose who fills each library role.

If a library role is still unfilled, the document shows a red warning such as "Choose who fills Manager before sending." with a **Choose roles** button.

## Detach and reset

**Detach to customise** asks you to confirm, then gives the template or draft its own copy. From then on, library changes don't reach it and you can edit its fields directly.

A detached copy's **Source** reads **Library copy**, and its menu offers **Reset to library version**. This discards every change made to the copy and links the library version again.

## Add a template's own document to the library

A document uploaded straight to a template can move into the library. Choose **Add to library** from the document's menu in the template builder, then confirm. The document, its roles and its fields are copied into the library, and the template links to that copy, so library edits reach it from then on. **Add to library** needs **Manage the library**, and only templates offer it.

## What blocks sending

An unfilled library role blocks sending, scheduling, launching and publishing. Trying shows "Choose who fills each library role before sending." and takes you back to the documents. Fill it with **Choose roles** first.

In a package, choose who fills each library role before you send. A library document's fields are placed in the library, so a package whose documents all come from the library has no fields to place. Its main button reads **Activate package** and sends it, and the **Fields** step is skipped.

## Sent packages are frozen

When a draft package is scheduled or sent, each linked document is frozen into a copy. Later library edits never reach packages that have already gone out, so what recipients see doesn't change under them.

Corrections to a sent package also work on copies, not the library document.

## Trashing a linked document

You can't move a library document or folder to trash while templates link it. The error names the templates, for example "Templates link this document: "Employment agreement". Remove it from them first."

A document used by a package can't be trashed either. The error starts "In use by a package" and names the document.

## Related

* [Library](https://docs.flowsign.app/guides/library/all-files.md)
* [Trash](https://docs.flowsign.app/guides/library/trash.md)
* [Template builder](https://docs.flowsign.app/guides/templates/template-builder.md)
* [Create a package](https://docs.flowsign.app/guides/packages/create-package.md)


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