Update Counterparty Signer fields AFTER reassignment and signature in Docusign

jeremy_ball

Hi, we've got a request from the business to allow/automate updating the Counterparty Signer Name (and email, et al) AFTER the original CP signer on the workflow has forwarded the Docusign envelope to the actual signer and the signed document is returned to Ironclad.

At this point, for us, the stage has advanced to Archive, and the properties are locked - is there a Docusign integration setting that we can adjust to get those fields corrected when the CP Signer Name has changed?

Thanks!

Quinn Hare

Thanks for the detailed writeup — this comes down to how the envelope got to the actual signer, since that determines whether Ironclad can see the change.

Why this happens: If the original Counterparty Signer used DocuSign's Other Actions → Assign to Someone Else to hand off the envelope, Ironclad tracks that as a formal reassignment — it logs it in the Activity Feed, and once the new signer completes signing, Ironclad automatically updates the Signer Name and Email properties to match. But if the envelope was simply forwarded (e.g., the email/link passed along outside that flow), DocuSign never tells Ironclad a substitution occurred, so the workflow properties stay exactly as they were at launch — including after Archive.

Since your fields show the original signer's info even after the correct person signed, that suggests the forward happened outside the official reassignment flow. Two things to check:

1. Going forward: Have your Counterparty Signers use Other Actions → Assign to Someone Else inside DocuSign rather than forwarding the email directly. That's what triggers Ironclad's automatic field update on completion.
2. For records already in Archive: You may still be able to correct the Signer Name/Email fields manually via View and edit properties on the workflow — edits at Archive are supported and get tracked in the Activity Feed. The one thing that would block this is if those specific properties are configured as Locked in the configuration — locked fields can't be edited by any user, regardless of role, only through an external source like a Salesforce integration. Worth checking your Signer Name/Email property configuration to confirm they aren't set to Locked.