Converting a non-signable document to signable is a fast way to move from review to signature, but there are important limitations to be aware of. These limitations ensure that the document’s integrity and audit trail remain intact.
This article outlines what you cannot change during conversion and what behaviors to expect.
No Signing Order
When enabling signing on a previously sent non-signable document:
Signing order cannot be set.
All assigned signers will receive the signing link at the same time.
If you need sequential signing, you must create a new signable version instead of converting.
No Content Editing After Sharing
Once a non-signable document has been shared:
You cannot edit the document content before or during conversion.
Only signer roles, recipient details, signing methods, and metadata can be changed.
If content updates are required, create a new version and resend.
Document Type Cannot Be Changed Back
After converting to a signable state:
You cannot revert the document back to non-signable.
The document remains a signable contract version until completed or expired.
Signing Settings Are Limited
During conversion:
Only Viewer and Signer roles can be applied.
You cannot define advanced signing workflows or additional authentication flows beyond what is shown.
Sender signing can be toggled, but more complex settings are disabled.
Recipient Behavior Has Fixed Rules
Recipients behave differently during conversion:
If there is only one recipient, they are automatically assigned as the signer.
You can edit name, email, and signing method, but cannot add custom roles or multi-step permissions.
All recipients receive the signing email immediately after conversion.
No Template or Layout Changes
Conversion does not allow:
Swapping templates
Replacing layouts
Adding pricing tables or new blocks
Reapplying template logic
If these changes are needed, create a new version instead.
Activity History Is Locked
While converting preserves valuable context, it also locks in certain elements:
Analytics and timeline data cannot be transferred to a new document.
Conversion maintains the original audit trail, but cannot merge history with other versions.
Key Takeaways
No signing order is available when converting.
Document content cannot be edited after it has been shared.
Conversion keeps the same document and recipients but limits configuration options.
Use conversion for fast signing; use a new version for deeper changes.