Skip to main content

    Filter by Idea status

    Filter by category

    1117 Ideas

    AustinLNew Voice

    Department-Level Group Admins with Scoped User ManagementIdea Submitted

    We would like to request an enhancement to DocuSign’s user and group management model to support true department-level group administration. Specifically, the ability to designate a “group super-user” who can add and remove users within their assigned group only, without granting broader administrative permissions.In our current configuration, the closest available option is to assign a custom Permission Profile with limited administrative access (Users and Groups → Edit Groups Only). However, this permission allows the user to view all users and manage membership across all groups in the account, which does not meet least-privilege or separation-of-duties requirements. There is currently no way to scope this capability to a single group, nor to prevent visibility or modification of other departments such as HR or Finance.The ideal solution would allow Account Administrators to assign group-scoped admin rights, enabling designated users to manage membership for their own department while preventing access to password changes, other groups, or account-wide settings. This capability would significantly improve governance, scalability, and security for organizations with multiple departments, especially those looking to decentralize routine user management without increasing risk.We believe this enhancement would benefit many customers with enterprise governance requirements and would appreciate consideration for future roadmap planning.

    FritziNew Voice

    Allow Selection of Saved Profile Signatures When Signing via Drag-and-Drop Signature FieldsIdea Submitted

    When signing documents in DocuSign, users can select from the signatures saved in their profile when completing a predefined signature placeholder. However, when a signature field is added directly during the signing process using drag and drop, the saved profile signatures are not available.This creates an inconsistent user experience because the available signature options depend on how the signature field was created rather than on the user's configured profile signatures.Many users maintain multiple signatures in their DocuSign profile, for example:Signatures with and without academic titles Alternative signature styles Different signatures for specific business contextsFrom an end-user perspective, they should be able to select any signature stored in their profile regardless of whether the signature field was predefined by the sender or added via drag and drop during signing.Proposed EnhancementEnable signers to access and select all signatures configured in their DocuSign profile whenever they are applying a signature, including signatures added through drag-and-drop fields.Business ValueConsistent signing experience across different workflows Better usability for users with multiple saved signatures Reduced confusion caused by differing behavior between signing experiences Less dependency on document preparation and field preconfiguration by sendersThis enhancement would provide a more intuitive and flexible signing experience while aligning the drag-and-drop workflow with the existing placeholder-based signing experience.

    Let ECFs do their job in the background without unnecessarily exposing technical fields to senders.Idea Submitted

    Flexible Visibility of Envelope Custom Fields (ECFs) DocuSign allows Envelope Custom Fields (ECFs) to be used as unique identifiers, such as contract IDs or purchase order (PO) numbers, in envelope email subjects. For high-volume document processing and large campaigns, Bulk Send with CSV uploads is an efficient way to manage envelopes using these identifiers.However, to use an ECF in this process, it must be visible to envelope creators at the account level, even when it is only required for background processing. This can confuse senders and unnecessarily expose technical fields in their workflow.Proposed enhancement Allow ECFs to remain functional while hidden from envelope creators, with more granular visibility controls.Ideally, administrators should be able to:Use hidden ECFs in Bulk Send CSV uploads and envelope email subjects. Configure visibility at the Template or Group level, rather than only account-wide. Control ECF visibility independently of its availability for processing.Suggested implementation priority 1. Initial enhancement: Allow hidden ECFs to be populated through Bulk Send and used in email subjects.2. Further enhancement: Introduce Template- or Group-level visibility settings for greater flexibility across business processes.This improvement would simplify the sender experience, reduce unnecessary training, and enable more flexible automation and identification workflows without exposing irrelevant technical fields to users.BRFrantisek