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

# Send document requests

> Send one or more published documents to people for signature, add an optional note, and preview the email before sending.

Send a document request when someone needs to sign. Each person receives their own email link and types their name to complete the request. They do not need a team member account.

## Before you send

* The document must be published, active, and have **Requires a signature** on.
* The people must be added to your organization with the correct email addresses.
* Your organization needs an active trial or subscription.
* Owners and administrators can send from **Requests**, a document, or a person's profile. Group Managers send missing requests within their assigned groups.

## Send to one or more people

1. Open a published document and click **Send request**. You can also start from **Requests**, the dashboard, or a person's profile.
2. The window is titled **Signature request**. In **To**, search for and select the people who should receive it.
3. In **Document**, select one or more published documents. Starting from a document keeps that document selected.
4. Add an optional note in **Compose**.
5. Open **Preview** to check the email.
6. Click **Send**.

Each person gets one email listing the documents you selected. You can still follow up on each document separately.

Use **Select all people** when you are not searching, or **Select all matching people** for a search result. Review the selection before sending. You can select up to **20 documents**. With one document, you can send to **500 people**. Choosing more documents means fewer people in that same send. Use a group for a larger roster.

## Add a note to recipients

The optional note appears in the email and on the signing page. Use it to explain why the document matters or what people should do next.

When sending from a group, its **Default Recipient Message** is prefilled. Edit or remove it before sending. Set the default in the group's **Settings → Automation**.

To change a note on an open request and send a reminder, use [Nudge with note](/guides/reminders#send-a-reminder-for-a-single-request).

## Assigning vs sending a request

| Action | Does it email people? | Can people open the document? |
| - | - | - |
| Add a signature-required document to a person | No, unless **Also send a document request** is on. | After a request is sent. Assignment alone does not grant access. |
| Send a document request | Yes. The email follows within a minute. The request shows as **Queued** until then. | Through the personal link and signing portal. |
| Add people or documents to a group | Can send eligible signature requests when **Automatic request emails** is on. | Through the resulting requests, or group reading access if signatures are off. |
| Publish a document with signatures off and include it in a group | No availability email. | Group members can open it in the signing portal. |

### Also send from an assign sheet

**Add Document** on a person and **Add People** on a document include **Also send a document request**, off by default. Turn it on to assign and send together. You can add a note when sending.

For documents that people should read without signing, follow [make documents available to read](/guides/read-documents).

## Automatic request emails

A group's **Automatic request emails** setting is on by default. Adding people or documents can create requests for newly active assignments to published documents that require a signature. The email follows within a minute.

It does not email documents available to read, publish drafts, or send a backlog just because the setting is turned on. See [group automation](/guides/manage-groups#automatic-request-emails) for setup and exceptions.

If people are assigned documents but still need requests, use **Send missing** on the group's **People** tab. To send missing requests for just one document, select it on the group's **Documents** tab and use **Send missing** in the side panel. See [send missing requests](/guides/manage-groups#send-missing-requests).

Use reminders for requests that are already pending.

## What recipients see

People receive a personal email link. They read the document, type their full name, confirm, and submit. A request deadline appears if expiry is enabled. After signing online, they can download a receipt.

They can also use the [signing portal](/guides/sign-document#use-the-signing-portal) to find pending requests and signed copies. The portal requires a one-time email code; the personal email link does not.

## Check the result

Open **Requests** to review status. It starts on **By person**. Switch to **By request** and use **Activity** on a request for its history, [reminders](/guides/reminders) for follow-up, or [delivery help](/guides/delivery-failures) if the email did not arrive.

Correcting a person's email updates their open requests and sends them again to the new address. Completed requests keep their original recipient details. See [correct an email address](/guides/delivery-failures#correct-an-email-address).


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