Dropbox Sign Standard or Premium for optional signers?

Choose Dropbox Sign Premium if one template must accommodate an optional signer. Dropbox Help says variable signing is available on Premium. It lets you include every potentially needed signer role in a template, then leave an unused role blank when sending. That role and its assigned fields are removed from the request. If every request has the same planned signer roles, evaluate Standard against your current quote. Confirm the quoted Premium entitlement and the account’s admin and template settings before committing to the optional signer workflow. Dropbox Help: variable signing.

Your sending pattern	Tier decision	What to verify
The same two signers are always needed	Evaluate Standard with those planned roles	The current quote and a representative template meet the fixed workflow
Some requests need a co-signer	Choose Premium for variable signing	The optional role can be left blank and its fields are removed from that request
The signer roster is uncertain	Hold the tier decision	Confirm the Premium entitlement, settings, and both sending paths

The choice turns on what happens to a role already built into the template. Dropbox’s sending instructions say to enter names and email addresses for signer roles and specify that Premium users can leave unneeded roles blank. Its variable signing article adds that fields assigned to an unused role are removed from the request. Those statements support Premium for an optional role; they do not establish any broader Standard limitation. Dropbox Help: sending from a template; Dropbox Help: variable signing.

Consider a small operations team that sends the same agreement repeatedly. The customer and a company representative must sign every time. Some agreements also need a co-signer. The team prepares one template with three named roles and places each signature field beside the correct party’s portion of the agreement. For a request without a co-signer, the sender fills the first two roles and leaves the third blank. Under the documented Premium behavior, the co-signer role and its fields are removed from that request. For a request with a co-signer, the sender supplies all three names and email addresses and checks that each party’s fields are correctly placed. The team should review both paths before using the template for real agreements. Dropbox Help: variable signing; Dropbox Help: sending from a template.

Roll out the template through a controlled sample. Identify who approves the agreement text, who maintains the template, and who may send requests under the team’s process. Confirm that the account and admin settings allow those people to carry out their assigned steps. If the quoted Premium entitlement or relevant settings cannot be confirmed, pause the rollout. If either signer path fails the checks below, correct the template or account setup before wider use.

Permissions and retention need separate decisions. The supplied help pages explain template sending and unused roles; they do not set the team’s internal approval rights or say how long its templates and sent agreements should be kept. Set access and retention rules with the organization’s owner, then verify them in the account and recordkeeping process. Removing an unused role’s fields from one request does not establish what happens to the template or other requests. Dropbox Help: variable signing.

Accept the purchase and rollout when these checks pass:

1. The current quote confirms Premium and variable signing for the intended account, and an admin confirms the applicable template settings.
2. The template contains roles for the two signers needed on every request and the optional co-signer, with each party’s fields in the intended location.
3. A sample request with two signers leaves the co-signer role blank. Review confirms its fields are absent while the other fields remain correctly placed.
4. A sample request with three signers includes the co-signer. Review confirms that all three parties’ fields appear in their intended locations.
5. The team records who may edit the template and send requests, where completed agreements are kept, and when records are reviewed or removed under its policy.