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

# Add and 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 see:

* **Documents:** current and previous assignments, completion status, and documents **Available to read**.
* **Requests:** the person's request history and delivery status.
* **Settings:** their details, groups, and archive or delete actions.

## Edit a person's details

1. Open the person and select **Settings**.
2. Change their name, email address, or phone number under **Details**.
3. Click **Save**.

<Note>
  Saving a new email updates open requests for that person and sends them again to the new address. Completed requests keep the name and email they were sent with. Changing only the name updates open requests but does not send another email.
</Note>

## Change group membership

In the person's **Settings**, use **Add group** or remove a group, then click **Save** for that section. 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 **Settings** and use the archive action in the danger zone. You can also archive several people from the list.

Archiving removes the person from active lists and compliance counts, cancels open requests, and preserves completed records and request history.

Unarchiving returns the person to active lists. Send new requests if they need to sign again; unarchiving does not reopen canceled requests.

## Delete a person

Use **Delete** in the person's **Settings** only when you want permanent removal. If request history prevents deletion, archive the person instead.

An owner evaluating ClearPolicy with test records can use [reset trial data](/guides/reset-trial-data) while eligible.

## Fix email delivery failures

Open **Failures**, select the person, and click **Review**. [Retry the address or correct the email](/guides/delivery-failures) so open requests can send again.


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