You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 12a3fd3
Browse filesBrowse the repository at this point in the historyBrowse files
docs(turbosign): comment out OTP how-to screenshots that were never captured
Five images referenced by the One-Time Passcode how-to (otp-01..05) were never added to
static/, which failed the Docusaurus build and the Cloudflare Pages deploy. The references stay
in HTML comments beside their RECAPTURE notes until the screenshots are captured.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/TurboSign/How to Configure One-Time Passcode.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Under **Default method**, choose how the passcode reaches signers by default:
44
44
The default method is used for every recipient unless you allow senders to change it.
45
45
46
46
<!-- RECAPTURE: screenshot of the Default method dropdown (open, showing None / Email / SMS) with the field highlighted. Shoot at 948 CSS px viewport width, DPR 1.5 (output 1422x676) to match the other screenshots. -->
47
-

47
+
<!-- TODO(screenshot not yet captured — see RECAPTURE note above): -->
48
48
49
49
To let senders pick a different channel per recipient, turn on **Let senders choose per recipient**. When it is off, every request uses the default method above; when it is on, senders can change the method for each recipient. This applies to the email channel too, so it is not tied to your SMS plan.
50
50
@@ -57,7 +57,7 @@ Email passcodes work on every plan and need no setup. If **Email** is your defau
57
57
To let signers verify by text message, turn on **Allow SMS as an alternative to email** under **Text message (SMS)**. Senders can then choose SMS instead of email for a recipient. Each signer verifies by one method, not both, and SMS may incur usage charges.
58
58
59
59
<!-- RECAPTURE: screenshot of the Text message (SMS) section with the "Allow SMS as an alternative to email" toggle highlighted. Shoot at 948 CSS px viewport width, DPR 1.5 (output 1422x676). -->
60
-

60
+
<!-- TODO(screenshot not yet captured — see RECAPTURE note above): -->
61
61
62
62
:::note SMS is plan-gated
63
63
SMS verification is available on **Pro and Enterprise plans**. If your plan does not include it, this section shows an **Upgrade to unlock SMS verification** card instead of the toggle.
@@ -77,12 +77,12 @@ TurboSign sends SMS passcodes through **your own** SMS account, so passcodes are
77
77
4. Click **Save SMS provider**.
78
78
79
79
<!-- RECAPTURE: screenshot of the SMS provider credential form (Provider = Twilio) with the Save SMS provider button highlighted. Shoot at 948 CSS px viewport width, DPR 1.5 (output 1422x676). -->
80
-

80
+
<!-- TODO(screenshot not yet captured — see RECAPTURE note above): -->
81
81
82
82
After you save credentials, click **Verify connection** to confirm your account can send messages (this is a free check and sends no text), then use **Send a test message** to send a real passcode-style text to a number you control and confirm end-to-end delivery.
83
83
84
84
<!-- RECAPTURE: screenshot of the "Send a test message" area with the Test number field and Send test message button highlighted. Shoot at 948 CSS px viewport width, DPR 1.5 (output 1422x676). -->
85
-

85
+
<!-- TODO(screenshot not yet captured — see RECAPTURE note above): -->
86
86
87
87
:::caution Use a production provider account
88
88
SMS passcodes use a custom message body, which **trial accounts** (for example a Twilio trial) block. Use a paid, production provider account. Sending to US numbers also requires **A2P 10DLC registration** on your provider account - TurboSign links to your provider's registration flow next to the credential fields.
@@ -102,7 +102,7 @@ Delivery-failure alerts email an admin when a one-time passcode cannot be delive
102
102
-**Specific addresses** - enter the exact addresses that should be alerted (for example `ops@example.com`), one chip per address.
103
103
104
104
<!-- RECAPTURE: screenshot of the Delivery failure alerts section with the "Send alerts to" selector highlighted. Shoot at 948 CSS px viewport width, DPR 1.5 (output 1422x676). -->
105
-

105
+
<!-- TODO(screenshot not yet captured — see RECAPTURE note above): -->
0 commit comments