In the recipient list, open Recipient settings for the recipient you want to configure.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Apply stronger signing requirements only where they matter.
Require digital signatures for selected recipients while allowing others on the same agreement to use standard electronic signatures.
After digital signatures are enabled for an account or group, senders can require specific recipients to sign using a digital signature during agreement creation.
Adobe Acrobat Sign enforces the requirement by ensuring each selected recipient has at least one required digital signature field. Senders can also apply an administrator-enabled signature policy to restrict which cloud-signature certificates a recipient can use.
Configuration
Availability
- The ability to require a digital signature is available when at least one digital signature method is enabled for the account or group.
- Acrobat Sign Solutions: Supported.
- Acrobat Sign for Government: Digital signature requirements are supported, but policy-based digital signatures are not available.
- Acrobat Standard and Acrobat Pro: Not supported.
Configuration scope
- Administrators enable digital signatures at the account or group level.
- Senders determine which recipients must apply a digital signature.
- Administrators can configure signature policies separately to restrict the certificates available to recipients.
How this capability works
Administrators enable digital signatures, and senders specify which recipients must use them.
There is no separate administrative control for requiring individual recipients to apply digital signatures. Once digital signatures are enabled, senders can apply that requirement during agreement creation.
When signature policies are enabled, senders can also select a policy that defines which cloud-signature certificates are acceptable. Depending on the administrator's configuration, selecting a policy may be optional or mandatory.
The digital signature requirement and the selected policy apply only to the recipient being configured.
Require a digital signature for a recipient
From the Request Signatures process, open the settings for the recipient who must apply a digital signature.
Select Require recipient to apply a Digital Signature.
If signature policies are available, select an enabled policy when appropriate or required.
Complete the remaining agreement configuration and send the agreement.
Apply a digital signature policy
When administrators enable digital signature policies, senders can apply a policy to recipients who must use digital signatures.
Policies restrict which cloud-signature providers and certificates recipients can use. They are selected according to the agreement's signing requirements, not automatically based on the sender's or recipient's location.
The behavior of Apply a signature policy depends on the administrator's configuration.
| Policy selection | Sender experience |
|---|---|
| Optional | Apply a signature policy is unchecked by default. The sender can select it and choose one enabled policy or leave it unchecked. |
| Mandatory | Apply a signature policy is checked and locked. The sender must choose one enabled policy. |
| No policies enabled | Policy selection is unavailable. The recipient can use any otherwise permitted valid digital certificate. |
Only one signature policy can be selected for each recipient.
The selected policy remains associated with the agreement after sending. Subsequent administrator changes do not modify the policy for an agreement already in progress.
For information about administrator settings and supported policies, see Configure digital signature policies.
Identity Check behavior when digital signatures are required
Identity Check options are displayed only when supported by the administrator's configuration and the selected signing method.
- If Identity Check and Cloud Signatures are enabled, the available Identity Check options appear after a sender requires a digital signature.
- Available options can include email matching and name matching.
- Options disabled by administrator settings are hidden.
- When a signature policy is applied, the recipient's certificate must satisfy both the policy and applicable Identity Check requirements.
If only Download and Sign with Acrobat is enabled, the digital signature requirement remains available, but Identity Check options are not displayed.
Identity Check is not supported in legacy send experiences.
What happens during authoring
When a sender requires a digital signature for a recipient, Acrobat Sign adjusts the authoring experience and validates the requirement before sending.
- The Digital Signature field becomes the default signature field for that recipient.
- Electronic signature fields remain available if needed.
- At least one required digital signature field must be assigned to that recipient.
If the requirement isn't satisfied, Acrobat Sign blocks sending until it's resolved.
This validation applies to both modern and classic authoring experiences.
What happens if authoring is skipped
If a sender sends the agreement without opening authoring:
- Acrobat Sign automatically adds a required digital signature field for each recipient who must sign digitally.
- The field is placed at the end of the document using the default size and placement.
This ensures that agreements are not sent without the required digital signature fields.
Mixed recipient scenarios
An agreement can include recipients who must apply digital signatures and others who can use standard electronic signatures.
Acrobat Sign enforces each recipient's digital signature requirement independently. Where available, a sender can also apply a different enabled signature policy to each recipient who must sign digitally.
When text tags are used:
- Existing digital signature fields are made required when enforcement applies.
- Electronic signature fields remain unchanged.
- Additional digital signature fields are added only when required fields are missing.
After the agreement is sent
Digital signature requirements and selected policies are established during agreement creation.
After an agreement is sent, the required signing method and selected signature policy cannot be changed. To modify the requirements, the sender must create a new agreement.
When a policy applies, the recipient can use only suitable cloud-signature credentials. Certificates that do not satisfy the policy appear as NOT SUITABLE and cannot be selected.
If no suitable certificate is available, the recipient must obtain a certificate that satisfies the policy before completing the signing process.
Limitations to be aware of
- Recipient-level digital signature enforcement is available in the modern Request Signatures experience.
- Policy-based digital signatures apply only to Cloud Signatures.
- Policies do not apply to Download and Sign with Acrobat, even when a policy has been selected for the recipient.
- Policy-based digital signatures are unavailable in Government Cloud.
- Identity Check with digital signatures is not supported in legacy send experiences.
- Recipient groups do not support Identity Check configuration.
- No additional sender roles or permissions are introduced.