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

Categories:Admin Tools

1 reply
25 views
Translate All

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.

BR

Frantisek

F

Frantisek Hajducko

Author

New Voice

Hello Community,

Just to add to my idea.

Customers often require one or two identifiers in the email subject line. Envelope Custom Fields (ECFs) are a great way to achieve this while also making the identifiers available in Envelope Reports. However, the current configuration options are not flexible enough.

It would be great to introduce an additional ECF setting, such as “Active but not visible,” allowing ECFs to be used in the background without exposing them to senders.

I agree that managing ECF visibility at the Group or Template level would be another good approach:

Group-level configuration: Administrators could assign ECFs to specific groups, making them available only to relevant senders. Senders outside the group would not see these fields.

Template-level configuration: ECFs could be selected in the template settings under Advanced Settings. This would be a simple, effective, and clean solution, ensuring that only the relevant ECFs are used with each template.

BR

Frantisek

Translate

Flexible Visibility of Envelope Custom Fields (ECFs)

Proposed enhancement

Suggested implementation priority

Sign up

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Docusign Community

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.