The Sign Document Sub-task
The Sign Document Sub-task enables Dado to automatically generate and send a document for signature, using a range of eSignature providers.
Contents
- Pre-requisites for using this Sub-task type
- How the Sign Document Sub-task works
- How to set up a Sign Document Sub-task
- Troubleshooting Sign Document Sub-tasks
Pre-requisites for using this Sub-task type
- An account with an eSignature service
- An integration between the eSignature service and Dado
- Find instructions on integrating Docusign here. For other eSignature services, please contact our help@dadohr.com
How the Sign Document Sub-task works
Dado's Sign Document Sub-tasks use an integration with your eSignature service to create and send a document for signature.
In practice, the Sub-task works as follows
- Everyone who must sign the document should be assigned a task in Dado that includes the Sign Document Sub-task
- When the first of these Sub-tasks reaches its scheduled start date and time:
- Dado sends a task notification to the Task assignee, via the channels you've selected
- the eSignature service sends a signing request to the Task assignee, via the email address you specify
- When the assignee has signed and completed the document:
- their Dado task automatically completes
- if any Dado tasks/messages/automations are set trigger when this task completes, they now trigger
- Once the final signer has signed the document:
- the eSignature service sends the completed document to all signers, and any other recipients defined for that document
If your document requires multiple signatures, you have two choices:
- Sequential signing
- Set up the document in your eSignature service to require that the first signer has completed before the request is sent to the second signer (and so on for three or more signers)
- Set up a task for the first signer in Dado and a task for the second signer. Set the second signer's task to start when the first signer's task completes
- Simultaneous signing
- Set up the document in your eSignature service to permit the signers to complete the document in any order
- Set up the tasks for each signer in Dado, and set all tasks to start at the same time
How to set up a Sign Document Sub-task
Step 1: Create a template document in your eSignature service
Dado works with the template documents that exist in your eSignature service. So, the first step is to set up this template.
- Add fields to the document for any data that you need Dado to fill with data. Make sure to give those fields a unique, easy-to-understand label.
- Decide which signers and other recipients (eg people who receive a copy of the finished document) Dado should dynamically assign. For instance, you might want the signer to be the experience participant and their manager to receive a copy. Do NOT set up these signers/recipients as predefined people in your eSignature service – ie, don't say that the manager role should always be one particular employee.
- It's fine to have some recipients or signers pre-defined – but Dado will not be able to overwrite those assignments.
- Set a signing order, where the signers go first, and then the other recipients (eg people who receive a copy of the finished document). This helps avoid unnecessary notifications to other recipients
- Make sure this template is accessible by the Docusign Integration User. How to find out which user this is
Step 2: Add a Task and a Sign Document Sub-task
Get started by creating a Task, and then dragging the Sign Document Sub-task into the center section. This will open up the Sub-task settings in the right section
Step 3: Configure your template in Dado
Now it's time to set up your eSignature document template in Dado.
When you click the blue Set up template button in the right section, a new window will open.
First you'll be asked to choose a document template from your eSignature service.
The dropdown will include only the templates accessible to the Docusign Integration User in your eSignature service. That's the user account that set up the connection between Dado and your eSignature service – here's how to find out which account that is. If you don't see a document here that you expect, make sure it is shared with that user in your eSignature service.
After you've selected a template, the window will show you the configuration options for this template:
Signers
In this section, map the signers defined in your eSignature service to the relevant roles in your Dado experience; and select which email address should be used to notify them of the signature request.
If you have predefined the name and email address of any signers in your eSignature service, Dado will not be able to override these settings. This can occur when, for instance, the same individual always needs to sign a document on your organization's behalf. In this situation, you don't need to map the signer in Dado.
Every signer mapped in this section will need their own signing task in Dado
Data to be inserted
In this section you can define what data Dado already holds about employees will be automatically inserted into the document, before it is sent for signature.
For instance, you might have a form where you want to prefill as much personal data about the employee as possible, to make it easier for them to complete it.
The names of the fields in the eSignature service are the ones you set when you were setting up the template in Step 1.
Don't forget to select which role's data should be inserted. For instance, do you want to insert the full name of the Participant, or of their Manager?
Other Recipients
Your eSignature service may allow you to set other people to receive copies of the completed document, who are not required to sign it. In this section, you can map these other recipients to the relevant roles in your Dado experience; and select which email address the eSignature service should use to notify them.
If you have predefined the name and email address of any recipients in your eSignature service (eg to ensure the Finance team always gets a copy of a signed document), Dado will not be able to override these settings.
This section is fully optional: you do not have to map any other recipients to Dado roles.
Once you've finished configuring your template, click the Save button.
Step 4: Finish your Sub-task and Task settings
After you've configured your template, you will return to the Task window, where you will be able to finish setting up your Sub-task.
The Sign Document Sub-task has two parts:
- Instruction text, which you can edit in the right section
- Status tracker, which is not editable. This will automatically update when the eSignature service informs Dado that the document has been completed by the assignee of this Sub-task.
- Note: this status relates only to the assignee of this Sub-task. If a document requires two signers, and this Sub-task is assigned to the first signer, the status tracker will update as soon as the first signer has completed the document. The status of other signers are irrelevant.
Step 5: Set up Tasks & Sub-tasks for other Signers
Now set up a Dado Task containing a Sign Document Sub-task for every other signer that you've mapped in the Template Configuration Settings.
You need a Task and Sub-task for every signer who is not predefined in your eSignature service. For instance, your organization's policy might be that the CFO signs every employment contract on the company's behalf. So you've pre-defined the CFO's name and email for this signer, in your eSignature service. You do not need a Task and Sub-task in Dado for the CFO.
If you do not have a Task and Sub-task for every signer mapped in the Template Settings, Dado will not be able to create and send the document for Signature.
Sequential or simultaneous tasks?
If your document requires multiple signatures, you have two choices:
- Sequential signing
- Set up the document in your eSignature service to require that the first signer has completed before the request is sent to the second signer (and so on for three or more signers)
- Set up a task for the first signer in Dado and a task for the second signer. Set the second signer's task to start when the first signer's task completes
- Simultaneous signing
- Set up the document in your eSignature service to permit the signers to complete the document in any order
- Set up the tasks for each signer in Dado, and set all tasks to start at the same time
Step 6: Save your Tasks and your Experience
As always, don't forget to save the Tasks you've just created, and then save the overall Experience.
Troubleshooting the Sign Document Sub-task
Errors that prevent the signature process completing
A few things can go wrong that would prevent the successful completion of the Document signature
Problem | Solution |
Dado cannot access the template in your eSignature service | Check the access settings for this template in your eSignature service. If the template has been deleted, you'll need to set up a new template; configure it in Dado; and then connect it to your existing Sub-tasks. Retriggering any Tasks which have already started is slightly more complex. We recommend you contact help@dadohr.com who will do this for you. |
You have mapped 2 signers in the Template settings, but only one of them has a Sign Document Sub-task. Dado therefore is unable to create and send the Document for signature |
Add a Task and Sub-task for the other signer, and save your Experience. Retriggering any Tasks which have already started is slightly more complex. We recommend you contact help@dadohr.com who will do this for you. |
In an individual employee's experience, a role is not filled, and that role should be a signer or recipient of the document EG an employee's manager is not defined, and they are supposed to be tasked with signing a letter. |
Assign the missing role in this employee's experience, then retrigger the task. |
Someone who should be a signer or recipient does not have an email address set in Dado For instance, an employee's work email address is blank, and this address should be used for the signature request. |
Add the missing email address, then retrigger the task. |
Docusign is sending unwanted notifications at the start of the signature process
Sometimes, Docusign will send a notification at the very start of the signature process to a recipient set up to Receive a Copy of a document. This notification contains a blank version of the document to be signed, and no extra information on who will sign it. This can be very confusing to the recipient!
The notifications sent by Docusign are controlled in the Docusign admin interface, not in Dado. So you'll need to log in to your Docusign account to remove this notification.
To prevent Receive a Copy recipients receiving this initial notification (with the blank, unsigned document):
- Log in to your Docusign admin interface, and navigate to the Templates section
- Select the template you wish to change, and click on it
It may be easier to find the template if you first select All templates in the left column
- Click on the Edit button at the top of the screen
If you do not see this button, you do not have edit permissions for this template. Please find someone who does, and ask them to follow these instructions
- On the new screen, scroll down until you find the Recipients section.
- Check the Set signing order checkbox, if it is not already checked
- Now rearrange the recipients, so all Receives a copy recipients are at the bottom of the list
- Finally, click the Save and close button on the bottom right
- Remember to do this for all templates you wish to change.