diff --git a/docs/TurboSign/embedded-signing/build/_setup-and-verify.mdx b/docs/TurboSign/embedded-signing/build/_setup-and-verify.mdx
index d8535a5..2adbe50 100644
--- a/docs/TurboSign/embedded-signing/build/_setup-and-verify.mdx
+++ b/docs/TurboSign/embedded-signing/build/_setup-and-verify.mdx
@@ -1,3 +1,3 @@
 An admin must have completed [Set up your organization](../set-up-your-organization.md): **Enable identity verification** is on (it is the master switch for embedded signing), and your app's origin is under **Allowed embedding domains**.
 
-This guide verifies each signer with an **email passcode**. Every embedded signer needs a verification method unless you use the sender override while testing. To use SMS, your own identity provider, or the override, see [Identity verification](../../identity-verification/index.md).
+This guide verifies each signer with an **email passcode**. Give every embedded signer a verification method. TurboSign does not enforce this: with no verification, and an organization that verifies only when requested, it still issues a reusable link that anyone holding it can use (see [A recipient with no verification is unprotected](../../identity-verification/index.md#signers-in-your-own-app-embedded-signing)). To use SMS, your own identity provider, or the override, see [Identity verification](../../identity-verification/index.md).
diff --git a/docs/TurboSign/embedded-signing/index.md b/docs/TurboSign/embedded-signing/index.md
index 652bf16..ee07013 100644
--- a/docs/TurboSign/embedded-signing/index.md
+++ b/docs/TurboSign/embedded-signing/index.md
@@ -49,7 +49,11 @@ Every embedded signing integration makes the same four moves:
 
 ## Choose how signers verify
 
-Every embedded signer needs a verification method, unless you use the sender override while testing. Your app shows the signing page itself and TurboSign emails no link, so a check is what ties the person at the screen to the signer of record.
+Give every embedded signer a verification method. Your app shows the signing page itself and TurboSign emails no link, so a check is what ties the person at the screen to the signer of record.
+
+:::caution TurboSign does not enforce this
+If you set no verification on a signer and your organization verifies only when requested, TurboSign still issues a reusable signing link, and anyone holding it can sign. If your organization verifies on every signature request, the signer gets your organization's default method instead. See [A recipient with no verification is unprotected](../identity-verification/index.md#signers-in-your-own-app-embedded-signing).
+:::
 
 | Method | Who verifies the signer | Signing URL |
 |---|---|---|