> ## 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 acknowledgment requests to people > Send attestation requests to one or more people, or an entire group, directly from any published document in ClearPolicy. Once a document is published, you can send requests to any of your people. Each recipient gets a personal email with a unique link — they don't need an account to complete the request. You can send to individual people or an entire group at once. New requests collect an electronic signature (typed name) so people can acknowledge the policy with an audit trail. Go to the **Documents** section and select the document you want to send. Make sure the document has a published revision before continuing. On the document page, click **Send request** or **Request signature** to open **Document request**. In **To**, search and check who should receive the request. Scroll the list to load more people as you go. Use **Select all people** to select everyone in your organization (when you are not searching), or **Select all matching people** when a search is active. You can uncheck individuals afterward if needed. You can send to at most 500 people in one send. To reach a larger roster, send in batches or use a [group](/concepts/people-groups). From a group, you can still send to the whole group (or use **Send missing**) without picking people one by one. Type an optional note in **Compose**. The note appears in the email your recipients receive and on the attestation page where they complete the request. For example, you might write: "Please review and acknowledge this policy before your next shift." If you are sending from a group that has a [default recipient message](/concepts/people-groups#groups), the note is pre-filled with that message. You can edit it before sending or remove it entirely. Open **Preview** to see the email before it goes out. Click **Send**. Each selected person receives a personal email containing a unique link to their attestation page. Links are individual — each recipient has their own private URL. ## Add a note to recipients A note to recipients is an optional message you can include when sending a request. It gives people context about why they are receiving the request and what you need them to do. Notes appear in two places: * **In the email** — directly in the notification email the recipient receives. * **On the attestation page** — displayed as a message from your organization when the recipient opens their personal link. You can type a note each time you send a request, or save time by setting a **default recipient message** on a group. When you send requests from that group, the note is pre-filled automatically. You can still edit or remove it before sending. Use **Preview** to see how the note looks in the email. To set a default recipient message on a group, open the group's **Settings** tab and fill in the **Default Recipient Message** field. You can also set it when you first create the group. Default recipient messages are especially useful for groups where you send the same type of request regularly. For example, a "New Volunteers" group might always include a message like "Welcome! Please review and sign this before your first volunteer day." ## Assigning vs sending a request Assigning a document to a person (or people to a document) does **not** email them. It only links the document so you can track compliance and send later. Assigning also does **not** make the document visible to the person. People only see a document after you send a signature request. There is no view-only list for employees, volunteers, or other people. The usual way to email a signing link is **Send request** on a published document, or **Send request** on a person's profile. ### Also send from an assign sheet When you use **Add Document** on a person or **Add People** on a document, you can optionally turn on **Also send a document request** (off by default). * Leave it off to assign only — no email goes out. * Turn it on to assign **and** send the same kind of document request as **Send request**. * When it is on, you can add an optional **Note** for the email (same idea as [Add a note to recipients](#add-a-note-to-recipients)). Leave the note blank to use the normal request email. * Unpublished documents cannot be sent until they have a published revision. Document **Send request** remains the primary path when you already know you want to email people. ## Automatic request emails Groups have an **Automatic request emails** setting that sends request emails automatically whenever you add people or documents to the group. This is turned on by default when you create a new group. When automatic request emails are on: * **Adding a person to the group** — ClearPolicy creates attestation requests for every published document assigned to the group and sends the person a single email with links to all of them. * **Adding a document to the group** — ClearPolicy creates attestation requests for every person in the group and sends each person an email for the newly assigned document. This means you don't need to manually send requests after updating a group's membership or documents — ClearPolicy handles it for you. If you assign groups from a person's or document's **Settings** tab, click **Save**. Automatic request emails go out when you save, not when you add the group to the list. ### Turn automatic request emails on or off You can toggle this setting in two places: * **When creating a group** — the **Automatic request emails** toggle appears in the group creation form. It is on by default. * **On an existing group** — open the group's **Settings** tab and find the **Automatic request emails** toggle under the **Automation** section. The group card on the **Groups** page shows an icon indicating whether automatic emails are on or off for each group. Turn off automatic request emails if you want to control exactly when requests go out — for example, if you're building a group ahead of time and plan to send all requests at once later. Automatic request emails only apply to published documents. If a document assigned to the group doesn't have a published revision yet, no request is created for that document until it is published and you send requests manually. ## What recipients see Recipients receive an email with a link to a public attestation page. No team member account is required. From that page, they can read the document and type their name to sign. If you included a note to recipients, it appears in the email and as a highlighted note on the attestation page. After completing the request online, they can download a receipt confirming their response. If [request expiry](/guides/request-expiry) is enabled, the email and attestation page both display the expiration deadline so the recipient knows when they need to complete the request. People can also open the [signing portal](/guides/signer-portal) with a one-time email code to see all pending and signed requests for that address—useful when they lost an email or have several documents waiting. You can also send requests from a person's profile. Open a person in the **People** section and click **Send request** in the header to choose a document and send a request to that person. Use Groups to send to many people at once without selecting them individually. Organize people into groups ahead of time to make bulk sending faster.