DocuSign: FAQs about the talent management integration

Integrating DocuSign with Enterprise workflows requires a Make a Change ticket and Enterprise configuration.

In the ticket, you must specify which workflows will initiate eSignature documents, such as candidate offer, assignment extension or assignment amendment. You must also designate which user role can manage documents, such as managed service providers (MSPs), program office users (PMOs) or suppliers. You can choose only one user role to manage documents.

Your ticket will be used to design the appropriate permissions for the user role you choose.

Adding client-defined fields (CDFs) to a DocuSign integration with talent management requires a separate Make a Change ticket and Enterprise configuration to set up your CDFs.

DocuSign is available as an add‑on solution to Enterprise. You can integrate DocuSign with your Candidate and Assignment workflows throughout Enterprise. You can initiate document eSignatures for any documents in your candidate and assignment workflow across all Enterprise modules: Contingent Staffing, Resource Tracking, and Services Procurement.

DocuSign for talent management supports three workflows: candidate offer (which includes onboarding), assignment extension and assignment amendment.

Code of ethics, confidentiality agreements, e-statements of work, and non-disclosure agreements.

Yes. You can use DocuSign for SOW and talent management eSignatures. However, you can designate only one user role to manage documents. For example, if you choose to have suppliers manage documents in your Services Procurement module, they must also manage documents for talent management.

Also, the email associated with your DocuSign account is the receiver of all DocuSign-related emails generated from Enterprise for talent management and SOW eSignatures. If you need to send responses to multiple users, use a distribution list for the email address.

Yes. When an eSignature document is initiated depends on how your workflows are set up. For example, by geography and industry or by contingent staffing and resource tracking. You will work with your Client Operations Manager to determine which approval steps in your candidate or assignment workflows will initiate an eSignature document.

Your approval workflow step settings override any choices selected when a template is made via self-service.

Each client defines when an envelope expires if action isn’t taken on the documents. Envelope expiration is configured in your DocuSign account. Contact your DocuSign representative for more information. When an envelope expires, it’s handled the same way as a rejected document.

When an envelope is rejected or expires, a task is generated that prompts the program office to review it. The program office user can resume the approval workflow step or reject it. Rejecting an approval step rejects all envelopes associated with the approval workflow step, even if one document is complete.

Enterprise leverages the frequency of reminders you set up in DocuSign. Contact your DocuSign representative for more information.

Yes, Enterprise leverages DocuSign’s feature to assign a signature to another user. Contact your DocuSign representative for more information.

If a different signer is set up in DocuSign, the delegate’s name displays on the completed document and on the eSignature Management tab in Enterprise. 

Currently, cultures and translations are not supported. Document templates must be created in the culture of the signers.

No. You need only one client administrator account to connect and test your integration.

Yes. Each time you select the View Signatory link, Enterprise pulls real-time document status from DocuSign via an API call. You can view real-time document statuses when you drill down to an eSignature Management tab in Enterprise. You can view real-time signatory statuses when you select View Signatories from the Action menu on an eSignature Management tab. Find out how under About real-time statuses.

Yes. eSignature-related fields are available in the eSIgnature Definition report. Learn more about gathering talent management analytics.

No. Your client administrator would need to cancel the envelope via your DocuSign account. That action updates the envelope status to Rejected.

When an envelope is rejected or expires, a task is generated that prompts the program office to review it. The program office user can resume the approval workflow step or reject it. Rejecting an approval step rejects all envelopes associated with the approval workflow step, even if one document is complete.

When an envelope is rejected or expires, a task is generated that prompts the program office to review it. The program office user can resume the approval workflow step or reject it. Rejecting an approval step rejects all envelopes associated with the approval workflow step, even if one document is complete.

If an envelope is expired, only your DocuSign administrator can delete or cancel an envelope.

A container that holds one or more documents associated with an approval workflow step used to initiate eSignature documents. A unique envelope is generated for each signatory. 

Here are some examples.

1. Assume a candidate has one document that requires three different sets of signatories. Three envelopes are created: one for each signatory.
2. Assume a has three documents that require one set of signatories. One envelope is created containing all three documents.

Yes. All envelopes created from a single workflow step are rejected, even if one of the envelopes was successfully signed. The eSignature tab will show Completed and Rejected statuses. A task will be created for the MSP so they can continue with the approval step or resubmit the action.

All signatories set up in your DocuSign account who are assigned to a document receive copies of the completed document.

Yes. You can view and download completed documents on the eSignature tabs in a Candidate or Resource Profile if you have the appropriate permissions.

Currently, you can view and download only one document/envelope at a time.

Completed documents attached and stored in Enterprise follow the data retention policy created for your organization by your Controller Admin.