Every signer managed.
Every identity captured.

Each signer gets added with name and email address. The platform validates the email format, captures the signer's name for use throughout the document, and queues the signing invitation. Multiple signers can be added at once for multi party contracts. Each signer is captured as a separate record with their own audit trail, so identification stays clean throughout the signing process and afterward in the contract history.

Each role behaves differently in the signing flow. Signers are the full signing party who must complete signature fields. Approvers need to approve the document but don't sign anything, useful for internal sign off chains where approval matters but signature does not. Acknowledgement recipients confirm receipt of the document, which works for policy distribution and internal communications where the team needs to know everyone has seen the content but no formal signature is required.

Each signer can receive a custom message with their signing invitation. The message appears in the invitation email and at the top of the signing experience. Different signers can get different messages for the same contract, so the legal counsel receives one context, the client another, the internal approver a third. Custom messages can also be updated when resending invitations, so the context refreshes for stalled signers.

When a signer hasn't opened the original invitation or needs another push. The email might have been missed, caught in spam, or arrived at a busy moment for the signer. One click resend pushes the invitation again, with an optional updated custom message that often unsticks the signer where the original failed. Resends preserve the original invitation in the audit trail so the full history of contact attempts is visible.

Identity beyond just email plus signature. IP address and geolocation captured at the moment of signing show where the signer physically was when they signed. Combined with timestamp, signing method, and the signer's name and email, this creates legal proof of identity that holds up in audits and disputes. If somebody later claims they didn't sign or someone else signed on their behalf, the captured evidence shows when and from where the signing actually happened.

Recipient Management defines who the signers are. Signing Workflows defines how the signatures get collected. Recipient Management handles signer setup, roles, messages, and identity capture. Signing Workflows handles whether the document moves sequentially, in parallel, through approval chains, or in any other workflow pattern. Recipient Management applies the same way across every workflow type, so the team's signer setup is consistent regardless of which workflow the contract uses.