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

# The signing experience

> What your counterparty sees when they open a signing link: consent, the document, adopting a signature once for every block, and the executed copy they keep. Plus how to brand it as yours.

<div className="sr-only">For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.</div>

<Info>
  This guide is part of the [User Guides](/user-guides/overview) collection. It describes the portal from the *signer's* side, so you know what you are asking someone to do. For sending, read [envelopes](/user-guides/signature-envelopes).
</Info>

Your counterparty does not need a Coverbase account. They get an email, they open a link, and everything happens in their browser, on a phone as readily as a laptop. Nothing is downloaded and nothing is installed.

This page describes each screen they pass through, so you can tell which one a confused signer is looking at.

## What they see, in order

<Steps>
  <Step title="Prove the address, if you asked for it">
    Only when the envelope asks for it. **Authenticate signers' identity** sends a one-time code to the address the agreement was sent to; an **Access code** set on that recipient asks for the code you gave them out of band. Either way, signers who were not expecting it often report it as a broken link.
  </Step>

  <Step title="Agree to sign electronically">
    Your organization's ESIGN disclosure, shown in full. Nothing on the page is writable until they accept, and the exact text they were shown is stored with their acceptance.
  </Step>

  <Step title="Read and fill">
    The document, with their fields marked on it. Everything is saved as they go, so closing the tab loses nothing.
  </Step>

  <Step title="Adopt a signature">
    Once. It then applies to every signature, initials and stamp block that belongs to them.
  </Step>

  <Step title="Finish">
    A separate act from filling the last field. It commits the signature.
  </Step>
</Steps>

<Note>
  A party who opens their link before their turn sees the agreement but cannot act on it, with an explanation of who is ahead of them. They do not get an error, and they do not need to be told to come back later.
</Note>

## The document

<Frame caption="The signing portal. The document sits in the middle, the counter and Finish in the header, the tools down the right, and progress along the bottom.">
  <img src="https://mintcdn.com/coverbase/BmsawideriHgRw5S/images/user-guides/signing-portal.png?fit=max&auto=format&n=BmsawideriHgRw5S&q=85&s=dd39bafb7164829681acdc60f5f6776b" alt="Signing portal showing a document with filled and empty fields, a Next chip, the remaining counter, the right-hand tool rail and a progress bar reading six of seven done" width="2048" height="1280" data-path="images/user-guides/signing-portal.png" />
</Frame>

The header names the agreement, says **Review and complete**, and marks the page a **Secure signing link**. **Finish** sits at the top right and stays grayed out until nothing of theirs is outstanding.

The field outlines carry meaning, and it is worth knowing which is which when a signer describes one to you:

|                 |                                                                                                 |
| --------------- | ----------------------------------------------------------------------------------------------- |
| **Blue dashed** | Theirs, and still empty. These are what the counter is counting.                                |
| **Green**       | Theirs, and filled.                                                                             |
| **Grey dashed** | Not theirs, or filled by Coverbase. Those read **Fills automatically**. Nothing for them to do. |

Two things track how far along they are. The **N Remaining · Proceed** chip in the toolbar counts only the fields that still need them and jumps to the next one; the bar along the bottom reads *6 of 7 done* against every field they own. The **Next** chip is anchored beside the field they are on and skips anything Coverbase fills itself, so a signer is never sent to a box that refuses input.

Down the right-hand rail: **Summary** asks Coverbase to summarize the agreement, **Search** finds a phrase and marks it on the page, **Pages** opens a thumbnail rail, and **Download** and **Print** take a copy of what they are being asked to sign.

<Frame caption="Search marks each hit on the page and lists it with its page number and the sentence around it.">
  <img src="https://mintcdn.com/coverbase/BmsawideriHgRw5S/images/user-guides/signing-portal-search.png?fit=max&auto=format&n=BmsawideriHgRw5S&q=85&s=d0f1f83be67f941f06eb149829c46767" alt="Signing portal with the search panel open, a highlighted phrase on the page and a result listing the page number" width="2048" height="1280" data-path="images/user-guides/signing-portal-search.png" />
</Frame>

## Adopting a signature

<Frame caption="Adopt Your Signature. Draw with a finger or a mouse, or type a name and pick a style.">
  <img src="https://mintcdn.com/coverbase/BmsawideriHgRw5S/images/user-guides/signing-adopt-signature.png?fit=max&auto=format&n=BmsawideriHgRw5S&q=85&s=af07ce17d8f3ae86e811f95925341676" alt="Adopt Your Signature dialog with draw and type tabs, name and initials fields, and a style picker" width="2048" height="1280" data-path="images/user-guides/signing-adopt-signature.png" />
