Signing experience
The Propper Sign signing experience provides a secure, guided interface for recipients to review and sign documents. Whether signing via email link, embedded within your application, or in-person on a shared device, the process guides recipients through required tags and signatures.
Screenshot: signing-experience-overview
Signing methods
Choose how recipients access documents:
- Email signing — Recipients click a secure link in their email to sign in their browser. No account required.
- Embedded signing — Integrate the signing experience directly into your application. Your backend creates a signing session and presents the URL in an iframe or redirect flow.
- In-person signing — A host facilitates face-to-face signing on a shared device, ideal for retail locations or branch offices.
The signing process
- Authentication — Recipients verify their identity using the authentication method configured for the agreement.
- Review — Recipients view all documents in the agreement along with their required tags.
- Navigate — Auto-navigation guides them through required tags in order.
- Sign — Recipients adopt a signature and apply it to designated signature tags.
- Complete — Recipients receive confirmation and an emailed copy of the completed document.
Auto-navigation
The signing interface automatically moves recipients from tag to tag, ensuring nothing is missed. Recipients can also navigate manually or scroll freely through the document. Optional tags can be skipped.
Tag validation
Required tags must be completed before signing can be submitted. Format validation ensures data like email addresses and dates are entered correctly. The interface clearly shows remaining required tags and overall progress.
Multi-document support
When agreements contain multiple documents, recipients navigate between them with visual indicators showing which documents still require attention.
Security and compliance
All signing sessions are:
- Encrypted in transit and at rest
- Tracked with complete audit trails
- Compliant with eIDAS, ESIGN Act, and UETA standards
Signing sessions expire after 7 days. Recipients who return to the signing link within that window can resume where they left off. Agreement expiration (the deadline for all recipients to complete signing) defaults to 30 days and is configured when creating the agreement.
Next steps
- Configure authentication requirements for identity verification
- Learn about the signature types available to signers
- Understand how email signing works for remote recipients
Related topics
- Sending Agreements — Prepare and send documents for signing
- Tag types — Available tags you can place on documents
- Status tracking — Monitor signing progress