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
- Adding users
- Create function-focused users
- 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
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- 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
- 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
- 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
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- 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
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
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- 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
Support and Troubleshooting
Overview of authored fields
Authoring a document allows the placement of fields to collect recipient data. This data can range from the ubiquitous signature and initial fields to more exotic options like calculated values, hyperlinks to external web pages, and external file attachments.
This article provides a brief summary of each field family and the included unique fields in that family. A link to a more detailed article is available for
Common vs. Advanced form fields
Where all accounts have access to the common field types, higher tiers of service have access to an additional set of advanced form fields and functionality:
Signature Fields:
- Signature
- Digital Signature
- Initials
- Signature Block
- Stamp
Signer Info Fields:
- Title
- Company
- Name
- Date
Data Fields:
- Text Input
- Drop Down
- Check Box
- Radio Button
Transaction Fields:
- Participation Stamp
- Transaction Number
Data Fields:
- Image
More Fields:
- File Attachment
- Hyperlink
Payment Fields:
- Payments (Payment fields are unique in that they require the integration of a third-party service.)
In addition to the above field types, "advanced form fields" also permit the below functionality:
- Conditional field visibility - Available to all field types except the Hyperlink and Transaction Fields
- Calculated field values - A property of the Text Input field
- Field validation: Custom - Regular Expression - A validation option for the Text Input field that allows use of a custom coded regular expression
- Field validation: Custom - Formula - A validation option for the Text Input field that allows use of a calculated value
Field-level field type selection
Within the properties of most field types, there s a drop down value that allows you to change the type of field to another field type.
This will significantly speed up form creation when used in conjunction with Automatic Field Detection.
Signature fields
By default, signature and initials fields are mandatory, as the red asterisk denotes. You can deselect the Required check box in the field properties if you want to make them optional. Each signer needs to have been assigned a required Signature field. If a signer does not have a required signature field assigned, or has only been assigned an optional signature field, Adobe Acrobat Sign adds a Signature block at the bottom of the document.
The signature block is a group of fields. The signature block field cannot be made optional and is always required.
By default, the signature block contains both a signature field, and an e-mail field.
Account Admins can adjust what fields are included in the signature block. Title and company name fields can be included in addition to the signature and e-mail fields.
They can be added by going to the Account page, Signature Preferences, and check the options labeled:
- Require signers to provide their job title when e-signing
- Require signers to provide their company name when e-signing
If signature blocks are appearing at the end of the document, the system was unable to find a required signature field for one or more signers. All signers must have at least one required signature field assigned to them.
A signature block is also added when Signature Preferences have been set to "require signers to provide their job title or company when e-signing" and discrete fields have not been added.
web forms require both a signature field and an Acrobat Sign e-mail field to be present for all signers.
Stamp fields can serve double duty as either a stand alone signature, or in support of another signature fields. For example, you may need to place a personal signature, as well as a corporate seal or Hanko stamp.
Signer info fields
Signer info fields are used to collect specific information stored in Acrobat Sign. Registered users have this information under their profile.
Usually, these fields are automatically populated with the information on record for the assigned user.
The Title and Company fields auto-fill with the Title and Company value if the signer already has an Acrobat Sign account. If the signer does not already have an Acrobat Sign account, they can click into these fields and enter a value. That value is then retained and automatically applied to these field types on documents they sign in the future.
The title and company fields cannot be made optional and are always required fields, as the red asterisk denotes.
The title and company fields can be resized by dragging the hashes in the lower-right corner of the field.
These fields are read-only fields that are automatically populated with the data on file for the signer.
The Signer Name field takes the name value that is entered into the signature field.
The e-mail field is automatically populated with the e-mail address you sent the agreement to.
The Date field is automatically populated with the date the agreement is accessed.
If you want a custom date value or manually entered e-mail address, use a form field and set it up to have a custom validation.
Data fields
Data fields are used to collect additional information from the recipient. It also includes objects the recipient can use to make selections or choose options.
The Text Field is the most versatile field type. It is a fillable text field, and by default it can have any kind of data entered such as an address or short sentence.
The form field can be resized by dragging the hashes in the lower-right corner of the field.
By default, Text Fields only support a single line of text. If you want to create a field that can contain multiple lines of text, open the options window for the form field. Then, select Multi-line Data Entry. Scale the field to an appropriate size to accommodate the multiple lines of data.
The Dropdown field is a list of selections, in which only a single selection can be made from that list. An example would be a drop-down list of states, where the signer can only select a single state from the list.
The drop-down field can be resized by dragging the hashes in the lower-right corner of the field.
Checkboxes are toggle objects and can be checked or deselected at any time. This option is useful for "check-all-that-apply" cases, or as a toggle for a single selection, like opting in for future contact.
Radio buttons are grouped together. The group requires a minimum of two buttons and only allows a single radio button to be selected in the group at any time. If another radio button in that group is selected, the others are deselected. This is ideal for "one-or-the-other" options, like Yes or No.
The Image field can be used to have a recipient attach an image that can later be exported for use. Student ID images, or scanned images of documents like a social security card are possible.
More fields
The file attachment field can be used to attach documents or images to the transaction.
File Attachment fields can be used to collect supporting documents or images from signers during the signing process. The uploaded documents are included as part of the signed document and are attached at the end of the signed agreement after the signature process is complete.
The file attachment field can be resized by dragging the hashes in the lower-right corner of the field.
Attachments are limited to 25 pages and 5 MB.
Supported formats: PNG, JPG, JPEG, GIF, BMP, PDF, DOC, DOCX, WP, TXT, RTF, HTM, or HTML
- The hyperlink field is available to business and enterprise service plans.
- The hyperlink field can be resized by dragging the hashes in the lower-right corner of the field.
- If a hyperlink field is defined as Required, the field must be assigned to a participant.
- Hyperlinks can be assigned using the Everyone participation role, meaning all recipients can click the link.
- Hyperlinks can be configured to navigate the user to a location within the document or to an external URL.
- When a hyperlink is configured with an external target, the recipient is warned that the link is directing them to an external site.
- When a hyperlink is configured with an external target, the recipient is warned that the link is directing them to an external site.
Participation stamps are applied after the assigned recipient signs the agreement. As such, they cannot be accessed or edited by the recipient.
By default, the stamp includes the participant's:
- Name
- Signing time
- Email address
- Title*
- Company*
*Title and company values are imported from the Title and Company fields assigned to the participant in the agreement.
- If the Title and/or Company field isn't present on the agreement, the values are imported from the participant's Acrobat Sign profile (if one exists).
- Otherwise, the values are left empty
Optionally, the participant's Title and Company values can be excluded by checking the Exclude company name and job title in the participation stamp feature located in that administrator's menu under Signature Preferences > Additional Settings:
The Transaction Number stamp will auto-populate with the unique identifying number that indicates the agreement in the Acrobat Sign system. Recipients cannot directly interact with the field.