Sent Dropbox Sign to the wrong person? Replace the signer

If a Dropbox Sign request is still pending and no one has signed it, you can replace the recipient on the existing request. Replacing a signer routes the request to someone else; it does not change the document, its fields, or who has authority to sign.

The names and addresses below are fictional examples.

Check the request and the role

Suppose October illustration approval was sent with Taylor Chen, taylor.chen@example.com, listed for the Designer role. Jordan Lee, jordan.lee@example.com, was the intended Designer signer. Morgan Patel, morgan.patel@example.com, is the Client signer and should stay on the request.

Before editing, check the request title so you do not confuse October illustration approval with a similarly named November request. Then write down the change you intend to make: Designer: Taylor Chen becomes Jordan Lee; Client: Morgan Patel stays unchanged. Check that no one has signed, and confirm outside Dropbox Sign that Jordan is the person authorized for the Designer role. An email address alone cannot establish that authority.

Treat the displayed name, email address, and role as separate checks. Changing “Taylor Chen” to “Jordan Lee” while leaving taylor.chen@example.com in place would still send the request to the wrong address. Likewise, the right address paired with the wrong role calls for a closer look before you save.

Replace the specific signer

Dropbox’s signer replacement instructions describe this flow for Essentials, Standard, and Premium plans when a sent request is pending and nobody has signed:

1. Open Documents, find the request, and choose More options.
2. Select Edit Signers.
3. Use the dropdown beside the signer you need to correct, then select Replace.
4. Enter the replacement signer’s name and email address. You can replace other signers before selecting Save.

For the example, replace Taylor with Jordan Lee, jordan.lee@example.com. Before saving, compare those entries with the planned Designer role and confirm that Morgan’s Client entry is untouched. Use Replace for a person who should take an existing signer’s place; it is not a way to add a second Designer signer.

Dropbox says the former signer is notified that their signature is no longer needed, their earlier link loses document access, the new recipient gets a request, and the change appears in the audit trail. Loss of access through that link does not establish whether the former recipient had already saved a copy.

The replacement flow does not let you edit the authentication method or signer settings. If Jordan needs a different authentication method, resolve that requirement separately before saving the replacement.

Tell the original recipient

The product notification handles the change in signing responsibility. A short personal message can explain why the request reached the person in the first place, especially if the address belonged to a colleague or client contact.

For the fictional October request, the sender could write:

Subject: Correction to October illustration approval

Hi Taylor,
October illustration approval was addressed to you in error. Your signature is not required. The recipient on that request is being corrected, so please disregard the original request. If you have a question about the document you received, please reply to me.

Thanks.

Keep the message factual. It need not speculate about whether Taylor opened the link, viewed the document, or retained a copy. Do not ask Taylor to forward the original link to Jordan; replace the signer on the request so the intended recipient gets their own request.

Give the new signer context

Jordan may appreciate a separate explanation of the document and expected role. This is a message from the sender, separate from the Dropbox Sign request:

Subject: October illustration approval: Designer signature

Hi Jordan,
You are the intended signer for the Designer role on October illustration approval at jordan.lee@example.com. Please review the Dropbox Sign request when it arrives. If you are not the right person or do not have authority to sign as Designer, reply to me before signing.

Thanks.

If a teammate owns the request, confirm the correction with that person first: “Is October illustration approval your request, and can you confirm that Jordan Lee at jordan.lee@example.com is authorized to sign in the Designer role?” Ask the sender to confirm ownership and signing authority before making the correction.

Match the fix to the mistake

A typo and a wrong person can look similar in the recipient list, but they call for different checks.

If Taylor Chen was the intended signer and the request went to taylorchen@example.com instead of taylor.chen@example.com, the correction is the email address. Those are different identifiers as written; do not assume a mail provider treats them as equivalent. Confirm Taylor’s intended address before replacing the recipient entry.

In the October illustration example, the address belongs to the wrong intended signer altogether: Jordan should replace Taylor in the Designer role. That requires confirming both Jordan’s email and Jordan’s authority. Morgan remains the Client signer in either case.

A replacement solves that recipient-routing mistake. If the document text or its fields are wrong, changing the signer’s name and email does not fix them.

If Replace is unavailable

Check the actual request status, whether anyone has signed, your plan, and whether you own the request before treating a missing menu as a technical fault. Dropbox’s team roles guidance says all four roles can edit their own pending requests, while admins can manage requests on behalf of others. A Team Manager does not automatically have access to other team members’ documents.

If someone has signed, Replace is unavailable. The newer pending-request edit and resend guidance covers broader changes and requires prior signers to sign again. Review that route for the specific request before acting. Do not delete or resend a request simply because the narrower Replace option is unavailable.

For an internal correction record, note the request title, old name and email, new name and email, intended role, whether anyone had signed when checked, any authentication-method question, and when the correction was made. That record keeps the reason for the change clear without treating the signer replacement as a document edit.

Source note: The product steps and limits come from the linked Dropbox Help pages. The October illustration request, all people and addresses, and the message drafts are fictional; no request was independently tested for this article.