# Send an attestation request Source: https://docs.clearpolicy.app/api-reference/attestation-requests/send-an-attestation-request /api-reference/openapi.json post /attestation-requests Sends a published document to a person for electronic signature (typed name). New requests are always signature; historical rows may still show acknowledgment as a read-only type. A document that does not require a signature cannot be sent. That request returns 422. # List documents Source: https://docs.clearpolicy.app/api-reference/documents/list-documents /api-reference/openapi.json get /documents Returns a paginated list of documents in your organization. Supports filtering by name and archived status. # Add people to a group Source: https://docs.clearpolicy.app/api-reference/groups/add-people-to-a-group /api-reference/openapi.json post /groups/{group}/people Adds one or more active people to a group. People who are already members are accepted and returned without error. The response always uses status 200 and lists one membership object per requested person ID, in the same order as the request. Adding people may assign the group's documents to them. When the group has automatic request issuance enabled, ClearPolicy creates signature requests for newly assigned published documents and sends grouped notification emails asynchronously. # List groups Source: https://docs.clearpolicy.app/api-reference/groups/list-groups /api-reference/openapi.json get /groups Returns a paginated list of groups in your organization, ordered by name ascending. # Remove a person from a group Source: https://docs.clearpolicy.app/api-reference/groups/remove-a-person-from-a-group /api-reference/openapi.json delete /groups/{group}/people/{person} Removes one person from a group. The person must already be a member; otherwise the API returns 404. Document assignments created earlier via the group are not automatically removed. # Get current user Source: https://docs.clearpolicy.app/api-reference/me/get-current-user /api-reference/openapi.json get /me Returns the authenticated user and their current organization. # Add a person Source: https://docs.clearpolicy.app/api-reference/people/add-a-person /api-reference/openapi.json post /people Adds a person to your organization. Provide last_name and email; first_name and phone are optional. This does not send a team invitation or a document request. # Get a person Source: https://docs.clearpolicy.app/api-reference/people/get-a-person /api-reference/openapi.json get /people/{id} Returns a single person by their ULID. # List people Source: https://docs.clearpolicy.app/api-reference/people/list-people /api-reference/openapi.json get /people Returns a paginated list of people in your organization. Supports filtering by name, email, phone, and archived status. # Create and use an API token Source: https://docs.clearpolicy.app/api/authentication Authenticate REST API requests with an organization-scoped API token and revoke tokens that no longer need access. The REST API uses **API tokens** sent as bearer tokens. A token is tied to the organization selected when it was issued; changing your organization in the app does not retarget that token. Owners and administrators can create and manage API tokens. The organization needs an active trial or subscription to use the REST API. ## Create an API token 1. Select the organization to connect. 2. Open **Settings → API**. 3. Click **Create API Token** and give it a descriptive name, such as `Reporting automation`. 4. Copy the token when shown. You cannot view the full token again after closing the dialog. 5. Store it in a password manager, secrets manager, or your integration's protected settings. Do not share tokens in email, support chat, or public code. If token setup fails, [contact support](/guides/get-support) with the error, not the token. ## Pass the token in requests Send `Authorization: Bearer YOUR_API_TOKEN` and request JSON responses: ```bash theme={null} curl 'https://api.clearpolicy.app/api/v1/me' \ -H 'Authorization: Bearer YOUR_API_TOKEN' \ -H 'Accept: application/json' ``` Use `GET /me` to confirm the token's organization before sending requests or changing group membership. ## Access by role The token follows the team member's role. Owners and administrators can use the people, groups, documents, and request endpoints. A token tied to a Group Manager can use `GET /me`, but organization-wide REST endpoints return `403 Forbidden`. ## Error responses | Status | Check | | - | - | | `401 Unauthorized` | The token is present, correct, unexpired, and not revoked. | | `402 Payment Required` | The token's organization has an active trial or subscription. | | `403 Forbidden` | The team member and token have permission for the endpoint. | See [API errors](/api/overview#errors) for other responses. ## Revoke a token Open **Settings → API** to see active tokens, who issued them, their expiry, and last use. Click **Revoke** when a token is no longer needed or may have been exposed. Update integrations to use a replacement token before revoking one they still need. ## Zapier and AI connections [Zapier](/integrations/zapier) and [ChatGPT or Claude](/integrations/mcp) use OAuth sign-in and consent instead of this API-token setup. # REST API overview Source: https://docs.clearpolicy.app/api/overview Use the ClearPolicy REST API for people, groups, documents, and signature requests. Review access, pagination, errors, and rate limits. The ClearPolicy REST API returns JSON over HTTPS. It supports listing and adding people, listing documents and groups, changing group membership, and sending document requests. ## Base URL ```text theme={null} https://api.clearpolicy.app/api/v1 ``` Include `/api/v1` in every request. The supported version is `v1`. ## Authentication [Create an API token](/api/authentication) and send it in the `Authorization` header. Include `Accept: application/json`, and `Content-Type: application/json` when sending JSON. All REST endpoints require an active trial or subscription for the token's organization. Without it, requests return `402 Payment Required`. ## Access by role Owners and administrators can use the REST endpoints. A token tied to a Group Manager can confirm its identity and organization through `GET /me`; other REST endpoints return `403 Forbidden`. Tokens are organization-scoped. Use IDs from the same organization as the token. ## Supported endpoints | Method and path | Purpose | | - | - | | `GET /me` | Confirm the authenticated account and organization. | | `GET /people` | List or search people. | | `POST /people` | Add a person. | | `GET /people/{id}` | Read a person. | | `GET /documents` | List documents. | | `GET /groups` | List groups. | | `POST /groups/{group}/people` | Add people to a group. | | `DELETE /groups/{group}/people/{person}` | Remove a person's group membership. | | `POST /attestation-requests` | Send a document request. | Use the endpoint pages in **API Reference** for request and response fields. ## Sending a document request Provide a `person_id` and `document_id` from the connected organization. The document must be published and require a signature. New requests collect typed-name signatures; historical responses can still contain acknowledgment values. Sending a document with `requires_signature: false` returns `422`. Change the setting in the app if a signature is needed. The REST API does not change that setting. Adding group membership can also send requests when automatic group emails are enabled. See [group behavior](/guides/manage-groups#automatic-request-emails). ## Response format Single-resource responses contain that resource's fields. Paginated lists have `data`, `links`, and `meta`. Check the endpoint reference for non-paginated variants, such as filtering people by an exact ID. ## IDs Resource IDs are lowercase ULID strings, such as `01kg82xqfx6fvr046d15hnfmjv`. Treat them as strings, not numbers. ## Pagination Use `page` and `per_page`. Page size defaults to **25**, with a maximum of **100**. Paginated responses provide the current page in `meta.current_page` and the next-page URL in `links.next`. Continue until `links.next` is `null`. For people and documents, `archived=true` selects only archived records; omitting it selects active records. It does not combine active and archived results. ## Errors | Status | Meaning and recovery | | - | - | | `400 Bad Request` | The action cannot be completed, such as sending an unpublished document. Correct the document or request. | | `401 Unauthorized` | Token missing, invalid, expired, or revoked. | | `402 Payment Required` | Update the organization's billing access. | | `403 Forbidden` | Check role and token permissions. | | `404 Not Found` | The resource is unavailable in the token's organization. | | `422 Unprocessable Entity` | Invalid fields or an unsupported action, such as requesting a signature on a document with signatures off. | | `429 Too Many Requests` | Wait for `Retry-After`, then retry. | Some action errors use an `error` field. Validation errors can use `message` and field-specific `errors`. Handle the HTTP status and the returned body rather than assuming every error has the same shape. ```json theme={null} { "message": "The email field is required.", "errors": { "email": ["The email field is required."] } } ``` ## Rate limiting Each API token is limited to **60 requests per minute**. Inspect `X-RateLimit-*` headers and respect `Retry-After` on a `429` response. Use backoff when retrying. # Changelog Source: https://docs.clearpolicy.app/changelog Product updates in ClearPolicy — new features and improvements for your organization. Product updates for documents, people, and signatures. Entries describe each release; use the [current guides](/introduction) for today's steps and settings. **October 2026** Browser completion alerts, draft review, approvals, and discussion before publication ## Browser completion alerts **Instant notifications** is now **Instant completion notifications**, with separate **Email** and **Browser** switches for each organization. Choose either channel or both when people complete your requests. Browser alerts are off by default. Turn on **Browser** to allow notifications when prompted and set up this browser, then click **Save**. Browser alerts do not require an open ClearPolicy tab. Daily digests, delivery-failure alerts, and product updates remain email-only. [Choose your notifications](/guides/notification-settings) ## Draft review and approvals Add **Reviewers** for feedback before publishing a draft. Reviewers can comment or approve. New drafts do not require approval: add a reviewer, then turn on **Require approval before publishing** when everyone must approve the latest content. Changing the content invalidates earlier approvals and requires a new review request. Use **Discussion** in the revision sidebar for comments and review activity. The review record remains available after publication. Approvals do not publish the document or send signature requests. [Review and approve a draft](/guides/review-document) **September 2026** Send several documents in one signature request, documents people can read without signing, requests grouped by person, reset trial data, organization logo, signing portal address ## Requests grouped by person **Requests** starts on **By person**. Each row is a person with their matching requests. Open the row to review those requests and send a reminder. **By request** is the list of individual requests. ClearPolicy remembers the view you last chose. [Manage requests](/guides/manage-requests) ## Several documents in one signature request **Send request** opens a window titled **Signature request**. Select people and up to 20 published documents. Each person gets one email listing those documents. With one document, you can still send to 500 people. Choosing more documents means fewer people in that same send. Starting from a document keeps that document selected. [Send requests](/guides/send-requests) ## Documents people can read without signing **Requires a signature** stays on unless you turn it off. When it is off, people in a group that includes the published document can open it in the signing portal. They are not asked to sign, and they are not emailed that it is available. The documents list shows **Available to read**. [Make documents available to read](/guides/read-documents) · [Signing portal](/guides/signer-portal) ## Reset trial data During a free trial, an owner can permanently delete people, documents, groups, document requests, and signature records from **Settings → Organization → Profile** and keep the organization. This does not change when your trial ends. After you subscribe, this action is gone. [Reset trial data](/guides/reset-trial-data) ## Document request and Nudge composers Sending a request and nudging a reminder now use the same compose window. Choose people and a document (when sending), type an optional note, and open **Preview** to see the email before you click **Send**. On a pending document row (including a person's **Documents** tab), **Nudge** still sends a reminder right away. Open the menu next to **Nudge** for **Nudge with note…**. Bulk **Nudge** on **Requests** uses the same composer. [Send requests](/guides/send-requests) · [Reminders](/guides/reminders) ## Organization logo Upload a logo in **Settings → Organization → Branding** so people recognize your organization on signature request emails, the signing page, and the signing portal. Choose **Show as icon** or **Show full width**. The ClearPolicy name stays on each. [Add your organization logo](/guides/organization-logo) ## Signing portal address The signing portal now lives at [go.clearpolicy.app](https://go.clearpolicy.app). Request emails use the new link. Old signing links redirect. The one-time code flow is unchanged. [How people use the signing portal](/guides/signer-portal) ## Assign documents from a sheet On a person's **Documents** tab, **Add Document** opens a sheet where you can search and select documents. Assigning does not send a request by default. Use **Send request** or **Request signature** when you are ready to email them. On a group's **Documents** tab, **Add Documents** uses the same sheet. If **Automatic request emails** is on, eligible new assignments to a published document that requires a signature send requests. Documents **Available to read** are not emailed. ## Also send a document request when assigning On **Add Document** (person) and **Add People** (document), you can optionally turn on **Also send a document request** (off by default). That assigns and sends the usual document request in one step, with an optional note for the email. Unpublished documents cannot be sent. Document **Send request** remains the primary send path. [Send requests](/guides/send-requests#assigning-vs-sending-a-request) · [Track compliance](/guides/track-compliance) **August 2026** Select all, nudge with note, signing portal ## Select all when sending requests When sending a document request, use **Select all people** (or **Select all matching people** while searching) to select a large roster quickly. The people list loads more as you scroll. You can send to at most 500 people in one send. [Send requests](/guides/send-requests) ## Nudge with note When you follow up on outstanding requests, you can refresh the note to recipients and send a reminder without creating a new request. * On a request row, click **Nudge** for an immediate reminder, or open the menu and choose **Nudge with note…** * On bulk **Nudge**, you can add a note that applies to every request in that nudge * A new note replaces the previous note on those requests, then ClearPolicy sends the usual reminder (same personal link) [Send reminders](/guides/reminders) · [Manage requests](/guides/manage-requests) ## Signing portal People can open the **signing portal** with a one-time email code—no team member account—to see pending and signed document requests for that address, including across more than one organization. * Enter email at [app.clearpolicy.app/signer](https://app.clearpolicy.app/signer), or choose **Here to sign a document?** on the team log in and register pages * **Sign** opens the same attestation experience as the personal email link * **View document** reopens completed requests, including after the original deadline has passed * Personal request links still work without a code [How people use the signing portal](/guides/signer-portal) **July 2026** Paper, reminders, and imports ## Paper on file When someone cannot finish online, a team member can upload the signed paper copy on the request so status and evidence stay in ClearPolicy. [Record paper on file](/guides/record-paper-signature) ## Smart Follow-up Automatic reminders adapt based on whether the person opened the request and whether a deadline is approaching—so follow-ups go out when they are more likely to help. [Send reminders](/guides/reminders) ## OneDrive import Import Word documents and PDFs from Microsoft OneDrive when you create a document or replace a draft—personal and work accounts. [Add a document](/guides/create-document) · [Microsoft OneDrive](/integrations/microsoft) ## Quick search Press **⌘K** (or **Ctrl+K**) to find people, documents, and groups, jump to a page, or start a new document without leaving where you are. # Understand signatures and completion records Source: https://docs.clearpolicy.app/concepts/attestations Learn what an attestation records, how requests stay linked to document versions, and how online and paper completions differ. An **attestation** is the completion record for a document request. New online requests collect a typed-name electronic signature. The record stays linked to the document revision the person signed. ## How recipients complete a request The person opens their personal email link, reads the document, types their name, and confirms the electronic signature. They do not need a team member account. Historical records may show an **acknowledgment** completed without a typed name. Those records remain in history. There is no separate acknowledgment-only mode for new requests. See [sign a document](/guides/sign-document) for the person's steps. ## How requests are sent A request links one person to one document revision. Emails and reminders use the name and email saved on that request. Changing a person's name or email updates open requests without sending email. An email change also replaces their personal request links; earlier links for those open requests stop working. Retry delivery or send a reminder when needed. Completed requests keep their original recipient details. Personal links grant access to the request. People should use their own link and not forward it for someone else to sign. ## The recipient experience The signing page shows the document, your optional note, and a deadline when request expiry is enabled. After an online completion, it offers a receipt. Other pending requests may appear so the person can continue signing. ### Finding requests without the email link People can enter their email and a one-time code in the [signing portal](/guides/sign-document#use-the-signing-portal). It shows their pending requests, signed copies, and documents made available to read through groups. ## What gets recorded An online completion records: * The completion date and time. * The typed signature name for new requests. * The IP address and browser information. * The specific document revision and its hash, a fingerprint used to identify the content. These details support the electronic certificate and request history. A signature records a completion; it does not establish whether someone follows the policy in practice. ## Request lifecycle A request can be sent, viewed, completed, canceled, or expired. Email delivery events show whether a message was delivered, bounced, failed, or marked as spam. Sending and delivery are separate events; a sent request is not proof that the email reached an inbox. Use [Requests](/guides/manage-requests) for request status and [completion statuses](/concepts/compliance) for whether a person's documents are current. ## Superseded requests Publishing a new revision does not change open requests. They still refer to the version originally sent. When you send a new request for the same person and document, pending requests for older revisions are canceled. The activity explains that they were superseded by a newer revision. Completed, expired, and previously canceled requests are preserved. See [update a document](/guides/update-document). ## Sending reminders A reminder uses the same request link, version, and deadline. It does not create a new request. See [send reminders](/guides/reminders). ## Paper on file A team member can complete a pending request by recording a paper signature and uploading the signed paper copy. This records paper evidence; it is not an electronic signature captured in ClearPolicy. | | Online completion | Paper on file | | - | - | - | | Who completes it | The person signs online | A team member records the collected paper signature | | Evidence | Electronic signature details and document version | Uploaded signed paper copy, recording time, and team member | | Download | **Download signed document** | **Download uploaded file** | | Electronic certificate | Included | Not generated | Both count as completion for the relevant revision. See [record a paper signature](/guides/record-paper-signature). ## Downloadable receipts Use [download records](/guides/download-records) for signed documents, electronic certificates, paper evidence, and printed activity. # Understand completion statuses Source: https://docs.clearpolicy.app/concepts/compliance Distinguish document completion, person status, request activity, and delivery status so you know what to do next. ClearPolicy's compliance views track whether people have completed their assigned documents on the current published version and whether renewal is due. They do not measure legal compliance or whether people follow a policy in practice. ## What compliance metrics mean Only the people and required documents you track in ClearPolicy contribute to these views. Documents **Available to read** do not require a signature and do not record opening activity. Online signatures and paper on file both count as completion for the relevant revision. Historical acknowledgments remain part of the record. ## Compliance statuses Document status answers: **What does this person need to do for this document now?** | Status | Meaning | Next step | | - | - | - | | **Signed** or **Acknowledged** | Completed on the current revision and not due for renewal. | No new signature needed. Download the record if needed. | | **Pending signature** | A request for the current revision is open. | Send a reminder or resolve delivery problems. | | **Outdated** | The latest completion covers an older revision. | Send the current revision. | | **Renewal due** | The renewal interval has passed since completion. | Send another request, or use Auto-renew. | | **Unrequested** | No current completion or pending request satisfies the assignment. | Publish if needed, then send a request. | A completed request stays completed even when its document becomes outdated or due for renewal. These are different views of the same history. ## Person statuses Person status summarizes current assignments: | Status | Meaning | | - | - | | **Compliant** | All current assignments are complete and current. | | **Pending** | At least one assignment has an open request, with no unrequested, outdated, or renewal-due assignment taking priority. | | **Needs Attention** | At least one assignment is unrequested, outdated, or renewal due. Other requests may also be pending. | | **Not Started** | No current document assignments contribute to the person's status. | Open the person's **Documents** tab to see the underlying document statuses rather than relying only on the summary. ## Request and delivery statuses A request's status describes its own lifecycle: sent, viewed, completed, canceled, or expired. A new revision does not rewrite that request's history. Email delivery is separate. **Bounced**, **Delivery failed**, and **Complained** flag requests that need delivery follow-up. “Sent” does not guarantee inbox delivery, and “Viewed” does not mean signed. See [manage requests](/guides/manage-requests) and [delivery failures](/guides/delivery-failures). ## Compliance progress indicators Document and person workspace progress counts current assignments only. Previous assignments remain available for history but do not contribute to current progress. Group views use that group's scope. Outstanding requests and assignment progress answer different questions. A person can have no open requests and still need a first signature, an updated revision, or a renewal. Progress bars are red below 50%, yellow from 50% to 79%, and green from 80%. A green bar can still include unfinished work; read the count or percentage. The dashboard's person-based completion score and a document's signature count measure different things. ## Per-document compliance view Use **Documents → Compliance** to find people who need a particular document. See [track completion](/guides/track-compliance#document-compliance-view). ## Per-person compliance view Use **People → Documents** to review a person's current and previous assignments. See [person details](/guides/track-compliance#person-detail-view). ## Activity history Open **Activity** on a request for its timeline. The organization-wide [Activity page](/guides/activity-feed) provides a broader history. ## Downloading receipts and audit trails Use [download records](/guides/download-records) for electronic certificates, paper evidence, and printed timelines. ## After publishing a revision Publishing a new revision makes earlier completions outdated for current-version tracking. It does not send replacement requests or cancel pending ones by itself. See [update a document](/guides/update-document). Scheduled renewal is a separate setting. Use [recurring renewals](/guides/renewals) when people should sign again after an interval even without a content change. ## Compliance is scoped to your organization Completion views reflect your selected organization. Group Managers see their assigned groups; owners and administrators can review organization-wide results. # Understand documents and revisions Source: https://docs.clearpolicy.app/concepts/documents Learn how document settings, published revisions, signature requests, and reading access fit together. A **document** holds its name, settings, and history. A **revision** is one version of its content. Keep the same document when you update a policy so its earlier versions and completions stay together. ## Document tabs and settings Open a document to start on **Workspace**. | Tab | Use it for | | - | - | | **Workspace** | Document details, outstanding requests, delivery follow-up, reading access, and recent activity. | | **Compliance** | Signature assignments, completion status, request actions, and previous assignments. | | **Revisions** | Drafts, approvals, discussion, published versions, previews, and file downloads. | **Compliance** appears when the document requires signatures or has signature history. If signatures are off, past records remain under **Previously assigned**. Click **Edit** beside the workspace details, or open the three-dot menu and choose **Edit settings**. Change the name, **Requires a signature**, groups, or renewal settings, then click **Save changes**. Archive and delete actions are in the three-dot menu. ### Follow up from the workspace For a published document requiring signatures, **Outstanding requests** shows open requests. Select a row to review that request's details and activity. Use **View compliance** to review assignments and decide who needs a new request. No outstanding requests does not mean everyone is up to date. Some people may still need their first request, the latest revision, or a renewal. For documents **Available to read**, the workspace shows group access instead of signature progress. Publish a revision and add a group before people can read it. Opening the document is not recorded. If the document has unpublished changes, the current published version remains available. Use **Finish draft** to continue editing. ## Requires a signature **Requires a signature** is on by default. | Setting | How people get access | What is recorded | | - | - | - | | On | Send a document request. The person opens their email link or signing portal. | Request activity and the completed signature. | | Off | Publish the document and add it to a group. People in that group open it in the signing portal. | No signature or record of opening the document. | With signatures off, the document is **Available to read**. No availability email is sent. Turning signatures off ends current signature assignments and cancels pending requests; completed records remain. Turning signatures on assigns current group members. The app asks for confirmation before sending eligible automatic group requests. See [make documents available to read](/guides/read-documents) for the full setup and switching behavior. ## What is a revision? A revision is either a **Draft** or **Published**. A draft is work in progress. Publishing makes that version available for requests or reading access. You can have one open draft per document. Published content cannot be edited in place. Add a new draft when you need to change it. Every request stays linked to the revision sent. A later update does not rewrite a signed document or its completion record. ## Adding a document Use **Documents → Add Document** to upload a PDF or Word file, import from Google Drive or OneDrive, or write in ClearPolicy. New file uploads and cloud imports publish on submission; content written in the editor starts as a draft. See [add and publish a document](/guides/create-document). ## Publishing a revision [Ask reviewers for feedback on a draft](/guides/review-document). Adding reviewers does not block publishing. Turn on **Require approval before publishing** to require every listed reviewer to approve the latest content. Changing the content invalidates earlier approvals. Discussion and review activity stay with the revision and become read-only after publishing. Publishing makes the revision current. It does not send requests by itself. Send requests after publishing when people need to sign the new version. For documents available to read, people with group access see the current published file. They do not receive an email when it changes. ## Updating content with a new revision Use **Revisions → New Draft**, update the content, and publish. Earlier completions remain in history but can become **Outdated** for current completion tracking. Publishing does not cancel pending requests for older revisions. Sending a new request for the same person and document cancels their pending requests for older revisions. See [update a document](/guides/update-document). ## Downloading a published document From **Revisions**, select a published revision and download its PDF. This is the document content. For a person's completed document and certificate, use [completion downloads](/guides/download-records). ## Archive a document Open the document's three-dot menu and choose **Archive**, then confirm. Archiving cancels open requests, ends current assignments, removes group links, and stops reading access. Completed records and revision history remain available. The workspace no longer shows current signature progress. Choose **Unarchive** to use the document again. Reassign groups or people and send new requests as needed; canceled requests do not reopen. # Understand people, team members, and groups Source: https://docs.clearpolicy.app/concepts/people-groups Choose whether someone needs to receive documents, manage your organization, or belong to a group. Add a **person** when someone needs your documents. Invite a **team member** when someone needs to work inside ClearPolicy. Use a **group** when several people need the same documents. ## People A person has a name and email address, with an optional phone number. They use personal email links or the signing portal to sign and read documents. They do not need a team member account or password. Adding a person alone sends no email. Adding that person to a group can create signature requests if the group has **Automatic request emails** on and published documents that require a signature. The email follows within a minute. See [manage people](/guides/manage-people) or [import people](/guides/import-people). ## Team members Team members sign in to manage the organization. Their role determines what they can see and change: **Owner**, **Administrator**, or **Group Manager**. A team invitation is separate from a document request. If a colleague needs both management access and documents to sign, they can be both a team member and a person. See [invite and manage team members](/guides/add-team-members). ## Groups A group collects people who need the same documents, such as **All staff**, **Volunteer drivers**, or **Board members**. Groups have two document uses: | Document setting | What group membership does | | - | - | | **Requires a signature** on | Assigns the document for completion tracking. Automatic request emails can also send the signing request. | | **Requires a signature** off | Lets people read the published document in the signing portal. No request or availability email is sent. | Removing someone from a group removes read access granted by that group. Access remains if another group still grants it. Existing signature assignments are not automatically removed when someone leaves a group. See [create and manage groups](/guides/manage-groups) for setup, automatic emails, default messages, and membership changes. ## Group Managers A **Group Manager** is a team member assigned to oversee particular groups. They can review those groups, send missing requests, send reminders, and view request activity. They cannot manage people, documents, group setup, billing, or organization settings. They do not have the organization-wide dashboard or reports. An owner or administrator must assign their groups. See [team roles](/guides/add-team-members#choose-a-role). ## Source tracking People can be added manually, imported from CSV, brought in from Planning Center, or added through an integration. ClearPolicy records their source so your team can identify how they were added. ## Filter group members by status Open the group's **People** tab and select a status to find people who still need to sign. Select a person to review their required documents in **Group compliance**. See [track completion in groups](/guides/track-compliance#group-compliance-view) and [understand statuses](/concepts/compliance). ## Compliance progress within groups Group progress counts only the people and required documents in that group. A person may be up to date in one group but still need to sign documents in another. Documents **Available to read** do not require a signature. To check one document, open the group's **Documents** tab and select a published document under **Requires a signature**. **Group compliance** shows who has signed and who still needs to sign. ## Viewing a member's document details In a person's **Group compliance** panel, expand a document to review its activity. Use **Send request** beside a document when a new signature is needed. **Nudge** at the bottom reminds that person's eligible pending requests in the group. # Manage your account and sign-in security Source: https://docs.clearpolicy.app/guides/account-security Update your personal profile and language, change your password, add passkeys, and set up two-factor authentication. **Account** settings apply to you as a team member. **Organization** settings apply to the selected organization. People signing documents use [email links or one-time codes](/guides/sign-document) instead of these team member settings. ## Update your profile 1. Open **Settings → Account → Profile**. 2. Update your name, email, or preferred language under **Account information**. 3. Click **Save** and complete any email verification requested. Changing your preferred language changes your app interface. The organization's language controls request emails and signing pages; see [organization language and time zone](/guides/timezone). ## Change your password Open **Settings → Account → Security**. In **Update password**, enter your current password, your new password, and its confirmation. Click **Save password**. If you cannot sign in, use the password-reset option on the login page. If you normally sign in through Google or Microsoft, try that same sign-in method. [Contact support](/guides/get-support) if you still cannot access your account. ## Add a passkey Passkeys let you sign in with Face ID, Touch ID, Windows Hello, or a security key. 1. Open **Settings → Account → Security**. 2. Under **Passkeys**, click **Add passkey**. 3. Give it a name and follow your device or browser's setup prompt. A passkey replaces the password step. ClearPolicy does not ask for an additional authenticator code when you sign in with a passkey. ## Enable two-factor authentication 1. Open **Settings → Account → Security**. 2. Under **Two-Factor Authentication**, click **Enable 2FA**. 3. Scan the QR code with your authenticator app or enter the setup key. 4. Complete the confirmation prompts. 5. Save your recovery codes somewhere you can access if you lose your device. Use a recovery code if you cannot access your authenticator. If you lose both, contact support for account-access help. ## Require stronger sign-in for your organization An owner can open **Settings → Organization → Profile**, turn on **Require two-factor authentication**, and save. Team members must use an authenticator app or a passkey to meet the requirement. This applies to team member access, not people completing document requests. # Review organization activity Source: https://docs.clearpolicy.app/guides/activity-feed Find when documents were requested, emails were delivered, people signed, and assignments or groups changed. Use **Activity** to understand what happened across the organization. Use **Requests** when you need to act on unfinished requests. ## Open and filter activity 1. Open **Activity** in the sidebar. 2. Choose a date range: the last 24 hours, 7 days, 30 days, or a custom range. 3. Filter by person, document, or event type when you need a narrower view. 4. Follow a related person or document link for more detail. Items are grouped by date and show their time and summary. The sidebar can show an unread activity count. ## Start from a person or document On a person's or document's **Workspace**, review **Recent activity** and click **View activity**. The Activity page opens with that person or document selected and a date range from when it was added through today. Adjust the date range or combine person, document, and event filters to narrow the history. Clear the person or document filter to broaden the view. ## Events you can review * Requests sent, viewed, completed, canceled, or expired. * Reminders sent manually or automatically. * Email delivery, bounces, failures, and spam complaints. * **Paper Signature Recorded** when a team member uploads paper evidence. * Document assignments added or removed. * Changes to **Requires a signature**. * People or documents added to or removed from groups. * People added or updated. An email delivery event and a document-view event mean different things. Neither is a signature. Opening a document **Available to read** is not recorded. ## Review one request's history Select a row under **Outstanding requests** on a person or document workspace. You can also open **Activity** from a request's actions. The side panel follows that request from sending through completion or closure. Use its print view when you need a copy. Closely repeated views can be grouped in the printed timeline. See [download records](/guides/download-records). # Invite and manage team members Source: https://docs.clearpolicy.app/guides/add-team-members Give colleagues access to ClearPolicy, choose their roles, assign Group Managers, and manage invitations or ownership. Invite a **team member** when someone needs to sign in and manage work in your organization. Add a [person](/guides/manage-people) when someone needs to receive documents. These are separate roles. ## Choose a role | Role | Access | | - | - | | **Owner** | Full organization access, including ownership transfer, administrator appointments, and Planning Center sync management. | | **Administrator** | Manages people, documents, groups, requests, reports, settings, and billing. Can invite and assign Group Managers. | | **Group Manager** | Reviews assigned groups, sends missing requests, sends reminders, and handles request follow-up within those groups. | Group Managers cannot create or edit people, documents, or groups. They do not have organization-wide dashboard, people, documents, requests, reports, billing, or team-management access. Only an owner can invite or assign an **Administrator**. Owners and administrators can invite **Group Managers**. ## Invite a team member 1. Open **Settings → Team members**. 2. In **Invite by email**, enter their sign-in email. 3. Choose **Administrator** or **Group Manager**. 4. For a Group Manager, select the groups they should oversee. 5. Click **Send invite**. The person receives a team invitation. They must accept using the same email address. Their role and group access apply after acceptance. ## Manage pending invitations Review pending invitations on **Settings → Team members**. Use the invitation actions to resend it or cancel an invitation that is no longer needed. Invitations expire after **7 days** and cannot be accepted twice. If an invitation cannot be accepted, check its status and the email used to sign in. Do not send another invitation to someone who is already a member. ## Update a member's role or groups 1. On **Team members**, open the member's actions menu. 2. Choose **Manage membership**. 3. Update the role or assigned groups, within your permissions. 4. Click **Save changes**. You can also assign Group Managers from a group's **Settings**. Team members cannot change their own role. ## Transfer organization ownership Only the current owner can transfer ownership to an existing **Administrator**. 1. Invite the person and make them an administrator first, if needed. 2. Open their **Manage membership** dialog. 3. Choose **Owner**. 4. Review the confirmation and save. The selected administrator becomes the owner. The previous owner becomes an administrator. If the current owner cannot sign in, [contact support](/guides/get-support) for account-access help. ## Remove a team member Use the member's removal action on **Team members** when they no longer need management access. Available actions depend on your role; the last owner cannot be removed or downgraded. Removing team access is different from [archiving a person](/guides/manage-people#archive-or-unarchive-a-person) who receives documents. ## Common issues ### I added someone on People, but they did not get a login email Adding a person does not send a team invitation. Invite them from **Settings → Team members** if they need management access. If they only need to sign, send a document request instead; no team account is needed. ### A Group Manager cannot see a group An owner or administrator needs to assign that group to them. Check **Manage membership** or the group's **Settings**. ### I cannot invite an administrator or owner Only owners can assign administrators. Owner is not an invitation option: invite an administrator, wait for acceptance, then transfer ownership. # Run and export completion reports Source: https://docs.clearpolicy.app/guides/compliance-reports Review outstanding people, document completion, or group progress, then print the results or export them to CSV. Use **Reports** to prepare a summary for your team, leadership, or a review. Reports summarize completion in ClearPolicy; they do not establish legal compliance. **Who can use Reports:** owners and administrators. Group Managers review progress inside assigned groups instead. ## Choose a report | Report | Best for | | - | - | | **Outstanding People** | Finding people with pending requests, outdated completions, renewal due, or unrequested documents. | | **Document Compliance** | Reviewing completion for one document or all documents. | | **Group Compliance** | Reviewing people against required documents in one group. | ## Outstanding People report 1. Open **Reports → Outstanding People**. 2. Filter by status, group, document, or search. 3. Expand a person to see which documents need action. 4. Review reminder activity or open a request's activity to decide on follow-up. ## Document compliance report 1. Open **Reports → Document Compliance**. 2. Select a document or **All Documents**. 3. Filter by status or search for a person. Results show document completion, last completion dates, and renewal dates where applicable. An all-documents export includes the document name. ## Group compliance report Open **Reports → Group Compliance**, select a group, and filter by status. Review each person's overall result and their per-document statuses within that group. ## Single-person compliance report Open **People**, select a person, and click **Print** on their **Documents** tab. The report includes document statuses, completion progress, average response time, and request history. ## Print a report Click **Print** to open a print-ready view. Use your browser's print options to print or save as PDF. The report includes matching results without pagination, plus the organization and generation details. ## Export to CSV Click **Export CSV** on an organization report to download all results matching your current filters, not just the visible page. * **Outstanding People:** people and their outstanding documents. * **Document Compliance:** person, document where relevant, status, last completion, and renewal due. * **Group Compliance:** person, overall status, and per-document statuses. Check the selected group, document, and status filters before sharing the export. ## Need the signed document itself? A report is a summary. For a person's signed document and certificate, or uploaded paper evidence, use [download records](/guides/download-records). # Add and publish a document Source: https://docs.clearpolicy.app/guides/create-document Upload a PDF or Word document, import from Google Drive or OneDrive, or write in ClearPolicy. Choose whether people need to sign. Add a document before you send requests or make it available to read. A published revision is required for both. **Who can do this:** owners and administrators. ## Upload a PDF or Word document 1. Open **Documents** and click **Add Document**. 2. Drop a file or choose one from your computer. PDF, `.doc`, and `.docx` files are supported, up to **25 MB**. 3. Check the document name. 4. Leave **Requires a signature** on if people need to sign. Turn it off if they only need to read. 5. Submit the form. ClearPolicy converts Word files to PDF and publishes the first revision. Open **Revisions** to review the published file before sending it. ## Import from Google Drive or OneDrive In **Add Document**, click **More options**, then choose **Pick from Google Drive** or **Pick from OneDrive**. Connect the service if prompted, select a supported file, check the name and signature setting, then submit. Like a local upload, a new cloud import is published when added. Imports are copies: later changes in Drive or OneDrive do not automatically update ClearPolicy. See [Google Drive import](/integrations/google) or [OneDrive import](/integrations/microsoft) for supported types and connection help. ## Write in ClearPolicy 1. In **Add Document → More options**, choose **Write in ClearPolicy**. 2. Enter a name and choose whether the document requires a signature. 3. Submit to open the draft editor. 4. Write and format your document. The editor saves automatically; wait for saving to finish. 5. To get feedback, [request review](/guides/review-document). Turn on **Require approval before publishing** if approval is required. 6. Click **Publish** when it is ready. If approval is required, every reviewer must approve the latest content first. Drafts are not visible to people and cannot be sent for signature. ## Choose what happens next | Your goal | Next step | | - | - | | Review a draft with other team members | [Request review and discuss changes](/guides/review-document). Review applies to drafts, not the first publication of a new upload or cloud import. | | Ask people to sign | [Send a document request](/guides/send-requests). Publishing alone does not send it. | | Let people read without signing | [Add the published document to a group](/guides/read-documents) with **Requires a signature** off. | | Change published content | [Add a new revision](/guides/update-document). | | Ask people to sign again periodically | [Set up renewal](/guides/renewals). | ## Find document settings and history Open a document to start on **Workspace**. Review its details, outstanding requests, delivery issues, and recent activity. Click **Edit** beside the details, or choose **Edit settings** from the three-dot menu, to change the name, signature requirement, groups, or renewal settings. Click **Save changes** when finished. Archive and delete actions are in the three-dot menu. Use **Compliance** for signature assignments and completion history. Use **Revisions** for content, published versions, and downloads. See [documents and revisions](/concepts/documents). # Use the dashboard Source: https://docs.clearpolicy.app/guides/dashboard Send your first document request, review follow-up work, and track completion across people, groups, and documents. Open **Dashboard** to see what needs your attention across your organization. Owners and administrators use this page. Group Managers work inside their assigned groups instead. ## Send your first request Before your organization sends its first request, the dashboard shows the next setup step: 1. **Add Document:** add a document that requires a signature. If you need to publish a revision or change the document's settings, choose **Review documents**. 2. **Add Person** or **Import people:** add the people who need the document. Groups are optional. 3. **Review first request:** choose the recipients and documents, preview the email, and confirm sending. Nothing is sent until you confirm. People can complete requests without creating a team member account. See [send your first document request](/quickstart) for the full walkthrough. Owners can choose **Open the setup guide** for the optional guided setup. If a setup action is unavailable, the dashboard tells you to ask an organization owner for help. ## Follow up After you start sending requests, **Follow up** highlights work you can review: | Item | What to do | | - | - | | **Delivery failed** | Open the matching requests and [review delivery details](/guides/delivery-failures) before following up. | | **Not viewed yet** | Open requests whose signing link has not been viewed. Check sent dates and [reminders](/guides/reminders) before sending another reminder. | | **Requests needed** | Open people who need requests for required documents, updated versions, or renewals. Review their documents before sending. | Only items with outstanding work appear. Select a row to open the matching filtered view. **No follow-up items right now** means these follow-up lists are clear. It does not mean every request is complete: someone may have viewed a request but still need to sign. Use the outstanding request count to review open requests. When people have no documents assigned, **View people with no documents assigned** helps you find them. ## People at a glance **People at a glance** shows how many people are up to date across all their required documents. Select a status to open the corresponding People view: * **Up to date:** people who have completed their current required documents. * **Awaiting signatures:** people with pending requests. * **Requests needed:** people whose documents need a new request. * **No documents assigned:** people without required documents to track. This row appears when there are people in this state. These counts track document completion, not legal compliance or behavior after signing. A person can have pending requests and also need attention for a different document. See [completion statuses](/concepts/compliance) for definitions. ## Group follow-up If you use groups, **Group follow-up** shows up to three groups with outstanding work. Groups with the most people needing requests appear first, followed by those awaiting signatures. Select a group to open its **People** tab, filtered to people needing requests or awaiting signatures. Progress reflects the documents required by that group, not documents assigned elsewhere. **No group follow-up items right now** means no one in your groups needs a request or is awaiting signatures. People with no documents assigned may still need setup. Choose **View groups** to review all your groups. ## Document progress **Document progress** shows up to three published required documents with unfinished work, starting with the lowest completion rate. Completed documents do not fill the remaining rows. Select a document to open its **Workspace**. Review outstanding requests there, or choose **Compliance** to see who still needs to sign. This section tracks non-archived documents with **Requires a signature** on and assignments to active people. Draft-only documents and documents **Available to read** are not included. * **All tracked required documents are up to date:** everyone assigned to the tracked documents is up to date. * **No required documents to track yet:** progress appears once a published required document is assigned to someone. This is not a completion result. A separate publishing notice appears when documents need publishing or have unpublished changes. It can appear even when all tracked documents are up to date. Select it to find those documents, then review and publish under **Revisions**. Choose **View documents** to open the full document list. Use **Send document request** at the top of the dashboard to [send another request](/guides/send-requests) when your people and documents are ready. ## Recent activity **Recent activity** shows the latest changes. Select a linked person, group, or document to open it, or choose **View activity** for the [full activity history](/guides/activity-feed). Use [Reports](/guides/compliance-reports) when you need a shareable completion summary. # Data storage and leaving ClearPolicy Source: https://docs.clearpolicy.app/guides/data-storage Find hosting-region information, export options, organization removal behavior, and the published privacy and data-processing terms. ClearPolicy stores customer people records, documents, and completion history primarily in the **United States**. Hosting-region selection is not currently available. ## Primary location | Data or service | Location | | - | - | | Application and database | United States cloud infrastructure | | Document conversion | United States cloud infrastructure | | Uploaded documents and files | Private object storage in the United States | | Independent backup copies of high-value files | Separate United States cloud infrastructure | For contractual commitments, retention, security measures, and transfers, use the published [Data Processing Agreement](https://www.clearpolicy.app/data-processing-agreement/). ## What this covers This includes people, groups, document revisions, signature records, paper-on-file uploads, and data imported through enabled integrations. Billing and analytics are described separately in the [Privacy Policy](https://www.clearpolicy.app/privacy-policy/). ## Roles Your organization is the **data controller** for the people and document data it manages. ClearPolicy is the **data processor**, providing, securing, and supporting the service. ## Sub-processors and integrations See **Section 8** of the [DPA](https://www.clearpolicy.app/data-processing-agreement/) for sub-processors and provider information. Some services apply only when you enable an integration. ## International transfers For UK or European Economic Area organizations, review the DPA's transfer provisions. UK organizations can also download the [pre-signed UK International Data Transfer Agreement](https://www.clearpolicy.app/downloads/clearpolicy-uk-international-data-transfer-agreement.pdf). ## Leaving ClearPolicy 1. [Export completion reports](/guides/compliance-reports#export-to-csv) and [download records](/guides/download-records) you need to retain. 2. Manage your subscription separately through [Billing](/guides/manage-billing). 3. Review organization removal under **Settings → Organization → Profile** before confirming it. If you remove an organization with completed document requests after subscribing, ClearPolicy deactivates it and preserves completion records as the audit trail. To request permanent deletion of the organization, including those records, email [support@clearpolicy.app](mailto:support@clearpolicy.app). The team confirms with an owner before deletion. Permanent deletion cannot be undone. Eligible owners who have never subscribed can instead use [reset trial data](/guides/reset-trial-data) to remove test data while keeping the organization. ## Compliance reviews Use the [DPA](https://www.clearpolicy.app/data-processing-agreement/), [Privacy Policy](https://www.clearpolicy.app/privacy-policy/), and [Terms of Service](https://www.clearpolicy.app/terms-of-service/) for legal review. Email support if you need a countersigned DPA or a question is not covered. Your organization decides whether ClearPolicy meets its regulatory and contractual requirements. ClearPolicy does not provide legal advice. # Fix missing or failed request emails Source: https://docs.clearpolicy.app/guides/delivery-failures Check request delivery, correct an email address, and retry failed emails. If someone did not receive an email, first check whether you sent a **document request** or a **team invitation**. Adding a person alone sends neither. Group automation can send requests when you add membership. ## Check whether a request exists 1. Open the person's **Requests** tab, or search **Requests** by their name or email. 2. If there is no request, [send one](/guides/send-requests). Assignment alone does not send email. 3. If a request exists, open **Activity** to review delivery and status. 4. If it is still pending and no delivery problem is flagged, ask the person to check spam or junk. Use **Nudge** to send the same link again, or share the [signing portal](/guides/signer-portal). If the person needs management access instead, check their invitation under **Settings → Team members**. See [invitation help](/guides/add-team-members#manage-pending-invitations). ## Review a delivery failure Open the person's **Workspace** to review the delivery issue and affected requests. From a document's **Workspace**, use **Review delivery** beside the person's name to reach the same place. You can also open **Requests → Failures** and click **Review**. | Status | Meaning | | - | - | | **Bounced** | The email could not be delivered. The address or receiving server may be the cause. | | **Delivery failed** | The email could not be sent or was rejected. | | **Complained** | The person or their provider marked the email as spam. | Review the address, error details, and time of failure before choosing an action. A failure does not always mean the address is wrong. ## Retry the same address Check the address, affected requests, and delivery details. On the person's **Workspace**, click **Retry delivery for…**. In a **Review** dialog, choose **Email is correct — try again**. This queues another delivery attempt for eligible paused requests for that person. **Delivery queued** does not confirm delivery. For spam complaints, confirm that the person wants the request before retrying. A retry does not override an opt-out or a provider restriction. ## Correct an email address 1. Open the person's **Workspace**. 2. In the delivery issue panel, click **Update email**. 3. Correct the address and click **Save email**. 4. Review the affected requests and destination address. 5. Click **Retry delivery for…** to queue another attempt. Saving updates open requests but does not send email or clear the delivery pause. Completed requests keep their original recipient details. You can also change the address through **Edit profile**, or use **Update email address** in a **Review** dialog. Retry delivery separately after saving. > [!NOTE] > > Changing only the person's name updates open requests without sending email. > After changing an email address, use **Nudge** for eligible open requests that > have no delivery failure. ## Why reminders are paused ClearPolicy skips ordinary reminders for requests flagged for delivery follow-up. Review the issue and retry delivery separately. The person-level retry applies to their eligible paused requests, not just one document. Other open requests that delivered successfully can still receive reminders. Turn on **Delivery failures** in [notification settings](/guides/notification-settings) to receive alerts. ## Still not receiving email? [Contact support](/guides/get-support) with the organization, affected request, and error shown. Do not include passwords or access tokens. For a missing signing portal code, see [signing help](/guides/signing-help). # Download documents and completion records Source: https://docs.clearpolicy.app/guides/download-records Choose the right download for a published document, an online signature, or a signed paper copy. Choose a download based on what you need to keep: document content, evidence of one person's completion, or a summary of many people's status. | What you need | Where to get it | What it contains | | - | - | - | | Published document content | Document **Revisions**, then select a published revision | That revision's PDF, without a person's completion certificate. | | An online completion | Completed request → **Download signed document** | The document and electronic certificate of attestation. | | A paper completion | Completed request → **Download uploaded file** | The signed paper copy your team uploaded. No electronic certificate. | | Completion summary | **Reports → Print** or **Export CSV** | Status across the people and documents included by your filters. | | Request history | Request **Activity**, then print | The request's activity timeline. | ## Download an online completion 1. Open **Requests → By request → Completed**, the person's **Requests** tab, or the document's **Compliance** tab to find the completed request. 2. Open its actions menu. 3. Choose **Download signed document**. The electronic record includes the document version, person, completion time, and signing details such as typed name, IP address, browser information, and document hash. Historical click-only acknowledgments do not have a typed-name signature. People can also reopen their completed request from the email link or signing portal to download the online receipt when available. ## Understand the PDF certificate seal ClearPolicy digitally signs electronic certificate PDFs to help verify their origin and detect later changes. This PDF seal is separate from the person's typed electronic signature. Some PDF readers describe ClearPolicy's signing certificate as self-issued or not trusted by a public certificate authority. That message alone does not mean the file was altered. See the published [security information](https://www.clearpolicy.app/security/) for details. ## Download paper on file Open the paper-completed request and choose **Download uploaded file**. This is the original evidence uploaded by your team. ClearPolicy does not generate an electronic attestation certificate for paper completions. ## Print or export a summary Use [compliance reports](/guides/compliance-reports) when you need many people's statuses. A report is a summary; use the individual completion download when you need the document and its signature evidence. To print one request's history, select an outstanding request on a workspace or open **Activity** from the request's actions, then click **Print**. This prints the timeline, not the signed document. Closely repeated views may be grouped for readability. # Get help from support Source: https://docs.clearpolicy.app/guides/get-support Ask the in-app support assistant, request a human reply, review your conversations, or email the ClearPolicy team. Open **Support** in the ClearPolicy sidebar or email [support@clearpolicy.app](mailto:support@clearpolicy.app). We read every support email and usually reply the same US business day, Mountain Time. Complex issues may take longer. ## Open support chat Click **Support** in the sidebar. You can keep working while the panel is open. The assistant answers product questions using ClearPolicy documentation. Tell it what you are trying to do, the page you are on, and what happened. It can explain workflows and help you find the right settings. ## Ask for a person Say **“I need a person”** in the conversation. This sends the conversation to the team for a human reply in the same thread. You can also email support directly. Human replies are not instant live chat. You may receive an email notification when a team reply arrives while you are away from the conversation. ## Find an earlier conversation Use the support panel's conversation history to reopen a thread. You can close a conversation when it is resolved and optionally rate the help. A later question can start a new conversation. ## Email support Email [support@clearpolicy.app](mailto:support@clearpolicy.app) for account access, billing, integration problems, or anything easier to explain in a longer message. You can email us even if you cannot sign in. ## What to include * What you were trying to do. * What happened, including the exact error if there is one. * The page or feature involved. * Your organization name. * The affected document or person, only if relevant. * For an AI connection, the client you use, such as ChatGPT or Claude. Do not send passwords, one-time codes, API tokens, or full payment card numbers. ## Product documentation Start at [ClearPolicy help](/introduction), or use [signing help](/guides/signing-help) if you received a document to sign. The [changelog](/changelog) lists product updates. ## Security issues Report vulnerabilities to [security@clearpolicy.app](mailto:security@clearpolicy.app), using the [Vulnerability Disclosure Policy](https://www.clearpolicy.app/security/). For ordinary product help, use support instead. # Import people from a CSV Source: https://docs.clearpolicy.app/guides/import-people Prepare a CSV roster, choose an import mode, and check results. Export Excel or Google Sheets as CSV before uploading. Import a CSV to add many people at once. If your roster is in Excel or Google Sheets, export it as **CSV** first. ClearPolicy does not accept `.xlsx` or `.xls` workbooks for people imports. **Who can do this:** owners and administrators. Each import accepts up to **10,000 people** and a file up to **5 MB**. ## Prepare your file Open **Settings → Imports** and download the sample CSV. Use its headers: | Column | Required column? | Contents | | - | - | - | | `First name` | Yes | The person's first name, when available. | | `Last name` | Yes | The person's last name. | | `Email` | Yes | The address used for document requests. | | `Phone` | No | A phone number with a country code, such as `+14065550132`. | | `Groups` | No | Comma-separated group names, such as `Staff, Safety committee`. | Header capitalization does not matter. Use the sample names to avoid an unrecognized column. Save as UTF-8 CSV if names or accents are not displayed correctly. ```csv theme={null} First name,Last name,Email,Phone,Groups Alex,Morgan,alex@example.com,,"Staff, Safety committee" Priya,Shah,priya@example.com,,Staff ``` Quote a CSV cell that contains commas. Spreadsheet exports handle this for you. ## Choose an import mode | Mode | What it does | | - | - | | **Add Only** | Adds new people and matches existing people by email. Archived matches stay archived. This is the default. | | **Add & Unarchive** | Adds new people and restores matched archived people to active lists. | | **Roster Sync** | Adds new people, restores archived matches, and archives active people not successfully included in this import. | > [!WARNING] > > **Roster Sync** applies to your whole organization, not just one group. Use a > complete, checked roster. Missing people—and rows that fail to import—can > result in people being archived and their open requests canceled. Choose **Add > Only** when importing a partial list. ## Upload and import 1. Open **Settings → Imports**. The import action on **People** also takes you to imports. 2. Drop your CSV or click **Choose file**. 3. Check the preview and total record count. The preview shows a sample, not every row. 4. Select the import mode. 5. Click **Import** with the displayed people count. 6. Review progress and results under **Past imports**. Open the import details for failures and warnings. You can keep working while the import finishes. Wait for it to finish before starting another import in the same organization. ## Existing people and groups ClearPolicy matches people by email within your organization. A match reuses the person; it does not overwrite their existing name or phone. Edit those details through **Edit profile** on the person's page. A populated **Groups** cell sets that person's group list and creates missing groups. Review the group names before importing, including for existing people. Adding group membership can create requests when a group has **Automatic request emails** on. The email follows within a minute. Adding people alone does not send a team invitation. See [group automation](/guides/manage-groups#automatic-request-emails). ## Fix an import problem * **File not accepted:** export a CSV, check the 5 MB limit, and split files with more than 10,000 people. * **Missing columns:** use `First name`, `Last name`, and `Email` headers from the sample. * **Characters look wrong:** export again as UTF-8 CSV. * **Phone warning:** include the country code. An invalid phone may be skipped while the person is imported. * **Some rows failed:** check the import details and correct the affected rows before trying again. Use **Add Only** for a file containing only corrections or additions. # Manage billing Source: https://docs.clearpolicy.app/guides/manage-billing Check your plan or trial, subscribe, update payment details, and get help with billing problems. ClearPolicy has one plan at **\$29/month**, with unlimited people, documents, and team members. There are no per-seat fees or feature tiers. Annual billing is not currently offered. **Who can manage billing:** owners and administrators. Billing belongs to the selected organization. ## Open billing settings Open **Settings → Billing** to see the organization's trial or subscription status. If you belong to several organizations, check that you selected the right one. ## Subscribe after a trial The free trial lasts **30 days** and does not require a credit card. Check your trial end date on **Billing**. 1. Open **Settings → Billing**. 2. Click **Subscribe for \$29/month**. 3. Complete checkout and any payment confirmation requested. 4. Return to Billing to check the result. If you want to remove trial test data first, an eligible owner can [reset trial data](/guides/reset-trial-data). That option is unavailable after a successful subscription. ## Manage an active subscription Click **Manage** on Billing to open the billing portal. Use its available options to review billing information, update payment details, or manage cancellation. Review the confirmation and effective date shown for any change. Do not start another checkout to update an existing subscription. ClearPolicy directs active subscribers to **Manage**. ## Trial ended or payment needs attention When your organization no longer has an active trial or subscription, access to product workflows pauses. This can also affect signing, automated work, and connected integrations. Billing remains the place to restore access. Open Billing, complete the subscription or payment step shown, then check again. If a payment was taken but access has not returned, [contact support](/guides/get-support) with the organization name and the error or status you see. ## I think I subscribed twice Check Billing for each organization you manage. If a charge appears duplicated, email [support@clearpolicy.app](mailto:support@clearpolicy.app) so the team can review it. Do not send full payment card details. ## Canceling and deleting are different Manage the subscription from Billing. Removing an organization or requesting permanent data deletion is a separate action. Export the records you need and review [leaving ClearPolicy](/guides/data-storage#leaving-clearpolicy). # Create and manage groups Source: https://docs.clearpolicy.app/guides/manage-groups Organize people, add documents to a group, and choose whether membership changes send signature requests. Create a group when several people need the same documents. A group can include documents to sign and documents **Available to read**. **Who can do this:** owners and administrators manage group setup. Group Managers can follow up within their assigned groups. ## Create a group 1. Open **Groups** and click **Create Group**. 2. Enter a name, such as **Volunteer drivers**, and an optional description. 3. Check **Automatic request emails**. It is on by default. Turn it off if you want to finish setup before sending requests. 4. Add a **Default Recipient Message** if you want the same starting note on requests from this group. 5. Submit the form. ## Add people and documents 1. Open the group and use **Add People** on **People** to select existing people. 2. Open **Documents** and use **Add Documents** to select existing documents. 3. Review the selection and confirm each addition. The **Documents** tab separates **Requires a signature** from **Available to read**. Drafts must be published before people can sign or read them. You can also manage groups through **Edit profile** on a person's page or **Edit settings** on a document's page. Changes take effect when you click **Save changes**. ## Automatic request emails **Automatic request emails** creates requests for newly active signature assignments when people or documents are added to a group. The email follows within a minute. Until then, the request shows as **Queued**. Change the setting in the group's **Settings → Automation**. | Change | With automatic request emails on | | - | - | | Add a person | Eligible published documents that require a signature get requests. Multiple new requests can be collected into one email. | | Add a document that requires a signature | Eligible people get a request if the document is published. | | Add a document available to read | No request or email. Group members can open the published document in the signing portal. | | Add a draft | No request until there is a published revision and you send it. Publishing later does not send these missing requests by itself. | Existing active assignments are not a new assignment just because another group includes the same person and document. Use **Send missing** to handle gaps. Turning automatic emails off lets you prepare assignments and send later. Turning it on does not send a backlog of existing assignments by itself. > [!NOTE] > > Adding people through CSV imports, Planning Center, or integrations can also > trigger a group's automatic request emails. Check this setting before bringing > people into a group. ## Send missing requests Use **Send missing** when people have been assigned documents but still need a request: * **For the group:** open its **People** tab and click **Send missing** when it appears. * **For one document:** open the group's **Documents** tab, select a published document under **Requires a signature**, and click **Send missing** in the side panel. Check the people and document counts before sending. Searching or filtering the people in a document's panel does not change who receives its missing requests. Only published documents that require a signature can be sent. The email follows within a minute. Drafts and documents **Available to read** are not emailed. Use [reminders](/guides/reminders) for requests that are already open. ## Set a default message In **Settings → Automation**, enter **Default Recipient Message** and save. For example: “Please review and sign these policies before your first shift.” The message is used for automatic group requests and prefilled when you send from the group. You can edit or remove the note before a manual send. It appears in the request email and on the signing page. ## Assign Group Managers In **Settings**, select the **Group Managers** who should oversee the group, then save. They must already be team members with the Group Manager role. Group Managers can review completion, send missing requests, send reminders, and view request activity. They cannot change the group's setup or membership. See [team roles](/guides/add-team-members#choose-a-role). ## Remove membership or delete a group Owners and administrators can remove a person or document from a group. Open the group's **People** or **Documents** tab and select the person or document. In the side panel, open the three-dot menu and choose **Remove from group**. Removing a person or document from a group ends read access granted by that group. Another group may still grant access. Existing signature assignments and requests remain; remove an assignment or cancel a request separately if it is no longer needed. Deleting a group removes the group and its memberships, not the people or documents. Use the delete action in the group's **Settings**. ## Check progress Use **People** to see what each person still needs to sign. Use **Documents** to see who still needs a particular document. See [track completion in groups](/guides/track-compliance#group-compliance-view). # Add and manage people Source: https://docs.clearpolicy.app/guides/manage-people Add people, correct their details, manage group membership, and archive people while keeping their history. Use **People** for the people who receive your documents. To give someone management access to ClearPolicy, [invite a team member](/guides/add-team-members) instead. **Who can do this:** owners and administrators. ## Add a person 1. Open **People** and click **Add Person**. 2. Enter their name and email address. Last name and email are required; first name and phone are optional. 3. Choose groups if needed. 4. Save the person. Adding a person alone does not send email or create a team member login. If you add them to a group with **Automatic request emails** on, eligible published documents in that group get requests right away. The email follows within a minute, and the request shows as **Queued** until then. Check the [group settings](/guides/manage-groups#automatic-request-emails) before adding people. For a larger roster, [import a CSV](/guides/import-people) or connect [Planning Center](/integrations/planning-center). ## Find the right people Search by name or email. Use group, document-status, and active/archived filters to narrow the list. Status buttons help you find people who are **Compliant**, **Pending**, **Needs Attention**, or **Not Started**. **Failures** appears when requests need delivery follow-up. Open a person to start on **Workspace**. Review their details, groups, communication status, current document progress, outstanding requests, and recent activity. * **Workspace:** review what needs attention. Select an outstanding request to open its details and activity. **View activity** opens the Activity page filtered to this person. * **Documents:** current and previous assignments, completion status, and documents **Available to read**. * **Requests:** the person's request history and delivery status. Archive and delete actions are in the three-dot menu. ## Edit a person's details 1. Open the person and click **Edit** beside their details. You can also open the three-dot menu and choose **Edit profile**. 2. Change their name, email address, or phone number. 3. Click **Save changes**. > [!NOTE] > > Name and email changes update open requests without sending email. Completed > requests keep their original recipient details. After changing an email, retry > requests with delivery failures or use **Nudge** for eligible open requests. ## Change group membership Open **Edit profile**, add or remove groups, then click **Save changes**. Create new groups from **Groups** first. Saving an addition can send requests when the group has automatic emails on. Removing membership hides documents available to read through that group, unless another group still grants access. It does not automatically remove signature assignments or cancel existing requests. ## Use bulk actions Select people in the list, then choose an action: | Action | Result | | - | - | | **Add to group** | Adds the selected people to an existing group; group automation may send requests. | | **Nudge** | Sends reminders for eligible pending requests. | | **Archive** | Archives the selected people and cancels their open requests. | | **Unarchive** | Returns people to active lists. Canceled requests are not resent. | ## Archive or unarchive a person Open the person's three-dot menu and choose **Archive**, then confirm. You can also archive several people from the list. Archiving removes the person from active lists and compliance counts, cancels open requests, and ends current document assignments. Completed records, request history, and group memberships remain available. Choose **Unarchive** to return the person to active lists. ClearPolicy restores assignments from their existing groups. Review any direct assignments and add them again if needed. Unarchiving does not reopen canceled requests. ## Delete a person Open the person's three-dot menu and choose **Delete Person**. Type their name to confirm permanent deletion. If the person has any document request history, deletion is unavailable; archive them instead. An owner evaluating ClearPolicy with test records can use [reset trial data](/guides/reset-trial-data) while eligible. ## Fix email delivery failures Open the person's **Workspace** to review delivery issues. Correct the address if needed, then retry delivery separately. See [fix missing or failed emails](/guides/delivery-failures). # Manage document requests Source: https://docs.clearpolicy.app/guides/manage-requests Find outstanding requests by person or by request, review activity, send reminders, and cancel requests that are no longer needed. Use **Requests** to work through unfinished document requests across your organization. Each request is one person being asked to sign one document revision. **Who can use this page:** owners and administrators. Group Managers handle follow-up from their assigned group pages. ## Choose a view Open **Requests**. It starts on **By person** and **Outstanding**. ClearPolicy remembers the view you last chose. | View | Use it to | | - | - | | **By person** | Follow up with someone who has one or more matching requests. | | **By request** | Act on a single request. | Search by person name, email, or document name, or choose a filter. The filter applies to both views. | Filter | What it shows | | - | - | | **Failures** | Pending requests flagged for delivery follow-up. Appears when there are failures. | | **Outstanding** | Active, unfinished requests. | | **Not viewed** | Requests whose signing link has not been opened. | | **Viewed** | Requests opened but not completed. | | **Reminded** | Open requests that have received a reminder. | | **Completed** | Completed requests, including historical acknowledgments and paper on file. | | **Canceled/Expired** | Requests that can no longer be completed. | | **All** | Full request history. | ### By person Each row shows the person, how many matching requests they have, the oldest, the last activity, and when the next automatic reminder will go out. Click the row to open that person's requests. The sheet lists that person's requests in the current filter, such as **Outstanding documents**, with a count. Search on the page applies here. When an automatic reminder is scheduled, the sheet says ClearPolicy is taking care of follow-up and shows the next send time. If a request bounced or otherwise needs delivery follow-up, that notice is replaced with the provider error and a link to update the person’s email. Reminders stay paused for those requests. The people list shows **Fix delivery** instead of the next reminder. Open a request in the sheet to see when it was sent, viewed, reminded, completed, canceled, or expired. **View profile** opens the person. **Nudge** in the sheet reminds that person's eligible requests in the current filter, including requests on later pages. A request that is still sending, or one flagged for delivery follow-up, is not included. Add a note in the composer if you want to replace the note on those requests. ### By request Each row shows the person, document, status, requested date, and latest reminder date. Use this view for one reminder, activity, delivery review, cancel, expire, paper on file, or download. ## Open a request from a workspace On a person's or document's **Workspace**, select a row under **Outstanding requests**. The side panel shows the request's recipient details, status, dates, document, and activity. Use **Nudge** when available, or open the request's actions to cancel or expire it. **Print** prints the request history. Delivery problems require review before ordinary reminders can resume. On a person's workspace, **View all requests** opens their request history. On a document's workspace, **View compliance** opens its assignment list. ## Follow up on a request On **By request**: * **Nudge** sends a reminder using the existing request link. * **Nudge with note…** lets you replace the request's note before reminding. * **Activity** opens the history of sending, delivery, views, reminders, and completion or closure. * **Review** on a failed request helps you retry delivery or correct the address. See [send reminders](/guides/reminders) for single and bulk actions. ## Fix a delivery failure Use **Failures → Review** to inspect delivery details. If the address is correct, choose **Email is correct — try again**. Otherwise, update and save the address, then retry separately. Saving alone does not send email. See [correct an email address](/guides/delivery-failures#correct-an-email-address). Ordinary reminders pause for a flagged request. Other successfully delivered requests to that person can still receive reminders. See [fix missing or failed emails](/guides/delivery-failures). ## Follow up on a group of requests Click **Nudge** and choose **All outstanding**, **Not viewed**, **Viewed**, or **Reminded**. Search can narrow the audience; the current status tab does not set the reminder scope. Check the count in the composer before sending. See [bulk reminders](/guides/reminders#send-bulk-reminders-with-nudge). ## Send a new request Click **Send request**, select people and one or more documents, preview, and send. Each person gets one email listing those documents. Use a new request for a new signature; use **Nudge** for an existing open request. See [send document requests](/guides/send-requests). ## Close a request that should not be completed On **By request**, open the active request's actions menu and choose: * **Cancel request** when the person no longer needs to complete it. * **Expire request** to close it immediately as expired. The personal link no longer allows completion. The request and its activity stay in history. A canceled or expired request is not reopened; send a new request if the person still needs to sign. ## Record paper on file On **By request**, use **Record paper signature** on a pending request when the person signed a paper copy. A PDF or image upload is required. See [record a paper signature](/guides/record-paper-signature). ## Download completed documents On **By request**, use **Download signed document** for an online completion or **Download uploaded file** for paper on file. See [download documents and completion records](/guides/download-records). ## When to use Requests, People, Documents, and Reports | Question | Where to go | | - | - | | Who needs follow-up today? | **Requests → By person** | | What does one person still need to sign? | **People → Documents** | | Who has signed a particular document? | **Documents → Compliance** | | How do I share completion summaries? | **Reports** | # Choose your notifications Source: https://docs.clearpolicy.app/guides/notification-settings Choose email and browser completion alerts, delivery-failure emails, your daily digest, and notifications for other team members' requests. Notification settings control alerts **to you as a team member**. They do not control the requests and reminders sent to people. **Product updates** apply to your account. The other options apply to the organization you have selected. ## Change your preferences 1. Select the organization you want to configure notifications for. 2. Open **Settings → Notifications**. 3. Turn the options on or off. For **Instant completion notifications**, choose **Email**, **Browser**, or both. 4. Click **Save**. | Setting | What you receive | Email | Browser | Default | | - | - | - | - | - | | **Instant completion notifications** | An alert when someone completes a request you sent. | Available | Available | Both off | | **Daily digest** | A morning summary of the previous day's completions. | Available | — | On | | **Delivery failures** | An alert when a request email bounces, fails, or is marked as spam. | Available | — | On | | **Product updates** | Occasional email about new ClearPolicy features. Turn this off here or with the unsubscribe link in the email. | Available | — | On | A dash means that notification type is not available in the browser channel. **Team activity** is a separate setting below the channel table. ## Instant completion notifications Email alerts identify the person and document. Browser alerts omit names and document details; clicking one opens your organization's dashboard. You can use email, browser alerts, and the daily digest together, or choose only the channels you need. ## Turn on browser notifications Browser completion alerts are off by default. 1. Select your organization and open **Settings → Notifications**. 2. Under **Instant completion notifications**, turn on **Browser**. 3. Allow notifications if your browser asks. ClearPolicy registers this browser for delivery if needed. 4. Click **Save** to save your organization's notification choice. You do not need to enable the device separately in the section below. If permission is declined or dismissed, or setup fails, the switch stays off and guidance appears beside the setting. Browser alerts do not require an open ClearPolicy tab. Delivery depends on your browser, device settings, and connection. ### Manage this browser or device Use **Browser notifications on this device** below the notification preferences to check device status or choose **Enable on this device** or **Disable on this device**. * Notification choices are saved separately for each organization. Device enablement is shared across your organizations. * Turning off **Browser** for one organization stops its completion alerts after you click **Save**. It does not disable other organizations or change email preferences. * **Disable on this device** stops all browser notifications on this device. It does not change other devices or your saved organization preferences. * Signing out does not disable browser notifications. Repeat setup in each browser or device where you want alerts. You can have up to 10 browser registrations across your organizations. If you reach the limit, disable notifications on another browser or device before adding a new one. ### If your browser blocks notifications Allow notifications for ClearPolicy in your browser's site settings. Return to **Browser notifications on this device** and click **Check again**, then try the **Browser** switch again. Device or operating-system notification settings, including Focus or Do Not Disturb, can also silence alerts. On iPhone or iPad, add ClearPolicy to your **Home Screen**, open it from there, and then enable notifications. A regular browser tab is not enough. If your browser is unsupported, you can still use email alerts and the daily digest. ## How delivery failure notifications work A delivery alert identifies the address and problem. Open the affected request in ClearPolicy and use **Review** to [resolve the failure](/guides/delivery-failures). ## How the daily digest works The digest summarizes the previous day's completions and is scheduled for **8:00 AM in the organization's time zone**. Check [time zone settings](/guides/timezone) if the timing is unexpected. ## Team activity notifications Owners and administrators can enable **Team activity** in its separate card to include completions from requests other team members sent. It applies to your enabled completion emails, browser alerts, and daily digest; it does not turn those options on. **Team activity** is off by default. Group Managers receive completion notifications for requests they sent themselves. ## Turn off completion emails Turn off **Email** under **Instant completion notifications** and turn off **Daily digest**, then click **Save**. You can keep browser completion alerts on. Delivery-failure emails have their own setting. To change follow-up emails sent to people, use [reminder settings](/guides/reminders#set-up-automatic-reminders). ## Draft review emails Emails about [draft review](/guides/review-document)—approval requests, completed approvals, and comments—are separate from completion notifications. They do not have an on/off option here. Turning off **Instant completion notifications**, **Daily digest**, or **Team activity** does not turn off review emails. # Add your organization's logo Source: https://docs.clearpolicy.app/guides/organization-logo Show your logo on request emails, signing pages, and the signing portal, and choose its display style. Add a logo so people recognize your organization in document request emails, on the signing page, and in the signing portal. **Who can do this:** owners and administrators. ## Add a logo 1. Open **Settings → Organization → Branding**. 2. Under **Logo**, click **Upload**. 3. Choose a PNG, JPEG, or WebP file up to **2 MB**. 4. Choose a display style, check the preview, and click **Save**. | Style | Result | | - | - | | **Show as icon** | A small logo beside your organization name. Works well for a compact mark. | | **Show full width** | The logo replaces the name heading on the signing page and portal. Works well for a horizontal logo containing your name. | Your organization name still appears in email text. The ClearPolicy name remains on emails, signing pages, and the portal. ## Share your portal link Your organization's signing portal link appears below the branding preview. Copy it to give people a place to find their documents. See [share the signing portal](/guides/signer-portal). # Make documents available to read Source: https://docs.clearpolicy.app/guides/read-documents Let people open published documents in the signing portal through their groups, without a signature request. Turn off **Requires a signature** when people need to read a document without signing. Publish it and add it to a group. People in that group can then open it in the **signing portal**. **Who can set this up:** owners and administrators. People reading the document do not need team member accounts. ## Give people access 1. Open the document's three-dot menu and choose **Edit settings**. Turn off **Requires a signature** and click **Save changes**. You can also choose this when using **Add Document**. 2. Make sure the document has a published revision. Drafts are not available to people. 3. Add the document to a group through **Edit settings → Groups**, then save. You can also use the group's **Documents → Add Documents**. 4. Add the people who need access to that group. 5. Share your organization's signing portal link from **Settings → Organization → Branding**. The document's **Workspace** shows its groups and reading-access status. If it needs a group or a published revision, follow the notice there. Use **View published version** to open **Revisions**. People enter their email address and a one-time email code. They can find the document under **Documents** and click **Open**. It may be under **More documents** when they also have documents to sign or signed copies. ## What this does—and does not—record For a document available to read: * Group membership controls access to the current published file. * ClearPolicy does not send an email announcing availability. * No signature request or signature assignment is created. * Opening the document is not recorded. Availability does not prove that someone read it. * The document does not require completion or contribute a signature requirement to compliance tracking. If you need a signature record, leave **Requires a signature** on and [send a request](/guides/send-requests). ## Change who can read it Add or remove people from its groups. Removing membership removes that group's access; another group can still grant access to the same document. There is no direct person-by-person reading grant. Use a group, even for a small audience. Assigning a signature-required document to a person without sending a request does not grant reading access. ## Turn signatures off on an existing document Turning **Requires a signature** off ends current signature assignments and cancels pending requests. The app asks you to confirm when pending requests will be canceled. Completed signature records remain in history. Group links remain. Current group members can read the published file. A person with only a direct signature assignment needs group membership to read the current file this way. ## Turn signatures back on Turning **Requires a signature** on assigns current group members. If the document is published and a group has **Automatic request emails** on, the app asks you to confirm with **Turn on and queue**. The request is created right away. The email follows within a minute, and the request shows as **Queued** until then. Otherwise, send requests when ready. Reading access without a request ends when signatures are turned on; people use their pending requests and signed copies instead. ## Someone cannot see a document Check that the document is published, not archived, and has **Requires a signature** off. Confirm the person is active and belongs to a group that includes the document. Ask them to use the email on their person record and select the right organization in the portal. They do not need a previous signature request to read a document shared this way. # Record a paper signature Source: https://docs.clearpolicy.app/guides/record-paper-signature Upload a signed paper copy to complete a pending request and keep the evidence with the person's document history. Use **Record paper signature** when someone has signed a paper copy instead of completing the request online. ClearPolicy stores the uploaded file and marks the request complete for that document revision. ## Before you start * You must be able to act on the request. Group Managers are limited to their assigned groups. * The request must be pending, not completed, canceled, or expired. * You need the signed paper copy for that request's document version. * Upload a PDF, JPEG, PNG, or WebP file up to **25 MB**. A note alone is not enough. ## Upload the signed paper copy 1. Find the pending request in **Requests**, a person's request list, or the document's **Compliance** tab. 2. Open the actions menu and choose **Record paper signature**. 3. Upload the signed paper copy. 4. Confirm that you obtained the paper signature or acknowledgment from that person for the document. 5. Submit the form. ## What changes The request becomes complete and reminders stop. Completion counts for the revision covered by the request; an older version can still be **Outdated**. The record shows **Paper on file**. Activity includes **Paper Signature Recorded** and the team member who recorded it. ## Download the evidence Choose **Download uploaded file** on the completed request. This returns the signed paper copy you uploaded. Paper on file is not an electronic signature captured by ClearPolicy. It does not include an electronic attestation certificate. See [how signatures and records work](/concepts/attestations#paper-on-file). # Send reminders Source: https://docs.clearpolicy.app/guides/reminders Remind people about open requests, update a reminder note, or configure Smart Follow-up and a fixed reminder schedule. A reminder emails the same personal link for an open request. It does not create a new request or extend its deadline. Owners and administrators can follow up across the organization. Group Managers can follow up within their assigned groups. ## Send a reminder for a single request Open **Requests → By request** and find the pending request. You can also open a document on a person's **Documents** tab, then find the request under **Requests** in the **Document compliance** panel. * Click **Nudge** to send a reminder immediately. * Choose **Nudge with note…** from the adjacent menu to write or replace the note first. Review **Preview**, then click **Send**. A new note replaces the previous note on that request. It appears in the reminder email and on the signing page. The request activity view may label the reminder action **Send reminder**. ## Send bulk reminders with nudge 1. Open **Requests** and search if you want to narrow the audience. 2. Click **Nudge** and choose **All outstanding**, **Not viewed**, **Viewed**, or **Reminded**. 3. Check **To** and the request count in the composer. 4. Add a note if you want to replace the note on every included request. Leave it blank to keep each request's existing wording. 5. Review **Preview**, then click **Send**. > [!NOTE] > > The chosen reminder scope and search determine the audience. The status tab you are viewing does not set the scope. Check the count before sending. Requests flagged for delivery follow-up are excluded. When possible, multiple reminders for the same person are grouped into one email. You can also select people on **People** and use **Nudge** for their eligible pending requests. On **Requests → By person**, open a person and use **Nudge** in the sheet to remind their eligible requests in the current filter, including later pages. Requests that are still sending, and requests flagged for delivery follow-up, are not included. To remind someone about documents in one group, open the group's **People** tab and select the person. **Nudge** at the bottom of **Group compliance** reminds their eligible pending requests in that group only. ## Set up automatic reminders Owners and administrators can configure reminders under **Settings → Document Requests**. 1. Turn on **Enable automatic reminders**. 2. Leave **Smart Follow-up** on for adaptive timing, or turn it off for a fixed cadence. 3. For a fixed cadence, choose **Every day**, **3 days**, **5 days**, **7 days**, or **14 days**. Enable **Repeat reminders until completed** to keep reminding at that interval. 4. Save the settings. Automatic reminders run in the morning in your organization's [time zone](/guides/timezone). They stop when a request is completed, canceled, or expired. When one of a person's requests is due, other open requests that are already old enough for a reminder go in the same email. A request sent that day is left for a later reminder. ### Smart Follow-up Smart Follow-up adjusts timing based on whether the request has been viewed. The first reminder is due about 48 hours after sending if the person has not opened the request, or about 24 hours after viewing without completing. Reminders are sent during the daily morning check, not at an exact hour after the event. ### Deadline reminders For requests with expiry enabled, Smart Follow-up uses deadline reminders in the final week: **7 days**, **3 days**, **1 day**, and **the deadline day**. Each milestone is sent at most once. Regular viewed/not-viewed reminders pause during that period. Manual reminders also use deadline-focused wording when a request is in its final week. ### Default settings | Setting | Default | | - | - | | Automatic reminders | On | | Smart Follow-up | On | | Fixed cadence, when used | 3 days | | Repeat reminders | On | Check your organization's settings for its current configuration. ## What happens when a reminder is sent The request keeps its link, revision, recipient details, and deadline. **Activity** records the reminder; automatic reminders appear as **Reminded (Scheduled)**. Emails use your organization's language and time zone. To ask for a fresh signature after a previous completion, use [renewal](/guides/renewals) or send a new request instead. ## When reminders are not sent ClearPolicy skips a request while it needs delivery follow-up. This applies to manual, bulk, automatic, and integration reminders. Other successfully delivered requests for the same person can still receive reminders. Click **Review**. Use **Email is correct — try again**, or [correct the person's email](/guides/delivery-failures#correct-an-email-address) and save. See [delivery failures](/guides/delivery-failures). Canceled, expired, and completed requests do not need reminders. Send a new request if someone still needs to sign after an old request was closed. # Ask people to sign again on a schedule Source: https://docs.clearpolicy.app/guides/renewals Set a document's renewal interval and use Auto-renew to send new signature requests when each person's next sign-off is due. Use **Renewal** when people need to sign a document again periodically, even if its content has not changed. Turn on **Auto-renew** to send a new request when renewal is due. **Who can set this up:** owners and administrators. The document must require a signature. Automatic renewal requests require an active trial or subscription. ## Set up recurring signatures 1. Open the document's three-dot menu and choose **Edit settings**. 2. Turn on **Renewal**. 3. Set **Renew every** to a number and unit: days, weeks, months, or years. 4. Turn on **Auto-renew** if you want ClearPolicy to send requests automatically when due. Leave it off to track due dates and send requests yourself. 5. Click **Save changes**. For an annual sign-off, choose **1 year** and turn on **Auto-renew**. Each person's due date is based on their last completion, not a shared calendar date. ## How renewal dates work ClearPolicy adds the renewal interval to each person's most recent completion date. One month means 30 days; one year means 365 days. When the interval passes, the document becomes **Renewal due** for that person unless a current request is already pending. With **Auto-renew** on, ClearPolicy checks daily and sends eligible new requests using the current published revision. Archived people and documents do not receive automatic renewal requests. A current assignment is required. > [!NOTE] > > Changing the renewal interval affects when existing completions become due. A > shorter interval can make people due for renewal sooner. Review the warning > before saving. ## Send the first request Renewal follows an existing completion. Setting a renewal interval does not replace the first request. [Send the document](/guides/send-requests) to people who have not signed it yet. If **Auto-renew** is off, review **Renewal due** documents in completion views or the **Outstanding People** report, then send requests when ready. ## Renewal, reminders, and expiry | Feature | Purpose | | - | - | | **Renewal** | Ask for another signature after a previous completion becomes due. | | **Reminders** | Follow up on a request that is already open. | | **Request expiry** | Set how long a new request can remain unfinished before it closes. | | **New revision** | Change the content of the document. Earlier signatures remain tied to their original version. | See [reminders](/guides/reminders), [request expiry](/guides/request-expiry), and [document updates](/guides/update-document). ## Stop automatic renewal requests Turn off **Auto-renew** to stop sending new requests automatically while keeping renewal tracking. Turn off **Renewal** if repeat signatures are no longer required. Save the change. Requests already sent remain open. [Cancel those requests](/guides/manage-requests#close-a-request-that-should-not-be-completed) separately if people no longer need to complete them. # Set request deadlines Source: https://docs.clearpolicy.app/guides/request-expiry Choose how long new document requests stay open and send replacement requests when unfinished ones expire. Request expiry closes unfinished requests after a set number of days. New organizations start with a **30-day** window. Check your settings for your organization's current window. **Who can change this:** owners and administrators. ## Configure request expiry 1. Open **Settings → Document Requests**. 2. Under **Document request expiry**, turn **Enable document request expiry** on or off. 3. If enabled, choose **3**, **5**, **7**, **14**, **30**, or **60 days**. 4. Save the settings. > [!NOTE] > > Changes apply to new requests only. Existing requests keep their original deadline. Turning expiry off does not reopen expired requests or remove existing deadlines. ## How expiry works Each new request gets a deadline using the window in effect when it is sent. After that deadline, an unfinished request cannot be completed. Expired requests appear under **Canceled/Expired** and remain in history. You can also close an open request immediately with **Expire request** in its actions menu. ## How recipients see the deadline The deadline appears in request and reminder emails, on the signing page, and on pending requests in the signing portal. Email dates use the organization's [time zone](/guides/timezone). ### After a request expires An unfinished expired request displays an expiry notice instead of a signing form. It no longer appears in the signing portal's pending list. The person should contact the sender for a new request. A request completed before its deadline stays completed. The person can still open the completed document; the old deadline does not undo their signature. ## Re-sending after expiry [Send a new request](/guides/send-requests) for the document if the person still needs to sign. The expired request stays in history and the new request gets its own deadline under your current settings. Sending a reminder does not extend a deadline. Use [Smart Follow-up](/guides/reminders#deadline-reminders) to remind people before requests expire. # Reset trial data Source: https://docs.clearpolicy.app/guides/reset-trial-data Remove trial people, documents, groups, requests, and signature records while keeping your organization and settings. Use **Reset trial data** when you tested ClearPolicy with sample records and want a clean start before subscribing. Only an **owner** can use this action, and only while the organization has never successfully subscribed. It does not restart or extend the trial. > [!WARNING] > > This permanently deletes the trial data, including signature records, electronic certificates, paper signature files, and related activity. It is not an archive and cannot be undone. Download anything you need before continuing. ## Reset trial data 1. Open **Settings → Organization → Profile**. 2. In **Danger zone**, click **Reset trial data**. 3. Review what will be deleted. 4. Type the organization name and click **Permanently delete trial data**. ## What is deleted * People. * Documents and revisions. * Groups. * Document requests and completion records. * Certificates, paper signature files, and related activity. ## What stays * Your organization and team members. * Settings, branding, and integrations. * Billing information and the existing trial end date. After a reset, the action is hidden until there is trial data to remove again. Since integrations stay connected, check their settings before bringing people back in. ## After you subscribe Reset trial data is no longer available after a successful subscription. Use archive actions to preserve normal working history, or review [leaving ClearPolicy](/guides/data-storage#leaving-clearpolicy) for organization removal and permanent-deletion requests. # Review and approve a draft Source: https://docs.clearpolicy.app/guides/review-document Ask reviewers for feedback on a draft, optionally require approval, and publish when it is ready. **Who can do this:** owners and administrators. Reviewers can comment or approve the current content. Review does not block publishing unless you turn on **Require approval before publishing**. Internal approvals do not replace signatures from people. ## Request review 1. Open **Documents**, select the document, and open **Revisions**. 2. Select the draft, or click **New Draft** to update a published document. 3. Finish your changes and wait for saving or file processing to finish. 4. If the revision sidebar is hidden, click **Details** in the revision toolbar. On smaller screens, use the panel icon labeled **Revision**. 5. Under **Reviewers**, click **Add reviewers**. Select team members from the list. You cannot select yourself. 6. Click **Request review** to email the newly selected reviewers. Selecting team members does not send emails until you confirm. If the invitation option is available, enter an email address to invite someone. Review the access notice before sending: the invitation grants **Administrator** access to the organization, not document-only access. ## Require approval before publishing New drafts start with **Require approval before publishing** off. Add at least one reviewer to enable the switch, then turn it on if approval is required. With the switch on, every listed reviewer must approve the latest content before you can publish. New requests use **Request approval**. With the switch off, pending reviews, comments, or missing approvals do not block publication. Turning the switch off asks for confirmation. It does not remove existing approvals or comments. Removing the last reviewer also turns off required approval; the removal confirmation explains this. Changing the switch does not send review emails or invalidate approvals. > [!NOTE] > > New uploads and cloud imports publish their first revision when added. Review > later changes in a new draft. Content written in ClearPolicy starts as a draft > and can be reviewed before its first publication. ## Approve a draft 1. Open the revision from your review request email. You can also find the draft under the document's **Revisions** tab. 2. Read the current draft and check **Discussion** for comments. 3. Under **Reviewers**, click **Approve** when you are ready. Before publication, use **Withdraw approval** beside your name to take back your own approval. If approval is required, publishing will wait for you to approve again unless you are removed from the reviewer list. Approval does not publish the draft or send signature requests. ## Add a comment You can comment even if you are not a selected reviewer. Leaving a comment does not count as approval. 1. Open **Discussion** in the revision sidebar. 2. Type in **Add a comment…**. 3. Click the arrow button labeled **Post comment**. ![Discussion showing a policy change requested by Maya Chen, Alex Morgan's update, and a drafted reply with the Post comment arrow.](https://mintcdn.com/ferviddigital/G7W6y7JpEM3tHfM6/images/revision-review/discussion-area.png?fit=max\&auto=format\&n=G7W6y7JpEM3tHfM6\&q=85\&s=4c00464bb8e75aacc60ae7ad900d2ef0) The screenshot shows fictional people and sample content. **Discussion** shows comments and review activity together. Click **Load earlier activity** to see older entries. Comments do not block publication. ## Change content after requesting review Editing document text or replacing an uploaded or imported file invalidates earlier approvals. Changing **What changed** or document settings does not. 1. Make your changes and wait for saving or file processing to finish. 2. Check **Reviewers**. **Needs new request** means the review request refers to earlier content. 3. Click **Request review again**, or **Request approval again** when approval is required, so the affected reviewers can review the latest draft. Saving does not send review emails. Requesting review again is for changed content, not a reminder for an unchanged draft. ## Remove a reviewer Click the **X** beside the reviewer, then confirm **Remove reviewer**. Their approval is no longer required, but comments and review history remain. Removing the last reviewer turns off required approval. **Unavailable** means the team member's role or access no longer allows them to approve, or their invitation is no longer available. Remove unavailable reviewers before requesting review again. They continue to block publishing only while approval is required. ## Publish and view the review record Click **Publish** and confirm when the draft is ready. If **Require approval before publishing** is on, every listed reviewer must approve the latest content first. To view the review record afterward, open **Revisions** and select the published version. Its review is read-only. Comments and review activity remain in **Discussion**. If people need to sign the published document, [send document requests](/guides/send-requests) separately. # Send document requests Source: https://docs.clearpolicy.app/guides/send-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 workspace. Group Managers send missing requests within their assigned groups. ## Send missing requests for a document Owners and administrators can use **Send requests** to send one document to all active people assigned to it whose status is **Unrequested**. The button appears at the top of the document's **Workspace** and **Compliance** tabs. It shows how many requests will be sent. When no requests are missing, the button is hidden. This sends to everyone who qualifies, not just the people visible in the table. Searching, filtering, or changing pages does not narrow the send. 1. Open the document's **Workspace** or **Compliance** tab. 2. Click **Send requests**. 3. In the **Document request** window, review the people and document counts. Add an optional note in **Compose**. 4. Open **Preview** to check the email. 5. Click **Send** with the request count to confirm. Nothing is sent until you confirm. The email follows within a minute. This action skips people with pending requests, completed signatures, **Outdated** completions, or signatures due for renewal. To request signatures on an updated version, see [update a document](/guides/update-document#ask-people-to-sign-the-update). To choose specific people instead, use **Send request** from the three-dot menu. ## Send to one or more people 1. Open a published document's **Workspace** or **Compliance** tab. Open the three-dot menu and choose **Send request**. You can also start from **Requests**, the dashboard, or a person's **Workspace**. 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 open requests without sending email. Retry requests with delivery failures separately, or use **Nudge** for eligible open requests. Completed requests keep their original recipient details. See [correct an email address](/guides/delivery-failures#correct-an-email-address). # Sign a document Source: https://docs.clearpolicy.app/guides/sign-document Open a document request, type your name to sign, and find your signed copy. No ClearPolicy team member account is needed. If an organization sent you a ClearPolicy document request, open the link in its email to read and sign. You do not need to register, create an organization, or set a password. ## Sign from an email link 1. Open the document request or reminder email and follow its personal link. 2. Read the document. Check the organization, your name, and any deadline. 3. Choose the signing action and type your name as requested. 4. Review the electronic-signature confirmation and submit. 5. Look for the completion confirmation. Download your receipt if you want a copy. Use your own link. Do not sign through someone else's request. If the name or document is wrong, ask the organization that sent it to correct the request. If other requests are waiting, you can use **Review next document** when offered. ## Use the signing portal Use the portal if you lost an email or want to find all your documents: 1. Open the organization's portal link, or [go.clearpolicy.app](https://go.clearpolicy.app). 2. Enter the email address the organization has for you. 3. Check your inbox for a **6-digit code** and enter it. 4. Open **To sign**, then click **Sign** beside a document. 5. Read and sign using the same steps as an email request. The portal uses a code instead of a password. If you reached the ClearPolicy team login page, choose **Here to sign a document?** rather than registering a team account. ## Find signed copies and documents to read Open **Documents** in the portal: * **Sign** means a request still needs your signature. * **Open** lets you open a signed copy or a document your organization made available to read. * **Your signed copies** lists earlier signed versions when there is more than one. * **Paper on file** means the organization recorded a signed paper copy. It does not include an electronic certificate for you to download. Some documents are available to read without signing. Opening one does not record a signature or a view. If you have documents from several organizations at the same email, switch organizations in the header. ## Sign out Use **Sign out** when finished, especially on a shared device. If your session ends, enter your email again to receive a new code. ## Need help? See [fix a signing problem](/guides/signing-help) for missing emails, expired links, codes, and name mismatches. Contact the organization that sent the document for changes to your request or access. # Share your organization's signing portal Source: https://docs.clearpolicy.app/guides/signer-portal Give people one link to find their pending requests, signed copies, and documents available to read. Share your signing portal link when people need a place to find their documents. They use their email and a one-time code; they do not need a team member account. If you are here to sign, see [sign a document](/guides/sign-document). ## Your organization's link 1. Open **Settings → Organization → Branding**. 2. Copy the signing portal link listed below the preview. 3. Share it on your website, internal site, newsletter, or in a message to your people. The link opens a page with your organization's name and [logo](/guides/organization-logo). The ClearPolicy name remains in the footer. People can also use [go.clearpolicy.app](https://go.clearpolicy.app) if they do not have your organization's link. ## When to point people here * They lost a request email. * They have several documents to sign. * They want a copy of something they already signed. * They need documents you made [available to read](/guides/read-documents). The portal does not send requests for you. A personal link in a request or reminder email still opens that request directly without an email code. ## How people sign in People enter the email on their person record and use the **6-digit code** sent to that address. A matching person record is required; a previous signature request is not required for documents available to read. People with access to more than one organization can switch organizations in the portal header. They see one organization's documents at a time. ## What people see | Tab | Contents | | - | - | | **To sign** | Pending requests they can still complete. | | **Documents** | Pending documents, signed copies, and published documents available to read through their groups. | ### To sign **Sign** opens the request's signing page. Expired and canceled requests are not listed. ### Documents **Open** leads to a signed copy or an available-to-read file. **Your signed copies** lists multiple completions for a document. Readable documents may appear under **More documents** when signature-related documents are also listed. A signature-required document appears after a request is sent. With signatures off, the document must be published and included in a group the person belongs to. Opening a document available to read is not recorded. **Paper on file** identifies a completion recorded by your team. It does not offer a person-facing electronic certificate. ## Email link vs signing portal Use the personal email link for one request. Share the portal for a place to return to all the person's documents. Both lead to the same signing workflow for pending requests. ## Session and sign out People can use **Sign out** in the header. If their session ends, they enter their email again for a new code. ## What to tell people > Open our signing portal link and enter your email address. Use the one-time code sent to your inbox to see documents to sign, signed copies, and documents you can read. You do not need to create a ClearPolicy account. For missing codes, an unrecognized email, or missing documents, see [signing help](/guides/signing-help). # Fix a signing problem Source: https://docs.clearpolicy.app/guides/signing-help Get help with missing request emails, one-time codes, expired links, incorrect names, and documents missing from the signing portal. You do not need a ClearPolicy team member account to sign. Use the personal link in your email or the [signing portal](https://go.clearpolicy.app). ## I cannot find the request email Check spam or junk, then use the signing portal with the email address the organization has for you. Ask the sender to confirm that a request was sent to that address and to send a reminder if needed. If you manage the organization, use [missing or failed email help](/guides/delivery-failures). ## I did not receive a portal code 1. Check that the email you entered matches the address the organization has for you. 2. Check spam or junk. 3. Use **Resend code** when it becomes available and use the latest code. 4. If it still does not arrive, ask the organization to check your person record and email address. The code-entry screen can appear even when the address is not recognized. Seeing that screen does not confirm that an email was sent. A person record must exist for your address. ## My code expired or does not work Request a new code and enter the latest one. Use **Use a different email** if you entered the wrong address. You do not need to reset a password. ## My request expired or was canceled An unfinished expired or canceled request cannot be signed. Ask the organization to send a new request. A reminder cannot reopen it. If you completed the request before its deadline, your completion remains recorded and you can still open the completed copy. ## My name is wrong or the signature is not accepted Type the name requested on the signing page. If it is incorrect, ask the sender to correct your person record, then reopen the request. Do not use someone else's name or link. The sender can update the name on an open request without replacing it. If they change your email address, ask them to send the updated link or use the signing portal with your new address. Completed records do not change. ## A document is missing from the portal Check your email address and the organization selected in the header. Ask the organization to confirm access: * For a document requiring a signature, they need to send you a request. Canceled and expired requests are not listed. * For a document available to read, it must be published and shared through a group you belong to. A previous signature request is not required. ## The organization is not accepting signatures Contact the organization that sent the request. Its team needs to resolve the account issue before you can continue. ## I cannot complete the request online Ask the organization whether you can sign a paper copy instead. Its team can [record paper on file](/guides/record-paper-signature) on a pending request. You cannot upload a paper completion yourself through the signing portal. For a technical issue the organization cannot resolve, [contact ClearPolicy support](/guides/get-support) and describe the error. Do not send passwords or one-time codes. # Set your organization's language and time zone Source: https://docs.clearpolicy.app/guides/timezone Choose the language for organization emails and signing pages, and the time zone for email dates and scheduled reminders. Your organization's language and time zone affect how people receive requests and see dates. Your personal app language is a separate setting. **Who can change organization settings:** owners and administrators. ## Set a time zone 1. Open **Settings → Organization → Profile**. 2. Under **Organization information**, choose **Time zone**. 3. Click **Save**. If you leave the app default selected, the organization uses that default. Choose your local zone if your team works elsewhere. ## Where time zone applies * Dates and deadlines shown in request and reminder emails. * The morning schedule for automatic reminders. * The daily completion digest, scheduled for 8:00 AM in the organization's time zone. Changing time zone does not reopen expired requests or extend existing request deadlines. ## Set the organization's language On the same **Organization → Profile** page, select **Language** and save. This supplies the default language for organization emails and public signing flows when a more specific preference is not available. ## Change the language you see in the app Open **Settings → Account → Profile**, choose your preferred language, and save. This changes your own app experience, not everyone else's settings. See [account settings](/guides/account-security) and [automatic reminders](/guides/reminders#set-up-automatic-reminders). # Track who still needs to sign Source: https://docs.clearpolicy.app/guides/track-compliance Choose the person, document, or group view that answers your question, then act on the outstanding work. Start with the question you need to answer. Owners and administrators can use organization-wide views. Group Managers work inside their assigned groups. | Question | View | | - | - | | Which open requests need follow-up? | **Requests** | | Who still needs one document? | **Documents → Compliance** | | What does one person need? | **People → Documents** | | How is a department or team doing? | **Groups → People** or **Documents** | | What needs attention across the organization? | **Dashboard** | | How can I share the results? | **Reports** | ## Requests page Open **Requests** for unfinished requests. Search and filter, then send reminders, resolve delivery failures, or close requests no longer needed. See [manage requests](/guides/manage-requests). ## Document workspace Open a document to start on **Workspace**. Review its published version, signature requirement, groups, renewal settings, and recent activity. For a published document requiring signatures, select an **Outstanding requests** row to open that request's details and activity. Use **Nudge** when available, or review a delivery issue before retrying. **View compliance** takes you to the assignment list. Workspace progress counts current assignments, not previous assignments. No outstanding requests does not mean everyone has completed the document. Documents **Available to read** show group access instead of signature progress. Archived documents retain history but no longer show current progress. ## Document compliance view Open the document and select **Compliance**. Filter by status or search for a person. Review who has completed the current revision, who has a pending request, and who needs a new request. To send missing requests for this document, use **Send requests** at the top of the page. See [send missing requests for a document](/guides/send-requests#send-missing-requests-for-a-document) for who is included and how to review the send. Select a person to open the **Document compliance** side panel. When they have request history, you can switch between: * **Requests:** review each request, the version it covers, and its activity. Use the request's actions to send a reminder or download a completed record. * **Signed:** review the versions the person has completed, including paper on file. When a new request is needed for that person, **Send request** appears near the top of the side panel. You can send the latest version even if a request for an older version is pending. Sending the new request cancels the older pending request. See [update a document](/guides/update-document). If the document has no published revision, finish it under **Revisions** first. ### Add people **Add People** assigns people to the document. It does not email them unless **Also send a document request** is on. To choose people and email them a signing link, open the page's three-dot menu and choose **Send request**. ### Filter by group When the document belongs to groups, use **Groups** to narrow the completion view. You can combine this with status and search. ## Person detail view Open a person to start on **Workspace**. Review their details, groups, delivery status, current document progress, and recent activity. Select an outstanding request to open its details and activity. Use **Documents** for assignments and **Requests** for request history. To change their details or groups, click **Edit** beside their details or choose **Edit profile** from the three-dot menu. ### Documents tab The table shows each required document's status and **Next step**. Select a document to open **Document compliance** and review its requests and completed versions. For current assignments, you can also send a request or remind someone who still needs to sign. Open **Filters → Assignment history** to choose **Currently Assigned** or **Previously Assigned**. Previous assignments let you review history and download completed records. You can also filter by status. Previous assignments do not contribute to current progress. Their completed records remain available even after an assignment ends. Use **Add Document** to assign an existing document, or **Print** for a single-person report. Assignment alone does not send a request unless you enable the send option. The **Available to read** section lists published documents accessible through the person's groups. Those documents do not require completion and have no opening record. See [reading access](/guides/read-documents). ### Requests tab Review request status, sending and reminder dates, and delivery problems. Open an individual request's activity when you need its full history. ## Group compliance view Open a group and choose **People** to check what one person still needs, or **Documents** to check who still needs one document. Selecting a row opens a side panel without leaving the group. ### Compliance on the group documents tab Under **Requires a signature**, select a published document to open **Group compliance**. Search for a person or filter by status to see who has signed and who still needs to sign. Use **Send missing** when it appears to send this document's missing requests to group members. Searching or filtering the list does not narrow that send. **View document** opens the document page for more detail. Documents under **Available to read** show how many group members can read them in the signing portal. Opening a document is not recorded. A document without a published version shows **Not published yet**. ### Compliance on the group people tab Select a person to open **Group compliance** and see their required documents. Expand a document to review its activity. Use **Send request** beside a document when a new signature is needed. **Nudge** at the bottom reminds that person's eligible pending requests for documents in this group. On the **People** tab, **Send missing** sends missing requests across the group. See [send missing requests](/guides/manage-groups#send-missing-requests). Group progress counts only the documents required by that group. A person may be up to date here but still need to sign documents assigned elsewhere. ## Compliance progress on the documents list Document cards show the current version, draft status, groups, and completion count. Documents available to read show **Available to read** instead of a completion meter. ## Compliance progress on the people list Person cards show overall status and completion among assigned documents. Use filters to find specific needs. Color is a quick guide, not proof that every document is complete; check the count. ## Request statuses For exact meanings, see [completion statuses](/concepts/compliance). Request completion, current-document status, and delivery status answer different questions. ## Paper on file in compliance views Paper on file counts as completion for its revision. The **Paper on file** label identifies how it was completed. See [record a paper signature](/guides/record-paper-signature). ## Downloading a completion receipt Use the completed request's actions. See [download records](/guides/download-records). ## Activity history Select an outstanding request on a person or document workspace, or open **Activity** from a request's actions, to review and print its history. Choose **View activity** beside **Recent activity** to open the organization Activity page filtered to that person or document. See [activity history](/guides/activity-feed). # Update a document and request new signatures Source: https://docs.clearpolicy.app/guides/update-document Publish a new revision without losing earlier records, then send the updated document to people who need to sign again. Add a new revision when a published document changes. Earlier signatures stay linked to the version each person signed. **Who can do this:** owners and administrators. ## Publish the updated version 1. Open **Documents** and select the document. 2. Open **Revisions** and click **New Draft**. If a draft already exists, continue working on it. 3. Add the new content using the editor, an upload, or a cloud import. For a document based on an uploaded file, prepare the updated file and upload or import it into the draft. 4. Optionally fill in **What changed**. This note is for your team's revision history; it is not shown to people receiving the document. 5. Wait for saving or file processing to finish. To get feedback, [request review](/guides/review-document). Turn on **Require approval before publishing** if approval is required. 6. Click **Publish** when the draft is ready. If approval is required, every reviewer must approve the latest content first. While you edit a new draft, **Workspace** shows **Unpublished changes**. The current published version remains available until you publish the update. Use **Finish draft** to continue editing. The new revision becomes current. Previous published revisions and completed records remain available. ## Ask people to sign the update Publishing alone does not email people or cancel old requests. For a document with **Requires a signature** on: 1. Open **Compliance** after publishing. 2. Review the people who need the current version. Earlier completions may show **Outdated**. 3. Select a person to open the **Document compliance** side panel. 4. Use **Send request** in that side panel to send the updated version. To choose several people, open the three-dot menu on the document's **Workspace** or **Compliance** tab and choose **Send request**. Select the people in **To**, check the selected **Document**, preview the email, and send. See [send to one or more people](/guides/send-requests#send-to-one-or-more-people). The **Send requests** button at the top of the page does not resend to people with **Outdated** completions. It is for [missing requests](/guides/send-requests#send-missing-requests-for-a-document). You can also use a group's **Send missing** for eligible missing requests. When you send a new request for the same person and document, pending requests for older revisions are canceled. Completed, expired, and previously canceled requests stay in history. ## What if someone still has the old link? Before you send a replacement request, the old pending request continues to refer to its original revision. Completing it records a signature for that version, not the new one. After it is canceled by a replacement request, the old request cannot be completed. Ask the person to use the new email or their [signing portal](/guides/sign-document#use-the-signing-portal). ## Update a document available to read When **Requires a signature** is off, publishing a revision changes the file people can open through their groups. There is no signature request, availability email, or record of opening the document. See [make documents available to read](/guides/read-documents). ## Repeat signatures without changing the document You do not need a new revision for a recurring sign-off. Use [renewal](/guides/renewals) to ask people to sign the same published document again on a schedule. # Import documents from Google Drive Source: https://docs.clearpolicy.app/integrations/google Connect your Google Drive to import Google Docs and PDFs, and understand how Drive access differs from Google sign-in. Import a Google Doc or PDF from Google Drive when adding a document or updating a draft. ClearPolicy stores a copy; later edits in Drive do not automatically update it. ## Before you start You need an owner or administrator role to add documents, and access to the file in Google Drive. Each team member connects their own Google account. Supported files are **Google Docs**, converted to PDF, and **PDF files** stored in Drive. ## Connect Google Drive Open **Settings → Integrations**, find **Google Drive**, and click **Connect**. Sign in to Google and approve Drive access. You can also connect when prompted from the document picker. ## Import from Google Drive 1. Open **Documents → Add Document → More options** and choose **Pick from Google Drive**. 2. Select the file from your Drive. 3. Check the name and **Requires a signature** setting. 4. Submit the form. The new document is published; review it under **Revisions** before sending. For an existing document, open **Revisions** and work on a draft. Import the updated file there, review it, then publish. See [update a document](/guides/update-document). ## Sign in with Google **Sign in with Google** on the login page lets team members use their Google account to access ClearPolicy. Google sign-in and Drive file access are separate permissions. If imports ask you to connect Drive, complete that permission step even if you already use Google to sign in. ## Disconnect Drive Use the Google Drive disconnect action under **Settings → Integrations**. Disconnecting stops that connection's future imports; documents already imported remain in ClearPolicy. ## Troubleshooting * **The file is missing:** confirm the connected Google account can access it and that it is a supported type. * **Google asks for permission again:** reconnect Drive under Integrations and retry. * **The Google Doc is too large to export:** open it in Google Docs, choose **File → Download → PDF Document (.pdf)**, then upload the PDF to ClearPolicy within the upload size limit. * **The Drive version changed:** import it as a new draft revision in ClearPolicy; imported copies do not sync continuously. # Connect ChatGPT and Claude Source: https://docs.clearpolicy.app/integrations/mcp Authorize an AI assistant to work with your ClearPolicy organization, then use it for documents, people, requests, and product help. Connect ChatGPT or Claude to ask about your organization's documents and take supported actions in conversation. Each team member connects their own AI account through **OAuth**, signing in to ClearPolicy and approving access. This connection can act on your organization. The in-app **Support** assistant is for product help; see [get support](/guides/get-support). ## Before you connect * Sign in to ClearPolicy and select the organization you want the assistant to use. * Complete any setup requested during authorization. A person and a published document are needed before this connection can be authorized. * Your team role determines which actions are allowed. * Write actions require an active trial or subscription. ## Connect ChatGPT ![](/images/chatgpt-icon.svg) Install in ChatGPT Open ClearPolicy in the ChatGPT Apps library and authorize your organization. Open in ChatGPT Apps library → [Open](https://chatgpt.com/apps/clearpolicy/asdk_app_69eee2d237b881918747780ab313427d?utm_source=clearpolicy\&utm_medium=docs\&utm_campaign=docs_chatgpt_app\&utm_content=mcp_install_card) 1. Open the ClearPolicy listing in the ChatGPT Apps library. 2. Follow the installation prompts and sign in to ClearPolicy. 3. Check the organization shown and approve access. 4. Return to **Settings → AI assistants** in ClearPolicy to check the connection. ### Manual MCP setup If your ChatGPT plan supports custom MCP connectors, you can add one using the [connection details](#connection-details). Follow ChatGPT's current connector instructions; menu names and plan availability vary. ## Connect Claude 1. Open Claude's connector settings and add a custom remote connector, where supported by your plan. 2. Enter the ClearPolicy server URL from [connection details](#connection-details). 3. Follow the sign-in prompt to ClearPolicy, check the organization, and approve access. 4. Check **Settings → AI assistants** in ClearPolicy after connecting. For Claude Code or another MCP client, follow that client's remote HTTP and OAuth setup instructions. Configuration formats differ between clients. ## Connection details | Setting | Value | | - | - | | Server URL | `https://api.clearpolicy.app/mcp` | | Transport | Streamable HTTP | | Authentication | OAuth 2.0 | The client should open ClearPolicy for authorization. You do not need to create or paste a REST API token. ## Available actions | Area | Supported work | | - | - | | Documents | List documents, get details, add a rich-text draft, read revisions, update a draft, start a new draft revision, and publish a draft. | | People | List people, get a person's details, and add a person. | | Groups | List groups, get group details, and add an existing person to a group. | | Signing requests | List or inspect requests, send requests, remind people, and cancel pending requests. | | Documentation | Search product help and read specific documentation pages. | Document drafting works with editable rich-text content. These tools do not rewrite an uploaded PDF or Word document as rich text. Manage uploaded content in the app. Published revisions cannot be edited; start a draft revision first. Changes to a document's **Requires a signature** setting are made in the app, not through these tools. Review the proposed document and audience before confirming publishing, sending, reminders, or group changes. Adding a person to a group can create that group's automatic requests. The email follows within a minute. ## Example prompts ```text theme={null} Draft a volunteer code of conduct covering attendance, safety, and confidentiality. Leave it unpublished for review. ``` ```text theme={null} Who still needs to sign the employee handbook? ``` ```text theme={null} Find Alex Morgan by email alex@example.com and show me their document status. ``` ```text theme={null} Show me the outstanding requests for the safety policy before sending reminders. ``` ## Documentation and organization data The **Search docs** and **Query docs** actions use public product documentation. They do not look up a person's live status. The people, document, and signing-request actions provide organization data. The docs connection used by in-app Support is different from the product MCP server above. Connecting ChatGPT or Claude to ClearPolicy already includes the documentation actions; a second connector is not needed. ## Other supported AI tools Other clients need support for remote Streamable HTTP MCP and OAuth. Use the same server URL with the client's own setup instructions. If authorization reports an unsupported or invalid redirect, [contact support](/guides/get-support) with the client name and error. ## Subscription requirements Supported read actions and write actions have different access requirements. Adding people, editing or publishing documents, and sending requests require an active trial or subscription. Your team permissions still apply. ## Rate limiting Each OAuth token is limited to **120 requests per minute**. If the server returns `429 Too Many Requests`, wait for the interval indicated by `Retry-After` before retrying. ## Troubleshooting ### The connection sends me to setup Finish selecting or setting up the organization, add a person and a published document, and continue authorization. ### I added the server, but nothing happens Check that the client supports remote HTTP MCP and OAuth, and that connectors are available on your plan. ### OAuth failed or the wrong organization appears Sign in with the intended team member account and confirm the organization at authorization. Reconnect if the connection was authorized for a different organization. ### An action is unavailable or denied Check your team role and the supported actions above. The integration does not expose every action available in the app. ### A write action failed because of billing Open **Settings → Billing** in the connected organization and check its trial or subscription. See [billing help](/guides/manage-billing). # Import documents from OneDrive Source: https://docs.clearpolicy.app/integrations/microsoft Connect Microsoft OneDrive to import Word documents and PDFs from a personal, work, or school account. Import Word documents and PDFs from OneDrive when adding a document or replacing a draft's content. Imports are copies; later OneDrive edits do not update ClearPolicy automatically. ## Before you start You need an owner or administrator role to add documents. Each team member connects their own Microsoft account. Supported files are **PDF**, **`.doc`**, and **`.docx`**. Word documents are converted to PDF. Personal and work or school Microsoft accounts are supported. ## Connect OneDrive Open **Settings → Integrations**, find **OneDrive**, and click **Connect**. Sign in to Microsoft and approve file access. You can also connect when prompted by the document picker. If your work or school account requires administrator approval, ask your Microsoft administrator to approve access, then retry. ## Import from OneDrive 1. Open **Documents → Add Document → More options** and choose **Pick from OneDrive**. 2. Select the Word document or PDF. 3. Check the name and **Requires a signature** setting. 4. Submit the form. The new document is published; review it under **Revisions** before sending. To update an existing document, import the replacement into a draft revision, then review and publish. See [update a document](/guides/update-document). ## Sign-in vs OneDrive access **Sign in with Microsoft** authenticates a team member to ClearPolicy. **Connect OneDrive** grants file-import access. One does not automatically enable the other. You can use Microsoft sign-in without importing files, or import from OneDrive while using another daily sign-in method. ## Disconnect OneDrive Use the disconnect action under **Settings → Integrations**. Previously imported documents remain in ClearPolicy. ## Troubleshooting * **Administrator approval required:** contact your Microsoft administrator. * **The file is missing:** confirm you connected the account that can access the file and that it is a supported type. * **Access expired or was revoked:** reconnect OneDrive and retry. * **An updated file is not reflected in ClearPolicy:** import it into a new draft revision; there is no continuous content sync. # Sync Planning Center lists to groups Source: https://docs.clearpolicy.app/integrations/planning-center Connect Planning Center, bring people into ClearPolicy groups, and control whether new membership sends document requests. Connect a Planning Center list to a ClearPolicy group to bring its people into your document workflow. Changes flow from Planning Center to ClearPolicy, not back to Planning Center. ## Before you start * You must be the ClearPolicy organization **owner** to manage Planning Center sync. * Use a Planning Center account with access to the lists and people you need. * Sync requires an active ClearPolicy trial or subscription. * Review the target group's **Automatic request emails** setting. Adding people through sync can create eligible signature requests. The email follows within a minute. ## Connect a list 1. Open **Settings → Integrations → Planning Center**. 2. Click **Connect**, sign in, and approve the requested list and people access. 3. Open the sync settings and choose a Planning Center list. 4. Choose an existing ClearPolicy group, or let ClearPolicy use the list name for the group. 5. Click **Add List**, then **Save changes**. 6. Check the sync status and the group's **People** tab after the sync runs. ![Planning Center list-to-group selection in ClearPolicy sync settings.](https://mintcdn.com/ferviddigital/CsQQ2AL8EcUoeR5Q/images/planning-center-sync-add.png?fit=max\&auto=format\&n=CsQQ2AL8EcUoeR5Q\&q=85\&s=102d20875c2cf1ca7e4338e0aa7dedba) Choose a Planning Center list and the ClearPolicy group it should populate. ## What gets synced ClearPolicy brings in names, email addresses, available phone numbers, and membership in the connected group. People without an email are skipped. Existing people are matched by email within your organization, and their details can be updated from Planning Center. Sync adds people to the connected group. It does not automatically archive people or remove group membership when someone disappears from a Planning Center list. Review departures in ClearPolicy and [archive people](/guides/manage-people#archive-or-unarchive-a-person) when appropriate. ## Send documents to the group Add documents to the group and choose your sending approach: * With **Automatic request emails** on, new eligible signature assignments can send requests when people or documents are added. * With it off, use **Send missing** when you are ready. * Documents **Available to read** become accessible through group membership without request emails. See [manage groups](/guides/manage-groups). ## Manage existing syncs Use the sync settings to review status and last sync time. **Sync Now** requests another sync. Remove a sync to stop future updates from that connection; this does not delete the people or group already in ClearPolicy. ![Planning Center sync list with connected groups, status, and manual sync actions.](https://mintcdn.com/ferviddigital/CsQQ2AL8EcUoeR5Q/images/planning-center-sync.png?fit=max\&auto=format\&n=CsQQ2AL8EcUoeR5Q\&q=85\&s=9a3a94144fe0216cf9215db833edfad2) Review connected lists, status, and the last sync time. ## Troubleshooting * **I cannot manage sync:** ask the organization owner. * **The connection needs authorization:** reconnect Planning Center under Integrations and approve list access. * **A person is missing:** check that they are in the source list and have an email address. * **A list or group is unavailable to select:** check existing mappings; it may already be connected. * **No requests were sent:** check that the group has automatic emails on, the document is published and requires a signature, and the assignment is newly active. Use **Send missing** for existing gaps. # Automate work with Zapier Source: https://docs.clearpolicy.app/integrations/zapier Connect ClearPolicy to Zapier to find or add people, manage group membership, and send signature requests. Use Zapier to connect events in another app to actions in ClearPolicy. For example, add a new volunteer to ClearPolicy and a group when they appear in your roster system. ## Before you start Use an owner or administrator account and select the organization you want to connect. Complete organization setup, including adding a person and a published document, if authorization asks you to do so. API actions require an active trial or subscription. ## Connect Zapier 1. Open **Settings → Integrations** and click **Connect** next to Zapier. 2. Follow the Zapier setup and add a ClearPolicy connection. 3. Sign in to ClearPolicy and check the organization shown before approving access. 4. Return to Zapier and test the connection in your Zap. Zapier uses **OAuth**: you sign in and approve access rather than copying an API token. ## Available triggers **New person** triggers when a person is added to ClearPolicy. Use it to start work in another app. ## Available searches **Find Person** searches by email, person ID, or name. Prefer a full email for matching. Pair it with **Add Person** in Zapier's find-or-create flow when the person may not exist yet. ## Available actions | Action | What it does | | - | - | | **Add Person** | Adds a person with their name, email, and optional phone. | | **Add Person to Group** | Adds an existing person to an existing group. Group automation can send signature requests. | | **Remove Person From Group** | Removes membership. Existing signature assignments remain. Reading access granted by that group ends unless another group grants it. | | **Create document signing request** | Sends a published, signature-required document to a person. | ## Example workflow 1. **Trigger in your roster app:** a new employee or volunteer is added. 2. **Find Person:** search ClearPolicy by their email, adding them if needed. 3. **Add Person to Group:** use the person from the previous step and the appropriate group. 4. **Optional signing request:** send a specific document when group automation is not handling it. > [!NOTE] > > Check the group's **Automatic request emails** before testing a Zap. Adding group membership can create real document requests. The email follows within a minute. You usually do not need a separate signing-request action for the same document if group automation already creates it. ## Troubleshooting * **Wrong organization's data:** check the organization used to authorize the connection, then reconnect to the intended one. * **Person already exists:** use **Find Person** before **Add Person**. * **Document cannot be sent:** confirm it is published, active, and has **Requires a signature** on. * **Payment required:** check the organization's [billing status](/guides/manage-billing). * **Group change did not send a request:** review [group automation and existing assignments](/guides/manage-groups#automatic-request-emails). You can disconnect Zapier from **Settings → Integrations** when it no longer needs access. # ClearPolicy help Source: https://docs.clearpolicy.app/introduction Find the steps to send documents, collect signatures, give people access to policies, and track completion. ClearPolicy helps you get documents to the right people and keep a record of their signatures. You can also make published documents available to read in the signing portal without asking people to sign. ## What do you need to do? > [card] [Send your first request](/quickstart) > > Add a document and a person, send a request, and check completion. > [card] [Organize people into groups](/guides/manage-groups) > > Set up a shared set of documents and choose when requests go out. > [card] [Follow up on requests](/guides/manage-requests) > > Find unfinished requests, send reminders, and resolve delivery problems. > [card] [Make documents available to read](/guides/read-documents) > > Give people access through groups, without a signature request. > [card] [Sign a document](/guides/sign-document) > > Open your email link or use the signing portal. No team member account needed. > [card] [Get help](/guides/get-support) > > Ask the in-app assistant, request a human reply, or email support. ## A few terms to know | Term | Meaning | | - | - | | **Organization** | Your team's documents, people, settings, and records in ClearPolicy. | | **Team member** | Someone who signs in to manage work in your organization. | | **Person** | Someone you add to receive document requests or read documents. Adding a person does not give them team member access. | | **Group** | A collection of people who need the same documents. | | **Document** | A policy, form, or other document your organization manages. | | **Revision** | A version of a document. Requests refer to the version sent. | | **Document request** | A request for one person to sign one document. | | **Attestation** | The completion record retained when a request is completed. | New online requests collect a typed-name signature. An acknowledgment is the outcome: the person acknowledges your policy. Older records may show click-only acknowledgments. ## Connect your other tools Use [Planning Center](/integrations/planning-center) for people, [Google Drive](/integrations/google) or [OneDrive](/integrations/microsoft) for documents, and [Zapier](/integrations/zapier) for automations. You can also connect [ChatGPT or Claude](/integrations/mcp), or use the [REST API](/api/overview). See the [changelog](/changelog) for recent product updates. # Send your first document request Source: https://docs.clearpolicy.app/quickstart Add a document, add a person, send a signature request, and check completion in ClearPolicy. Start with one document and one person. The person receives an email link, reads the document, and types their name to sign. They do not need a team member account. ## Before you start Sign in to ClearPolicy and select your organization. You need an **Owner** or **Administrator** role, an active trial or subscription, and a PDF or Word document ready to send. **1. Add the document** Open **Documents** and click **Add Document**. Choose your PDF or Word file, check the document name, and leave **Requires a signature** on. Submit the form. ClearPolicy publishes this upload. Open **Revisions** to check the published file before sending it. To write a document instead, see [add and publish a document](/guides/create-document). **2. Add a person** Open **People**, click **Add Person**, and enter their name and email address. Save the person. Leave groups unselected for this first request. Adding a person by itself does not send an email or invite them to sign in as a team member. **3. Send the request** Open your document's **Workspace**. Open the three-dot menu and choose **Send request**. In the **Signature request** window, select the person in **To**. Your document is already selected in **Document**. Add an optional note in **Compose**. Open **Preview** to review the email, then click **Send**. This sends the person's signing link by email. **4. Check completion** Open **Requests** to check the request's status. After the person signs, open **Requests → By request → Completed** and choose **Download signed document** from its actions. The download includes the document and its electronic certificate. If the request is still outstanding, use **Nudge** to send a reminder. You can also open the person's or document's **Workspace** and select an outstanding request to review its activity. ## What happens next? * **The person cannot find the email:** check the address and [delivery status](/guides/delivery-failures), or share the [signing portal](/guides/signer-portal). * **You need to send to more people:** [create a group](/guides/manage-groups) or [import your roster](/guides/import-people). * **People only need to read:** use [Available to read](/guides/read-documents) instead of sending a signature request. * **You need a colleague to help manage ClearPolicy:** [invite a team member](/guides/add-team-members).