Skip to main content

2 posts tagged with "signature-request"

View All Tags

One request or one per signer: when several people sign in your flow

· 4 min read
IgniSign Team
IgniSign Team

Sooner or later a flow in your product needs more than one signer. A lease needs the tenant and the landlord. An onboarding document goes to every new hire in a team. A policy update goes to each account admin. With the IgniSign API you list the signers on the signature request, and then you face one decision: should those people share one request, or should each of them get a request of their own?

One swipe or one by one: signing several documents in one request

· 4 min read
Julien Jenoudet
CEO of IgniSign

Many product flows ask a signer for more than one document at once: an onboarding contract with its data-processing annex, a mandate with a consent form, a set of terms that changed together. With the IgniSign API you can put them all in one signature request. The decision left to the integrating developer is how the signer gets through them: one document at a time, which is now the default for requests with several documents, or every document with a single swipe. This post is about that choice and what it changes in your backend.