Skip to main content

Settings

Configure Sign preferences for your organization. Changes apply immediately to new agreements unless noted otherwise.

Go to Settings from the navigation to access all configuration options described here.

Signing options​

Control the default behavior when recipients sign documents.

Document behavior​

SettingDescription
Auto-navigationAutomatically moves the signer between required tags so nothing is missed
Allow reassignmentRecipients can delegate signing to another person
Allow markupRecipients can add highlights and text annotations before signing
Agreement ID stampingAdds the agreement's unique ID to each page of the document
Signer visibilityRecipients see only the tags assigned to them, not tags for other signers
tip

Auto-navigation is recommended for documents with many tags — it significantly reduces incomplete submissions.

Authentication defaults​

Set the default authentication method applied to new agreements. This can be overridden on a per-recipient basis when creating an agreement.

Available authentication methods:

MethodHow it works
None (email link)Anyone with the signing link can access — simplest, no extra step for the recipient
Email OTPOne-time code sent to the recipient's email address
SMS OTPOne-time code sent via text message to the recipient's mobile number
Access codeSender provides a code that the recipient must enter — shared through a separate channel
TOTPTime-based code from an authenticator app
Identity providerThird-party identity verification (OneID, ID.me, Clear)

See Authentication for a detailed comparison and setup instructions for each method.

tip

Use email link authentication for routine agreements. Enable SMS OTP or access code for sensitive documents, high-value contracts, or any agreement where stronger signer verification is important.

Branding​

Customize the signing experience with your organization's logo and colors. Your brand appears in invitation emails, the signing page, and completion certificates.

RequirementDetail
Supported formatsPNG, JPG, SVG
Maximum file size2 MB
Recommended dimensions200 × 60 px
note

Custom branding availability depends on your account plan.

Colors​

  • Primary color — buttons, links, and interactive elements
  • Background color — signing page background
  • Text color — headers and body text

Ensure sufficient contrast between foreground and background colors for accessibility. Test your branding on both desktop and mobile before sending to recipients.

For detailed branding configuration including logo, colors, and email templates, see Custom Branding.

Coming Soon

Screenshot: Branding settings panel showing logo upload and color configuration

API access​

API keys​

Generate API keys to use the Sign API for programmatic agreement creation, status polling, and webhooks.

  1. Click Generate New API Key.
  2. Give the key a descriptive name (for example, "Production" or "CRM Integration").
  3. Copy the key immediately — it is shown only once.
  4. Store it in an environment variable or a secrets manager.
danger

Never commit API keys to version control. Rotate keys regularly and revoke any key that may have been exposed.

See the Sign API documentation for available endpoints, request formats, and response examples.

Webhooks​

Webhooks deliver real-time notifications to your system when agreement events occur.

Setup:

  1. Enter your webhook endpoint URL (must be HTTPS).
  2. Select the events you want to receive.
  3. Click Save.

Available events:

EventWhen it fires
agreement.sentAgreement is dispatched to recipients
agreement.viewedA recipient opens the agreement
agreement.signedA recipient completes signing
agreement.completedAll recipients have signed
agreement.declinedA recipient declines to sign
agreement.voidedThe agreement is voided by the sender
agreement.expiredThe agreement expires before all parties sign

Delivery behavior:

  • Propper retries failed webhook deliveries with exponential backoff
  • Each request includes an X-Propper-Signature header for payload verification
  • Webhook endpoints must respond with a 2xx status within the timeout window
Testing

Use webhook.site to inspect webhook payloads during development before pointing to your production endpoint.

note

The specific payload structure for webhook events is documented in the Sign API reference. Refer to the API documentation for the authoritative payload schema.

Roles and permissions​

Roles and permissions for Sign are configured at the organization level through platform settings, not within Sign itself.

To manage team member access:

  1. Go to Organization > Members.
  2. Select a member to adjust their role and permissions.

Access levels control which agreements and templates a member can create, view, and manage. Contact your organization administrator to update permissions.

Advanced settings​

In-person signing​

Enable in-person signing to facilitate face-to-face signing sessions where the sender and recipient are physically present together. The sender manages the device and the recipient signs directly. The full audit trail is maintained.

Useful for retail, branch office, and event scenarios. See In-Person Signing for setup details.

Completion certificate​

A completion certificate is automatically generated for every completed agreement. It includes:

  • Full signing timeline with timestamps
  • All recipients listed with authentication method used
  • SHA-256 document hashes for tamper-evidence verification
  • Cryptographic proof of integrity

The completion certificate is always generated — there is no setting to disable it. See Completion Certificate for details on what it contains and how to download it.

Audit trail​

A tamper-evident audit trail is recorded for every agreement regardless of account type. The audit trail captures all participant actions, IP addresses, authentication events, and document hashes.

To view the audit trail: open an agreement > Audit tab.

See Audit Trail for a full explanation of what is tracked and how the hash-chaining works.

Data retention​

How long signed agreements and audit records are retained is an organizational policy decision. Your legal or compliance team should define retention schedules based on applicable regulations, industry requirements, and document type.

Ensure your document management and storage practices align with your legal team's retention requirements.

note

Some industries — healthcare, financial services, legal — have mandatory minimum retention periods defined by regulation. Consult your legal counsel to determine the correct retention schedule for your documents and jurisdiction.

Saving changes​

Click Save Settings after making changes. Settings apply immediately to new agreements.

note

Branding updates may take up to 5 minutes to propagate across all signing sessions.