Skip to main content

    Filter by Idea status

    Filter by category

    1117 Ideas

    Mcbmbr24Newcomer

    HAVING CAPABILITY OF MODIFYING OR ADDING ENVELOPE NAME IN POWERFORMSIdea Submitted

    I’d like to suggest an important enhancement for PowerForms in DocuSign: Having the capability modifying the “SUBJECT LINE/ Envelope Name” field so sender can customize the envelope name (So they can add the project name or Clients/Company name) before sending. Currently, when multiple PowerForm templates are used, all envelopes are sent with the default title “PowerForm Template>>>>XYZ.” I know that there is a way of adding the recipient name or email address to the subject line. However, there are many contracts that go out to the same person and/or email.This creates significant challenges:There is no way to distinguish which envelope contains which document when reviewing sent items. The email notifications sent to recipients also use the same generic title, providing no indication of the specific contract or document inside. When sending multiple templates (e.g., four different agreements through same PowerForm), all appear identical, making tracking and organization difficult for both senders and recipients.Allowing users to name envelopes would:Improve clarity and organization for both internal teams and clients. Reduce confusion and errors when managing multiple agreements. Enhance the overall user experience by providing transparency in communications. Provide better tracking while searching in the inbox for specific agreement and within DocuSign so we can check the status of the envelope as well.

    daniel.krcmarDigital Collaborator

    Include Clause Library in Agreement Builder and Generation (Conditional Clause Selection)Idea Submitted

    ProductDocusign IAM (Agreement Preparation / Agreement Builder)Idea / Enhancement RequestCurrently, the Docusign Clause Library is available primarily in CLM scenarios, but it is not usable within IAM Agreement Builder or generation flows when working with conditional or dynamic clauses.In IAM: Conditional logic can insert or paste static text Clause content must be hard-coded or duplicated There is no option to select a clause from the Clause Library via a lookup field This limits reuse, governance, and consistency across agreements.Proposed EnhancementExtend the Clause Library so it can be used: During agreement generation Inside the Agreement Builder, including conditional logic Specifically: Allow users to select clauses from the Clause Library via a lookup/dropdown field Insert the selected clause dynamically into the agreement Preserve clause metadata (name, version, owner) Support conditional logic (e.g. jurisdiction, contract type, customer segment) Instead of pasting static text, users should be able to reference managed clauses.Why This MattersWithout Clause Library support in IAM: Clauses are duplicated across templates Legal loses control over clause versions Updates require manual changes in multiple places IAM falls short of basic CLM expectations Example Use Case“If country = Germany → insert German liability clause from Clause LibraryIf contract value > €50k → insert extended indemnification clause (latest approved version)”SummaryIAM Agreement Builder should support dynamic clause selection from the Clause Library, not just static text insertion. This is essential for scalable, enterprise-grade agreement creation.