Skip to main content

Agreement Settings

Agreement settings let you control how an agreement behaves during and after the signing process. You configure these before sending. Once an agreement is sent, most settings can't be changed.

Access settings from the Settings tab when preparing an agreement.

Markup​

Default: Off

When enabled, recipients can highlight text and add annotations to the document before signing. Markup is visible to all parties and sits on top of the original file, it doesn't change the underlying document.

When to use it: Use markup when recipients are reviewing a draft and you want them to flag questions or suggest changes without sending a separate document. Common in negotiation workflows where back-and-forth is expected before final execution.

Comments​

Default: Off

When enabled, recipients can post comments on the agreement. Comments are visible to all recipients and the sender, and are recorded in the agreement history.

When to use it: Use comments when recipients may have questions that don't require a change to the document, they can ask without stopping the signing process.

Recipient Document Visibility​

Default: Off

When enabled, each recipient only sees documents that contain fields assigned to them. In an agreement with multiple documents, recipients won't be shown documents where they have nothing to complete.

When to use it: Enable this when an agreement contains documents with confidential information that shouldn't be shared with every recipient, for example, when Document A is for one party and Document B is for another.

Responsive Signing​

Default: On (responsive layout enabled)

By default, the signing experience adjusts to the recipient's screen size, making it comfortable on phones and tablets. Toggling Disable Responsive Document turns this off and presents the document at its original fixed layout on all screen sizes.

When to use it: Disable responsive layout only when precise document formatting is critical and reflowing could cause confusion, for example, when column alignment or table structure has legal significance.

Envelope ID Stamping​

Default: Off

When enabled, the agreement's unique ID is printed on each page of the document as a watermark. The stamp appears on the final signed document.

When to use it: Enable this when you need a visible identifier on the physical document for filing, auditing, or legal reference.

Authoritative Copy​

Default: Off

Designates this agreement as the legally authoritative original. Only one authoritative copy exists, and its transfer must be performed through Propper.

When to use it: Use this for agreements where a single controlling document is legally required, for example, promissory notes or loan agreements under UETA or the ESIGN Act. → See Document Validity & Trust for how Propper's signing evidence holds up legally.

note

This setting has specific legal implications. Consult your legal counsel before enabling it.

Auto-Navigation​

Default: On

When enabled, the signing experience automatically scrolls to the next required tag after a recipient completes each action, guiding them through the document step by step.

When to use it: Leave this on for most agreements. It significantly reduces incomplete submissions by ensuring recipients don't miss required fields. Disable it only when recipients need to read the full document at their own pace before interacting with any tags.

Recipient Reassignment​

Default: On

When enabled, a recipient can reassign their signing responsibility to someone else. The substitute receives a new invitation; the original recipient is removed from the workflow. Reassignment is logged in the audit trail.

When to use it: Leave this on when recipients may delegate, for example, an executive who routes contracts to their assistant. Disable it when the identified recipient must personally complete the agreement and delegation isn't permitted.

Document Locking​

Default: Off

When enabled, the document is locked as soon as the first recipient completes their signing action. All subsequent recipients sign the same locked version.

When to use it: Enable this when document integrity between signers is a legal or compliance requirement, ensuring every recipient signs an identical version.