</Frame>

Which options appear depends on **Accepted Signature Types** in your signing settings: draw, type, or upload an image.

Two things about this come up often in support:

**One adoption covers every block.** A signer adopts once and Coverbase applies it to each signature, initials and stamp slot that belongs to them, wherever they are in the document. They do not initial each page separately.

**It is remembered.** Reopening the dialog shows the mark they adopted rather than a blank pad, so a signer checking their own signature does not have to redraw it. Drawing a new stroke replaces it.

<Frame caption="One adoption, applied to a signature, initials, a stamp and a second signature, each carrying the signer's name and recipient id.">
  <img src="https://mintcdn.com/coverbase/BmsawideriHgRw5S/images/user-guides/signing-portal-marks.png?fit=max&auto=format&n=BmsawideriHgRw5S&q=85&s=203185cab7497e5af0d60ff508689f56" alt="Document showing signature, initials and stamp blocks all filled from one adoption, each captioned with the signer name and id" width="2048" height="1280" data-path="images/user-guides/signing-portal-marks.png" />
</Frame>

Every mark is captioned with who applied it and their recipient id, on screen and in the sealed PDF. That caption is burned into the executed document, so it stays in English on screen even for a signer reading a translated interface. The page they approve has to match the page they receive.

## Finishing

**Finish** commits the signature. It is a separate act from filling the last field because ESIGN requires the signer to indicate intent, and filling a box does not do that on its own.

Beside Finish, a signer can also **decline**, which stops the envelope rather than skipping them, or **delegate** to somebody else if the agreement allows it.

<Frame caption="The confirmation screen, with the executed copy previewed beside it and the other parties' progress below.">
  <img src="https://mintcdn.com/coverbase/BmsawideriHgRw5S/images/user-guides/signing-portal-complete.png?fit=max&auto=format&n=BmsawideriHgRw5S&q=85&s=3def0c5cf771c46c323f2d2410af0852" alt="Completion screen showing fully executed, download and print buttons, who else is signing, and a preview of the signed document" width="2048" height="1280" data-path="images/user-guides/signing-portal-complete.png" />
</Frame>

The confirmation names what happens next: whether every party has signed or the agreement is still moving, and who is still to act. The link stays valid, so a signer can come back for their copy later rather than needing you to send it.

## Branding the portal

Two places control how the signing link looks to a counterparty.

<AccordionGroup>
  <Accordion title="Configuration → Signing Settings → Portal Branding">
    **Display name** is who the agreement appears to come from. **Reply-to** is where a signer's reply lands. **Portal message** is a short line shown on the signing page. Use it for a contact name, or to say which agreement this is part of.
  </Accordion>

  <Accordion title="Your organization's branding">
    The portal uses the logo and accent color from your organization's branding settings, so a signing link matches the rest of your branding without a second configuration. Set the logo there and it appears in the portal header.
  </Accordion>

  <Accordion title="Signing Emails">
    Your own wording for the invitation, the reminder and the completion notice. Leave a field blank and Coverbase's built-in copy is used.
  </Accordion>
</AccordionGroup>

## What to tell a signer who is stuck

<AccordionGroup>
  <Accordion title="I cannot click anything">
    They have not accepted the electronic signature disclosure. Nothing is writable until they do.
  </Accordion>

  <Accordion title="It says I cannot sign yet">
    They are not the current routing step. They will be emailed when it is their turn.
  </Accordion>

  <Accordion title="Finish is grayed out">
    A required field is still empty. The bar along the bottom says how many of their fields are done, and the **Remaining** chip takes them straight to the first one that is not.
  </Accordion>

  <Accordion title="It is asking for a code">
    Two different codes, and which one depends on the envelope. If **Authenticate signers' identity** was on, the code was emailed to the address the agreement was sent to. If you set an **Access code** on that recipient, it is the code you were meant to give them yourself. Resend it, or generate a new one on the envelope.
  </Accordion>

  <Accordion title="The document has not appeared">
    A Word source is still converting to PDF. The page resolves itself when the conversion lands; no refresh needed.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Sending for signature" icon="paper-plane" href="/user-guides/signature-envelopes">
    Create the envelope, set identity checks, and track what is out.
  </Card>

  <Card title="Signature templates" icon="file-lines" href="/user-guides/signature-templates">
    Field types, required and read-only switches, and the signer tooltip.
  </Card>

  <Card title="E-signature overview" icon="signature" href="/user-guides/signature-overview">
    Signing settings: consent wording, accepted signature types, and verification.
  </Card>
</CardGroup>
