This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Let users host an in-person signing session on the host’s device.
In-person signing in Adobe Acrobat Sign allows a designated host to guide a signer through completing an agreement on a shared device. This host-controlled workflow supports scenarios where the signer does not have access to email or a personal device while maintaining a secure and auditable signing process.
Senders assign the In-Person Signer role, designate a host, and complete the signing session within the application. The audit trail records hosted signing activity for traceability.
Configuration
Availability
- Acrobat Sign Solutions: Supported.
- Acrobat Sign for Government: Supported.
- Acrobat Standard and Acrobat Pro: Not supported.
Configuration scope
In-person signing can be enabled at the account and group level.
- Group-level settings override account-level settings.
Default value: Disabled.
- If in-person signing is disabled before the hosted signing session starts, the agreement cannot progress and must be replaced.
To access this setting, navigate to Send Settings > Allowed recipient roles > Allow senders to mark recipients as In-Person signers
Controls
Allow senders to mark recipients as In-Person signers
- When enabled, senders can assign the In-Person Signer role and route agreements through a host-led signing session.
- When disabled, the role is unavailable and all recipients must sign through standard delivery methods.
Allow senders to specify an email address of In-Person signers
- When enabled, senders can enter the in-person signer’s email address during agreement creation.
- When disabled, the signer can enter an email address during the signing session before applying their signature.
Best practices
For administrators
- Enable this setting only for groups that require assisted signing workflows.
- Enable signer email entry when completed agreement delivery or signer recordkeeping is required.
- Apply authentication to the host when stronger access control is required.
For hosts
- Verify the signer’s identity before handing over the device.
- Clear the browser session before starting a new signing session.
How the setting works
This setting changes the signing model from direct recipient access to host-controlled access on a shared device.
When enabled, this setting adds the In-Person Signer role to the list of recipient roles available during agreement creation.
When a sender selects In-Person Signer for a recipient, the recipient record changes to support hosted signing. The sender must provide:
- The host’s email address.
- The signer’s name.
If Allow senders to specify an email address of In-Person signers is enabled, the sender can also enter the signer’s email address during composition. If that control is disabled, the signer can enter an email address during the signing session before applying their signature.
The host must be an internal user in the same account and can be the sender.
Authentication can be applied to the host, but not to the in-person signer. The host is expected to complete any required authentication before starting the signing session. The in-person signer does not complete a separate authentication challenge in this workflow.
To understand how this configuration affects the user experience, review the related process documentation:
- Host an in-person signing
- Compose an agreement for in-person signing
Things to know
- Only internal users can host in-person signing.
- Authentication is not supported for the in-person signer.
- The host is responsible for verifying the signer’s identity.
- Multiple in-person signers can be used in the same agreement.
- If in-person signing is disabled while agreements are waiting for an in-person signer, those steps cannot be completed. Hosts cannot start the signing session, and the agreement remains pending until the setting is re-enabled or the agreement is replaced.
