Dropbox Sign optional signers: what disappears when you skip a role

Dropbox Sign Premium lets you leave an unneeded signer role blank when sending from a template. Its variable signing feature removes that role and the fields assigned to it. Before using it for an optional co-signer, check field ownership: anything assigned to the omitted person disappears from that request. Dropbox’s variable signing guide

An agreement with an occasional Guarantor makes the problem easy to see. Customer and Company always sign; Guarantor signs only when the agreement owner requires it. The owner decides that requirement. The example here covers how to prepare the document for either recipient set.

Give each field the right owner

Use this six-field example to plan the assignments. The IDs are worksheet labels, not Dropbox Sign API parameters.

Field ID	Role	Field type	Required if included	Without Guarantor
customer_signature	Customer	Signature	Yes	Retained
customer_date	Customer	Sign date	Yes	Retained
company_signature	Company	Signature	Yes	Retained
guarantor_name	Guarantor	Textbox	Yes	Removed
guarantor_signature	Guarantor	Signature	Yes	Removed
guarantor_date	Guarantor	Sign date	Yes	Removed

With Guarantor included, the layout has six fields. Applying the documented omission rule leaves three fields when Guarantor is absent. These are the expected results for this example, not an exported or completed signature request.

Now consider a misplaced field. You drag a Customer name textbox onto the first page but accidentally assign it to Guarantor. Its position looks right, yet its owner is wrong. Correct the assignment before using the template. A field’s location beside a Customer heading does not establish its recipient.

Click a field and inspect the assigned signer in the editor’s right sidebar. The sidebar also contains its required setting and name. Dropbox’s editor guide explains these controls. Check fields near the boundary between the Customer and Guarantor sections, where a visually plausible placement can hide the wrong assignment.

Download the role-map CSV to adapt these six rows to your document. It is a planning worksheet, not an importable Dropbox template or a contract.

An optional field still belongs to a signer

The required setting controls whether a field must be completed. Dropbox’s signing experience guide describes a counter for required fields and an alert when a signer tries to finish without them. Optional fields also appear in the signer’s navigation.

For example, you might allow an included Guarantor to skip a secondary phone-number textbox while requiring their signature. That changes the field’s completion requirement. To prepare a request without that person, use the recipient-role omission described above. Do not make every Guarantor field optional and assume the signer has disappeared.

Prepare the document as well as its fields

Dropbox’s template creation instructions let you upload the document, add signer roles, place fields, and save the reusable template. Templates are available on Essentials, Standard, and Premium; variable signing requires Premium. Add the full set of roles the document may need, with clear names such as Customer, Guarantor, and Company.

Use Preview and the view dropdown to inspect the intended signer views before saving. Field ownership and the page underneath deserve separate attention. If the uploaded PDF contains a printed heading reading “Guarantor signature,” inspect how the document should read when that person is absent. Dropbox promises removal of assigned form fields; do not expect that feature to rewrite printed agreement wording. Ask the agreement owner to supply appropriate text or a separate document version where necessary.

Leave the unused recipient blank when sending

In the web app, open Templates, choose My Templates, and select Use template. Upload any additional documents the request needs or continue with Next. Enter the names and email addresses for the included roles. Premium users can leave an unneeded role blank. Continue with Next, add the title and message under Message to signers, then use Send for signature. Dropbox’s template sending instructions

For the example, Customer and Company need real recipients in both versions. Enter a Guarantor only for the version that requires one. Avoid a fake address, your own address, or a placeholder name as a substitute for an absent recipient. Before sending, read each address beside its role; reversing Customer and Company is a different error from omitting Guarantor.

A Customer checkbox cannot control a Guarantor’s fields

Premium conditional logic changes which fields appear based on signer input. Both the trigger and the fields it controls must belong to the same signer. Dropbox’s conditional logic instructions

A Customer checkbox labeled “Use a different delivery address” can show a Customer address textbox. A Customer checkbox labeled “I have a Guarantor” cannot control a Guarantor-owned signature field under that documented same-signer rule. Decide the recipient set before sending.

To create a rule within one person’s fields, select the trigger, choose Create Rule, set its condition, and add the fields to show or hide. This can simplify the Customer portion of a document even when an optional Guarantor role exists elsewhere.

Review sequential signing for both versions

If your process requires Customer to sign before Company, configure the order deliberately. Dropbox’s +Signer control exposes Set signer order. Enable the toggle and drag the grid of dots beside each role to rearrange them. The next signer receives an email after the previous signer completes their part. Dropbox’s signing-order instructions

A process might use Customer, then Guarantor, then Company. Review the request without the middle recipient too. The ordering guide does not describe that exact omission case, so verify the resulting route in your account before relying on it for real agreements.

Repair a pending request without surprising signers

If you already sent a request with the wrong recipients or fields, Dropbox documents Documents, the pending request’s more-options menu, then Edit and resend. You can update the recipients, fields, message, and document. Review the request details again, including access codes, which do not automatically repopulate. Dropbox’s pending-request editing guide

People who already signed are notified and prompted to sign again. Removed signers receive a notification, and the audit trail records the changes. Tell affected recipients why a new signing request is arriving; an edit can require action from someone who thought they had finished.

For a wrong person occupying an otherwise correct role, Edit Signers and Replace is a narrower option available before anyone has signed. That replaces the recipient for the existing role. Dropbox’s signer replacement instructions

Keep the API workflow separate

Dropbox documents variable signers for /signature_request/send_with_template and /signature_request/create_embedded_with_template. Check the integration’s actual entitlement and endpoint instead of assuming a web plan covers its API use. Advanced signing tools

A non-template text-tag request has different requirements: its referenced signer list must have no gaps, and each referenced signer needs a corresponding name and email address. Removing an arbitrary indexed signer from that request is not the web template procedure above. Dropbox Sign’s text-tag documentation

Source scope: These instructions follow Dropbox’s linked documentation. The field map and recipient variants are authored examples. No paid-account request or API transaction was tested for this article.