Dropbox Sign access codes and SMS: help the right signer open the request

A Dropbox Sign invitation can reach the right email address while the authentication step still reaches the wrong person. Before sending a request, decide who is meant to sign, which method each signer will use, and how an access code or text message will reach that person. If a signer gets stuck, identify the failed step first: the invitation email, the separately delivered code, or the text message prompt.

Set the method and its delivery details

1. On Who needs to sign?, enter the signer’s name and email.
2. Open that signer’s vertical ellipsis menu and choose Add signer authentication.
3. Under Authentication method, choose Access code and enter the code you will give the signer, or choose Text message and enter the signer’s mobile number.
4. Repeat for each signer who needs authentication.

Deliver an access code separately; Dropbox Sign does not include it in the invitation. With SMS, the signer opens the request email, follows the prompt to send a code to their phone, then enters that code to access the document. Dropbox Sign signer authentication

Route each signer’s access

Consider a hypothetical two-party agreement. Jordan is the client at client@example.com, and Sam is the provider at provider@example.com. Finance records at records@example.com needs a completed copy but is not a signer. The addresses are examples, not accounts used in a transaction.

A workable plan might give Jordan an access code and Sam text message authentication. Before sending, the sender would privately agree with Jordan on a separate way to deliver the code and confirm Sam’s phone details with Sam. In this plan, finance records receives a copy and has no signature task. Its mailbox should not replace Jordan or Sam in the recipient details.

If several people read client@example.com, agree which person is signing and route the separate code to that person. Neither mailbox access nor possession of the code certifies the person’s identity.

The sample signer-routing.csv is a worksheet for planning that route manually. Its rows assign the client an access code, the provider a text message, and records a completed copy. It records a delivery plan, not the code or a full phone number. A sender can review those rows with the intended recipients, then enter the appropriate people and methods in Dropbox Sign. The CSV is not a Dropbox Sign export, import, or integration.

Keep the access code separate

For Jordan’s access-code route, the sender needs two pieces to arrive through their planned channels: the request at client@example.com and the code delivered separately. Using the same shared inbox for both deliveries would let its other readers receive both pieces. The sender should arrange a private channel with Jordan before sending the request and use that agreed channel for the actual code.

A reusable coordination message is:

Jordan, I’m preparing the agreement for client@example.com with an access code. Please confirm privately which separate channel I should use to deliver the code to you. I won’t include the code in the routing worksheet.

This message arranges delivery; it does not contain a code. If Jordan later reports that the code is rejected, check the characters as entered. Dropbox Sign says access codes are case sensitive, so changing a capital letter to a lowercase letter can explain a failed entry. Its help pages use both “password” and “access code” wording for this feature. Dropbox Sign signer access codes

Follow the text message route

If Sam has the invitation but the phone step fails, compare the intended recipient with the number entered by the sender. The worksheet can record “Confirm phone with intended recipient” while the actual number stays in the request.

A text message used to open a signature request is different from SMS two-factor authentication on the sender’s Dropbox Sign account. The latter protects the sender’s login. Turning attention to the sender’s login setting will not explain a problem with the recipient’s document authentication step. Dropbox Sign SMS two-factor authentication

If someone else now needs to sign in Sam’s place, treat that as a change to the request’s recipient plan. Ask the sender to correct the intended signer and delivery details. Casually forwarding Sam’s invitation, code, or text message to a delegate would leave the request addressed and routed according to the old plan.

Locate the failed step

Work through the sequence in order. Each answer points to a different correction.

1. The invitation is missing. Confirm which address the sender entered for that signer and which inbox the signer is checking. In the example, Jordan should look for the request at client@example.com; a message sent to records@example.com would have reached the copy recipient instead. Ask the sender to check the request’s recipient details if the addresses do not match.

2. The invitation arrived, but the access code did not. Check the separate delivery arrangement with the sender. Receiving the request email alone does not mean Jordan has received the separately delivered code. Keep the code out of a shared troubleshooting thread and out of the worksheet. Dropbox Sign signer authentication

3. The access code was delivered but rejected. Compare the entered code with what the sender delivered through the agreed channel, including capitalization. Report the rejection without pasting the code into an email to multiple people. Dropbox Sign signer access codes

4. The text message route points to the wrong phone. Sam should tell the sender which part failed so the sender can review the intended recipient and phone details. Do not assume that access to provider@example.com gives its reader access to the phone selected for Sam.

5. The sender cannot choose the intended method. A Dropbox Sign administrator can enable signer authentication methods and control member access under Admin console > Settings > Signature Requests > Signature Request Options. An unavailable option may reflect an administrator setting, so the sender should ask the account administrator to review it. The access-code help page explicitly lists Standard and Premium, but that listing does not establish every plan’s eligibility or any text message price. Manage signer authentication settings · Signer access codes

A recipient can report a failure without sending an authentication secret:

I received the request at provider@example.com, but the text message step is going to a phone that is not mine. Please review the recipient details with me before I continue. I won’t forward a code or text message.

For an access-code problem, change the message to identify the last successful step: invitation received, separate delivery received, or code rejected. Include the document title and the address where the invitation arrived so the sender can distinguish this request from others. Keep the actual code in the private channel agreed with the sender.

Source note: Official Dropbox Sign help pages were checked October 7, 2026. The agreement, messages, and routing worksheet are illustrative; no signature request or authentication flow was tested.