What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Create function-focused users
- Review users who haven't completed verification
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup / Branding Settings
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send Settings
- Show Send page after login
- Agreement creation experiences
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Remove recipients from in-flight agreements
- Create a copy (of an agreement)
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Populate form fields with identity-verified data
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Add myself
- Download agreement link
- Form field borders
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Restrict access to shared agreements
- Show Send page after login
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
- System Requirements and Limitations
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Automatic field detection
- Drag and drop fields using the authoring environment
- Assign form fields to recipients
- The Prefill role
- Apply fields with a reusable field template
- Transfer fields to a new library template
- Updated authoring environment when sending agreements
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Checkbox group
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Field types
- Authoring FAQ
- In-app authoring environment
- Sign Agreements
- Manage Agreements
- Manage page overview
- Copy an Agreement
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Automatically populate and lock critical form fields using identity-verified data when a signer completes an identity verification check. This reduces data entry errors and provides clear, auditable proof that specific values came from a trusted source.
Verified Forms let you bind verified identity information returned by an identity provider to form fields. When a signer successfully completes identity verification with a provider connected via the Digital Identity Gateway, Adobe Acrobat Sign inserts values from the identity claims into the tagged fields during signing, ensuring that critical data comes directly from a trusted source.
This capability is designed for high-trust workflows in regulated and security-sensitive environments, such as financial services and government.
How identity-verified data works
Identity-verified data is triggered only by field name conventions in either the authoring UI, text tags, or API.
There are:
- No UI controls to configure identity-verified fields.
- No validation when the document is uploaded or sent.
- No error messages if the configuration is incorrect.
If the field name does not match the required syntax exactly, the field behaves like a normal form field or is ignored entirely.
Required field naming syntax
To bind a form field to identity-verified data from an identity provider, the field name must follow this exact pattern:
VF_DIG_{claimName}*
Where:
- VF_ identifies the field as a verified form field.
- DIG_ specifies the Digital Identity Gateway authentication method.
- {claimName} is the exact OpenID Connect (OIDC) claim name returned by the configured identity provider, including spelling and casing, surrounded by curly brackets.
- * is optional text used to make the field name unique.
Examples:
- VF_DIG_{birthdate}
- VF_DIG_{address}_page2
- VF_DIG_{zipcode}1
If multiple fields reference the same identity claim, each field must still have a unique field name.
Supported identity claims
Only identity claims returned by the configured identity provider are recognized.
Claim names:
- Are defined by the identity provider, not by Acrobat Sign. It is incumbent on the sender to obtain the list of claim names from their vendor.
- Are case sensitive.
- Must match exactly.
- Do not support aliases.
- Are ignored silently if incorrect or missing.
If a claim name is not returned by the identity provider during identity verification, the field is not populated with verified data.
Sender responsibility for data ingestion
Senders are responsible for determining which identity attributes are mapped to form fields when using identity-verified data. By configuring verified form fields, the sender controls which identity provider data fields are populated into an agreement.
Senders must ensure that any data ingested through verified form fields is data they are authorized to process and store using Acrobat Sign, and that such use complies with all applicable laws, regulations, and contractual obligations.
Senders must not configure verified form fields to ingest data that customers are prohibited from collecting, processing, or storing under the Acrobat Sign Product Specific Licensing Terms (PSLT). For example, Acrobat Sign may not be used to store payment card data or sensitive authentication data (as defined by PCI DSS), and customers may not process protected health information unless they have entered into a Business Associate Agreement with Adobe.
Adobe does not review, validate, or restrict the data selected by the sender for ingestion through verified form fields.
Field behavior during signing
Verified form fields follow existing Acrobat Sign field behaviors, with identity-aware overrides.
Read-only fields
- Are populated with verified data when the claim is present.
- Cannot be edited by the signer.
- Override any predefined value.
- If the claim is missing, the predefined value is used.
Editable fields
- Are populated with verified data when the claim is present.
- Remain editable by the signer.
- Allow the signer to change the value.
Required fields
- Behave like editable fields
- Require signer input if the claim is missing, empty, or null
Silent failure conditions
Identity-verified data fails silently in all of the following cases:
- The field name does not follow the required syntax.
- The claim name is misspelled or uses incorrect casing.
- The claim is not returned by the identity provider.
- The feature is disabled at the account or group level.
The agreement or web form still sends successfully.
Always validate field behavior in the authoring environment before distributing the agreement or web form.
Signer Identity Report behavior
When an agreement contains one or more verified form fields, the Signer Identity Report – if enabled at the sender’s account or group level – includes a dedicated section listing those fields.
For each verified form field, the Signer Identity Report includes the following information:
- The field name
- The final value
- A single state indicator
Possible states on the Signer Identity Report
States are determined after the agreement is completed. They reflect the final value source and do not validate the configuration during authoring or signing.
Each verified form field is assigned one state only, based on the following priority order.
- Edited - The signer changed the field value during signing.
- Predicate:
- Field is editable, and
- The final value was modified by the signer
- Predicate:
- Verified - The field value originates from identity-verified data and has not been meaningfully altered.
- Predicate:
- Matching identity claim was returned, and
- Final value matches the verified claim value
- Applies to:
- Read-only fields populated from verified data
- Editable fields left unchanged
- The field populated from verified data was edited, but the value remained identical.
- Predicate:
- Predefined - The field retained its default value set by the author.
- Predicate:
- No identity-verified data applied, and
- No higher-priority state applies.
- Predicate:
- Claim Not Present - The referenced identity claim was not returned by the identity provider.
- Predicate:
- Claim name specified in the form field does not exist in the identity provider response.
- Predicate:
- Empty or Null Value - The referenced identity claim was returned without a usable value.
- Predicate:
- Claim exists but is empty or null.
- Empty means an empty string or object.
- Null means the value is explicitly null.
- Predicate:
Notes
- Only one state is assigned per field.
- States do not generate warnings or errors.
- The report reflects outcomes, not configuration errors.