Hello @alawless, 

Thank you for reaching out here, we want to welcome you to the DocuSign Community, I appreciate you bringing your question to this Community.

I apologize for the inconvenience, I understand that you want to know if there is a possibility to add additional DocuSign accounts in the integration between DocuSign & HighQ, so these users can indicate when sending the envelope who it is coming from.

This integration is not owned by DocuSign, we do not have the necessary information to provide you a proper reply.

Normally, when setting up an integration, all notifications and envelopes are based on the user who set it up. This creates a consent that provides permission to the user to act on behalf of the other users

If you want or need to separate the users, you would need to grant consent individually, so that each user can authenticate through the integration.

This would depend on the capabilities of the integration, a common scenario is that the Admin user would potentially need to change the way to get consent individually. 

You can get more information at OAuth JWT: Granting Consent (docusign.com) and How to obtain individual consent | Docusign

Note: Some advanced features and options are supported only in specific DocuSign plans. Your account plan might not support some options discussed in this help topic. Contact your account administrator for more information about which options are available for your account. Or, visit our Plans and Pricing web page for more details on the features included with your plan. Compare eSignature plans & pricing.

Let us know if you need further assistance.

Best regards,

Christopher | DocuSign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hi @alawless,

I hope you are doing well.

I would like to confirm if you need further assistance, feel free to let me know and I will gladly help you address the situation as soon as possible.

Best regards,

Christopher | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hi @Christopher.Alpizar and @alawless 

I am having the exact same problem with my DocuSign and HighQ integration. 

Was a solution found for your issue? and is there anything DocuSign can do to help?

Kind regards

George

Hello @George.Efstathiades,

Thank you for reaching out here, we want to welcome you to the Docusign Community, I appreciate you bringing your question to this Community.

I apologize for any inconvenience this might cause you, since the integration is not owned by DocuSign, we do not have the necessary information to provide you a proper reply. Only the information provided in the last post.

Let us know if you need further assistance.

Best regards,

Christopher | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

@George.Efstathiades 

Hi George, i picked up with HighQ separately about this and similar to what Christopher has said, it is owned by HighQ. There are a couple different ways you can set up the integration (whether you want each user to authorise the service individually, or a blanket authorisation by logging into the service once with a DocuSign service account), so we had a chat with our Client Success Manager from HighQ who pointed us in the right direction. Hope this helps :)

https://knowledge.highq.com/help/working-with-content/esign-electronic-signature-with-docusign

https://knowledge.highq.com/help/system-administration/advanced-docusign-and-adobe-acrobat-sign-configuration_1

as the document told:

If a service is authorised in System settings, you can send a document for signing on behalf of the system account. If a service is NOT authorised, a user can still send a document but must have their own eSigning service account.

maybe can try it.

@Hengfeng Ge @alawless appreciate both of your responses - we have been able to set it up. We now have the issue that it does co-operate with our DocuSign SSO. @alawless do have DocuSign SSO set up and if so were you able to communicate it with HighQ?

@George.Efstathiades we did not go down the SSO route sorry - we used a service account for blanket authorisation.