With Conga Composer and DocuSign you can generate any document (Contract, Agreement, Application, etc.) and utilize DocuSign “In-Person Signing” to handle that requirement.

In-Person signing with Conga and DocuSign allows you to generate your document with Composer and pull up the DocuSign signature block on your device for signing in person via DocuSign.

Steps to Implement

  1. Enable DocuSign's Sign in Person Functionality by contacting DocuSign support directly.
  2. Create a Conga Solution record or create a new Conga button manually.
  3. Turn on the DocuSign Integration - This is done by adding &DocusignVisible=1.
  4. Add an in-person signing host, which is required for in-person signing sessions. The signing host must be an internal DocuSign for Salesforce user, and will be specified in the DocusignR1Id parameter. This can reference a static user id or merge the record owner or button's running user's record id.
  5. Add the DocuSign sign in person parameters - DocusignR1SignNow and DocusignR1SIPName.
  6. Add the Docusign role, type, and routing order parameters.
  7. Repeat these steps for additional sign in person recipients.

Example URL:

https://composer.congamerge.com
?sessionId={!API.Session_ID}
&serverUrl={!API.Partner_Server_URL_290}
&id{!Opportunity.Id}
&DocusignVisible=1
&DocuSignR1Id=00536000002tSDo
&DocuSignR1SignNow=1
&DocusignR1SIPName=John+Doe
&DocusignR1Type=Sign+In+Person
&DocuSignR1Role=Signer+1
&DocusignR1RoutingOrder=1
&DocuSignR2Id=00536000002tSDo
&DocuSignR2SignNow=1
&DocusignR2SIPName=Jane+Doe
&DocusignR2Type=Sign+In+Person
&DocuSignR2Role=Signer+2
&DocusignR2RoutingOrder=2


  • &DocusignVisible=1 --> Turns on Docusign Integration
  • &DocuSignR1Id=00536000002tSDo ---> This is the in-person signing host and is an internal Salesforce user &DocuSignR1SignNow=1 --> Enables Signing in Person for this signer &DocusignR1SIPName=John+Doe --> In Person Signer's Name
  • &DocusignR1Type=Sign+In+Person --> Specifies that this signer will be signing in person
  • &DocuSignR1Role=Signer+1 --> Standard first signer role value, which can be replaced with a custom signer role &DocusignR1RoutingOrder=1 --> Indicates this is the first signer in the routing order

A Docusign in-person signing session might continue after all sign-in-person recipients have completed signing the document. You might experience this when:
  • A sign-in-person recipient is immediately followed by a standard signer who should receive the agreement through email.
    • For example: &DocusignR1Type=Sign+in+Person and &DocusignR2Type=Signer
  • The sign in person host for the first, in-person signer and subsequent signer are the same user in Salesforce. For example: &DocusignR1ID=00541000000bK9y and &DocusignR2ID=00541000000bK9y.
    • To fix the issue, create a Contact record in Salesforce with the same name and information as the internal Salesforce user and reference the Contact record ID for the signer that follows the in-person signer.