It will be extremely time-consuming to utilize Pandadoc without this functionality, if possible at all.
​

Since we are relying on the Pandadoc API and Embedded Signing to integrate Pandadoc into our platform, we need to fulfill certain business needs. One of those needs is to allow for several users from a given organization the opportunity to sign a document. That means we do not know who from an organization will sign into our platform to make a signature.
​

What does that mean for our use of Pandadoc? Well, as I understand it, we need to create a document with a list of recipients -- one per role, or a list of recipient groups so that each role can have multiple emails/members attached. In theory, this should allow any one of those users from the recipient group to sign the document, which is the case, but only if they use the Pandadoc platform directly. Since we also wish to use the Embedded Signing, we need to use the API to get a token -- this is the point of failure for us. That API does not fetch a token for emails that are part of a recipient group.