Why can't I mark sender (template owner) text fields as optional?

If you're building a Sign.Plus template, you may have noticed that recipient (signer) fields can be marked optional, but sender fields cannot. This is by design, but here's the reasoning and the workarounds.

Why sender fields default to required

When you set up a template, fields assigned to the template sender (you, or whoever sends the signing request) are filled in before the request is sent to signers. The template wizard assumes that if you added the field, you intended to fill it in. This prevents accidental omissions in critical fields.

How to leave a sender field blank in practice

You have several options:

Option 1: Don't include the field in the template at all.
If a piece of information is sometimes blank, the simplest solution is to leave it out of the template entirely. Add it on a per-document basis when needed.

Option 2: Include the field but enter a single space or "N/A".
When sending the request, fill the field with a single space, "N/A", or "—" to satisfy the requirement. The field will appear empty or with that placeholder in the final document.

Option 3: Use a recipient field but assign it to "yourself."
Add the field to your template as if it were a signer field. Configure it to be assigned to a "signer" who is actually you (your own email). Mark it as optional. When the request is sent, you receive the request first, fill in the field as needed (or leave it blank), and pass it to the actual signer.

Option 4: Save multiple template versions.
Create one template with the optional field included and another without. Use the appropriate template for each document type.

Tips for template design

  • Group fields by purpose. If a field is "always-on" for a document type, include it. If it's situational, consider leaving it out and adding it ad-hoc.
  • Use templates per-workflow rather than per-document. Save separate templates for "Standard contract," "International contract," "Renewal contract" rather than one template with many optional fields.
  • Test with a colleague. Before rolling out a new template to clients, send a test to a colleague to make sure the flow makes sense.
     
Was this article helpful?
0 out of 0 found this helpful
More Articles in this section