This is absolutely a critical feature for anyone integrating Pandadoc into their platform.
Currently, if a platform wished to support multiple users from one organization to be eligible to sign a document via the embedded signing tool, they would need to use another product.
Pandadoc API supports creating a document with recipient groups, and yet the same API does not allow the creation of a signing session for a user with an email in those same recipient groups.
Many organizations have multiple authorized signers, no? And if a document has more than one organization to sign a document, then it is likely at least one of those organizations requires the use of a recipient group when creating the document. For Pandadoc integration, the use of recipient groups in tandem with the embedded signing is critical as we cannot predict who will ultimately do the signing from a given organization.
Lucas Allen
supported this idea
·
This is absolutely a critical feature for anyone integrating Pandadoc into their platform.
Currently, if a platform wished to support multiple users from one organization to be eligible to sign a document via the embedded signing tool, they would need to use another product.
Pandadoc API supports creating a document with recipient groups, and yet the same API does not allow the creation of a signing session for a user with an email in those same recipient groups.
Many organizations have multiple authorized signers, no? And if a document has more than one organization to sign a document, then it is likely at least one of those organizations requires the use of a recipient group when creating the document. For Pandadoc integration, the use of recipient groups in tandem with the embedded signing is critical as we cannot predict who will ultimately do the signing from a given organization.