DocuSign Integration

in nue, there are 2 different options for using docusign with nue — either via docid\ dg7 1mqzjgwigjay9exnx , or via nue’s docid\ i2uoxjkirteiel rez4ua the gen based approach relies on seat based docusign licenses and the https //www docusign com/products/gen package and licenses to generate and sign order forms directly from salesforce in contrast, the native integration uses nue’s own quote builder and order form generator to build documents — then sends them via docusign’s api under a single “integration user,” so you do not need individual seats or user licenses for every envelope sender and signer the result a lighter, more scalable e signature workflow that keeps everything inside nue and minimizes licensing complexity the following table shows a comparison of these 2 different approaches feature / requirement docusign gen for salesforce (gen) nue native docusign e signature integration document generation uses docusign gen templates (usually word or salesforce merged templates) tied to salesforce record data uses nue’s native quote builder + order form generator — templates and pdfs are built entirely in nue using the light weight, fully themable, drag n drop template builder where signing happens generated doc lives in salesforce; then sent for signature via docusign from salesforce built and sent directly from nue, using docusign api under a single integration user docusign licensing required seat based docusign esignature license + docusign gen license per seat/user only one docusign account with api access is required; no need for individual user seats for every signer signer licensing requirements with the docusign gen model, the licensing requirements apply to users who generate documents via docusign gen users who send envelopes users who need to view/manage envelopes inside docusign or salesforce access docusign admin or envelope management functions use advanced docusign features tied to licensed seats signing alone does not consume a seat signers (internal or external) receive email links and can sign via browser — no docusign license needed for them the only docusign license requirement is 1 api enabled docusign account (with api plan or enterprise plan that includes api access) used as the single “integration user” for all envelopes sent from nue best for organizations already fully embedded in salesforce and using salesforce focused document workflows this approach may be better if you have a stable, relatively small team of internal senders and want direct salesforce + docusign gen workflow teams wanting a simpler, scalable, seat license light workflow directly inside nue — especially when many signers are external or you want minimal per user licensing overhead this approach is better if you want to support many signers (internal + external), and scale based on envelope volume rather than user count now that you understand the differences between the two docusign integration approaches docusign gen for salesforce and nue’s native e signature integration you can continue to the documentation below to review setup steps, configuration requirements, and workflow details for each option this will help you choose the integration path that best fits your licensing model, technical needs, and internal processes docid\ dg7 1mqzjgwigjay9exnx docid\ i2uoxjkirteiel rez4ua