> ## 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.

# How people use the signing portal

> People can open the signing portal with a one-time email code—no team member account—to finish pending requests and review signed documents.

People do not need a ClearPolicy team member account to sign. Each request email still includes a personal link that opens that document directly. When someone loses an email, has several requests waiting, or works with more than one organization at the same address, they can open the **signing portal**, verify their email with a one-time code, and see **Documents**: everything still pending and everything they have already signed.

## When to point people here

Share the signing portal when someone:

* Cannot find the original request email or reminder
* Has more than one pending request and wants a single place to finish them
* Receives requests from more than one organization at the same email address
* Lands on the team **Log in** or **Register** page by mistake (they should not create an organization account just to sign)

You can still [send a reminder](/guides/reminders) for a specific request. The personal link in that email always opens that request.

## How people open the signing portal

1. Go to [app.clearpolicy.app/signer](https://app.clearpolicy.app/signer), or click **Here to sign a document?** on the team log in or register page.
2. Enter the **email address** where they receive document requests.
3. Check that inbox for a **6-digit code** and enter it on the next screen.
4. After the code is accepted, they see **Documents** — pending and signed requests for that email.

No password and no team member account are required.

<Note>
  For privacy, ClearPolicy always shows the code entry step after someone submits an email. A real code is sent only when that address matches at least one person in ClearPolicy. Wrong or expired codes use the same error path either way.
</Note>

## What people see

The **Documents** screen is grouped by **organization**. Within each organization, people can filter with **All**, **Pending**, and **Signed**.

| Tab         | What appears                              |
| ----------- | ----------------------------------------- |
| **Pending** | Open requests they still need to complete |
| **Signed**  | Requests they have already completed      |
| **All**     | Both, in the same organization groups     |

Expired and canceled requests do **not** appear. Only actionable pending work and completed history show up.

### Pending requests

Each pending row shows the document name and due date when request expiry is set. Clicking **Sign** opens the same attestation page used from the email link. The person reads the document, types their name, and submits.

If they already verified their email in this browser, the attestation page can include a **Documents** control so they can return to the signing portal after signing. ClearPolicy does not force them back automatically.

### Signed requests

Each signed row shows when the request was completed. **Paper on file** appears when a team member recorded a paper completion instead of an online signature.

**View document** opens the completed request so the person can review what they signed. Completed requests remain viewable even after the original expiration deadline has passed. For online completions, the completed page still offers the downloadable receipt (certificate) when available. Paper completions do not offer a person-facing electronic certificate download.

## Email link vs signing portal

| Path                                           | Best for                                                        |
| ---------------------------------------------- | --------------------------------------------------------------- |
| Personal link in the request or reminder email | Opening one specific document right away — no code required     |
| Signing portal at `/signer`                    | Finding all pending and signed work for that email after a code |

Both paths use the same signing experience. The signing portal is optional re-entry, not a replacement for request emails.

## Session and log out

After a successful code, the person stays signed in to the signing portal for a limited time while they are active. They can click **Log out** in the header at any time to end the session immediately on that browser.

If the session ends, they enter their email again for a new code.

## What to tell people (support copy)

You can send language like this:

> Open [app.clearpolicy.app/signer](https://app.clearpolicy.app/signer), enter the email where you get our document requests, and use the one-time code we send. That’s the signing portal—you’ll see everything still pending and anything you’ve already signed. No ClearPolicy account needed.

If they never receive a code, confirm you are using the same email on their person record and that a request was sent to that address. You can [send a reminder](/guides/reminders) or a [new request](/guides/send-requests) from ClearPolicy as needed.

## Related

* [How attestations work](/concepts/attestations) — signing page, records, and request status
* [Send requests](/guides/send-requests) — how request emails and personal links work
* [Request expiry](/guides/request-expiry) — deadlines for unfinished requests
* [Reminders](/guides/reminders) — follow up on a specific open request