ILLUSTRATIVE SIGNER CONTROL TRACE
This is a planning example derived from the linked official documentation.
It is not an export from a paid Adobe account, a product trial, legal advice,
an identity record, or a claim that a sample agreement was actually sent.

Document: client-change-order.pdf (illustrative name; no customer file)
Recipients: Client Signer and Company Signer
Both recipients are Signers. Each has a field assigned to their own role.
Assume the same configured method applies to both recipients in this example;
no separate internal-recipient authentication exception is configured.

PROVIDER AUTHENTICATION, DEFAULT WITH OVERRIDE OFF
1. Administrator enables a chosen provider on the Digital Identity page.
2. Administrator selects that provider as the sending group's default method.
3. Administrator disables sender override for this configuration.
4. Sender creates the agreement in that group and assigns each required field
   to the correct recipient. The sender cannot substitute another method.
5. Each recipient authenticates with the provider before returning to Sign.
6. Expected audit evidence: provider name and authentication events.
   External identity attributes and provider credentials are not in the audit.

PROVIDER AUTHENTICATION, DEFAULT WITH OVERRIDE ON
The sender can choose another enabled authentication method per recipient.
A default provider alone does not prove that the agreement used it.
Compare the saved recipient method and audit events with the required method.

REQUIRED DIGITAL SIGNATURE FOR CLIENT SIGNER ONLY
Administrator enables Digital Signatures for the account/group.
Sender selects the Client Signer and requires a Digital Signature.
That recipient needs a required Digital Signature field assigned to them.
Company Signer can use a standard electronic signature in the same agreement.
Adobe lists the per-recipient requirement feature for Sign Solutions, not Pro.
Provider authentication and a certificate-backed signature are separate steps.

TRANSACTION UNITS
Sending this one agreement to both recipients is one agreement transaction.
If both recipients use Phone authentication, two Phone transactions are used.
This calculation is illustrative, not an allowance, price, or observed usage.

Official sources checked 2026-10-07:
https://helpx.adobe.com/sign/web/settings-configuration/send-settings/digital-identity-authentication.html
https://helpx.adobe.com/sign/web/settings-configuration/digital-signatures/require-dig-sig-thru-send.html
https://helpx.adobe.com/sign/web/settings-configuration/send-settings/phone-auth.html
https://helpx.adobe.com/sign/web/system-level-resources/transaction-limits.html
https://helpx.adobe.com/sign/web/settings-configuration/send-settings/overview.html