Docusign (Docusign enabled)

Kyloe AwesomeDocs can be integrated with Docusign. The below settings enables Docusign as an option and what should happen to the signed document. To add default recipients for your template you can do this under the Recipients tab.

To be able to see the option to send a Kyloe AwesomeDocs document to Docusign in Bullhorn, the Docusign Enabled option should be checked.

Screenshot of the DocuSign tab.

1. Docusign Enabled: Checking this will enable the Docusign functionality for this template. Without this checked none of the other settings in this tab will apply.

2. Signing Order Enabled: Checking this will ensure that the document will work through the listed recipients in order. It is recommended for all templates.

3. CC follows signing order: In some cases Recipients may be included that are not required to sign/interact within Docusign. These are treated as CC recipients by Docusign. Checking this box will ensure that any CC recipient will receive the document at the point of the signing process they have been placed. If this box is not checked, the CC recipients will receive the document before any signing has taken place.

   NOTE: It is recommended that all three of Enabled boxes are checked by default.

4. Sending on behalf of is used to capture the sender of the document to Docusign's details and email address.

   1. If this option is left blank then all Docusign emails will appear to have been sent from the Docusign admin account used during your Kyloe AwesomeDocs implementation.

   2. If an email address is entered here then the Docusign emails will appear to come from that particular user, e.g [e-mail]. 'corporateUser' can be entered here. This will use the email address stored against the user's Bullhorn account.

      NOTE: Any email address entered here, or against a Bullhorn user, must exist within your Docusign account. If it does not match then the AwesomeDoc will not send and an error will be displayed.

5. Docusign account ID to use: If this is left blank then the master Docusign account will be used. If you have multiple Docusign accounts for your organisation you can enter the specific ID / account identifier for any other Docusign account you wish to send documents through for this specific template.

   NOTE: Please contact Kyloe Support for assistance if you wish to enable the option for multiple Docusign accounts.

6. Brand: If you have specific branding created within your Docusign account, you can select it from the drop-down list here.

7. Template: Select the Docusign template that you wish to use with the AwesomeDoc from the drop-down list. If you select a template you will be asked to enter a position ID. This is the document position in the Docusign template that the AwesomeDoc will replace within the Docusign template. Generally we suggest adding a blank page to your Docusign template where you want the AwesomeDoc to be inserted.

   NOTE: If you only want to use AwesomeDocs to trigger the sending of a Docusign template enter the value: 0

8. Entity to save back to: By default, the signed AwesomeDoc will be returned to the Files tab of the entity record from which it was raised. However, you can select a parent entity (if applicable). This will store the returned document on that entity instead, not as well as.

9. Note type: Enter a valid Bullhorn note type here to create a note against the entity record in Bullhorn each time the template is sent to Docusign. This note will contain a link directly to the Docusign envelope.

10. Signed Update: When the signed document is returned from Docusign to Bullhorn it is possible to update Bullhorn fields with fixed values. An example script is provided here but please contact Kyloe Support for more information.

DocuSign will apply a Reminder period and Expiration date to Docusign envelopes sent through the AwesomeDoc integration. These settings are based on the Reminder and Expiration settings in the Docusign account used for the integration.