Signatures
Recipients and Roles
The six recipient roles, signer, approver, viewer, witness, CC, and in-person, and what each one can do.
Every recipient on an envelope has a role that decides what they must (and can) do.
The six roles
| Role | What they do |
|---|---|
| Signer | Fills and signs the fields assigned to them. The default role. |
| Approver | Reviews the document and approves or rejects. No signature fields required. |
| Viewer | Gets the document to read. No action required; their view is logged. |
| Witness | Attests to a signature. Signs alongside a signer as a witness. |
| CC | Receives a copy of the completed envelope. Informed, not a participant. |
| In-person signer | Signs on the host's device. For face-to-face signing sessions. |
What each role means in practice
- Signers get their own field set. The field builder color-codes fields per recipient so you always know whose box is whose.
- Approvers see an approve/reject decision with an optional note. The envelope pauses on their verdict in sequential routing.
- Viewers open the document through the same tracked viewer. Their read is in the audit trail and analytics.
- Witnesses countersign. The trail records them as attesting, not as a party.
- CC'd recipients get the sealed result when the envelope completes. They never see a signing screen.
- In-person hands the signing screen to someone physically present. The host's session drives, they sign on the spot.
Per-recipient options
- Verification. Require email verification (or stronger, where enabled) per recipient; a finance approver can face a stricter gate than a CC.
- Private message. A note shown to that recipient only.
- Language. The signing experience follows the recipient's locale where translations exist.
Editing recipients
While the envelope is a draft, everything is editable. Add, remove, reorder, change roles and verification. After sending, the list locks: fix mistakes by voiding and resending, or with the correction flow on active envelopes.