Any guidance appreciated. Sorry if I'm being dense. The description and use case for this new feature is as follows and the bit I have emboldened made me take notice because getting a signer email up front in the launch form can be difficult and does cause friction, but made me ask the question, how does the signer get the signature packet if they're only adding their email at signature?
Or is it just confirming the data to be captured at that point? I'm pretty sure currently even if the signer ends up being delegated, the signer email that is captured is the one that signs.
Just unsure what the use case is here - it sounds like it could be really useful. Thanks
| Description |
Users with access to Workflow Designer can now assign a signer to boolean and email properties. Once assigned, the information provided by the signer will be captured as metadata and used in Ironclad Repository, Insights, and more. This is available for Ironclad Signature, and supported 3rd party eSignature providers.
|
| Use Case |
An Ironclad admin is building a workflow and wants to capture their signers’ emails and sync them back to their CRM where they maintain their contract's record. To optimize the signer's experience, the admin wants to capture the email when the signer is signing rather than in the launch form
|
