Skip to main content
Question

Advanced Web Form - Multiple Recipient/Collaborative Fields

  • May 20, 2026
  • 2 replies
  • 66 views

Forum|alt.badge.img

Hello, 

I am working on an Advanced Web Form that contains multiple recipients and needs Collaborative fields for two of the reviewers. The goal is to allow the Agent to begin the process and the Owner review and possibly update fields. All other recipients would simply be signing the form. I have a few issues. 

 

  1. When creating the webform from the template, an error is received that all recipients need a unique field. It does not register that some fields are collaborative. It does not account for Signature fields.
  2. Typically, with multiple recipients and collaborative fields, for PowerForms you set the fields to the last person in that signing order, so that if the fields are required, they are optional for all recipient prior to final signature. In this case, we’d want the Agent who is initiating the request to complete everything as optional, and then it be required for the owner. However, with AWF, all the fields have to be tied to the first recipient in the order.

Are there any suggestions to get this working the way business needs as a Webform experience?

2 replies

Forum|alt.badge.img+14
  • Community Moderator
  • May 26, 2026

Hello ​@PMills 
Thank you for reaching out, and welcome to the Docusign Community! Thank you for sharing the details of your workflow.
Based on the behavior you're describing, this is a current limitation of Advanced Web Forms rather than an issue with your template design. For Advanced Web Forms, each selected recipient must have at least one assigned data field (Text, Checkbox, Dropdown, or Radio field).

Signature and Initial fields alone do not satisfy this requirement, and collaborative fields are not recognized as a substitute for the unique recipient field requirement during Web Form creation. Additionally, Advanced Web Forms handles recipients differently than PowerForms.

While multiple recipients can edit collaborative fields in an envelope, the Web Form configuration still expects fields to be associated with the recipient who is designated to complete the Web Form experience.
As a result, the workflow you're looking for, where the Agent enters information as optional, and the Owner later becomes responsible for completing the same required fields, is not currently supported in the same way PowerForms can be configured.

Possible alternatives to consider:

• Configure both the Agent and Owner as Web Form participants, with separate fields assigned to each recipient.
• Use collaborative fields where appropriate, understanding that they do not bypass the Advanced Web Form recipient field requirements.
• Evaluate whether a PowerForm or a standard eSignature workflow may better support the business requirement if the Owner must be the final required completer of shared data fields.

If this workflow is critical to your business process, you may also want to submit it as a product enhancement request, as it would require functionality beyond the current Advanced Web Forms design.

Limitations and Considerations for Web Forms
Differences Between Web Forms and PowerForms

If you found the response to be a useful solution to your question, please “like” and mark it as the best answer by clicking “Select as Best” to make it easier for other users to find. Thank you!

Sincerely,

Ma. Cassandra | Docusign Community Moderator
If this helped, feel free to Like👍and click "Best Answer."


Forum|alt.badge.img+14
  • Community Moderator
  • June 3, 2026

Hello ​@PMills 

How are you? We'd like to know if my previous response addressed your questions. If so, we hope you could consider selecting it as Best Answer ✅," so others can find it too.

If you still require assistance, please don't hesitate to let us know. We are always happy to help!

 

Sincerely,

Ma. Cassandra | Docusign Community Moderator