- SIGNER
- APPROVER
- ACCEPTOR
- FORM_FILLER
- CERTIFIED_RECIPIENT
What's New
Get Started
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
- 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
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- 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
- Set a default time zone
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- Healthcare customer
- Account Setup
-
Signature Preferences
- Well formatted signatures
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow signers to print and place a written signature
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Digital Signatures
- Electronic Seals
- Digital Identity
-
Report Settings
- Security Settings
-
Send settings
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Recipient Agreement Access
- Field flattening
- Modify Agreements
- Private messages
- Allowed signature types
- Reminders
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Signing order
- Liquid mode
- Bio-Pharma Settings
- Notarization Settings
- Payments Integration
- SAML Settings
- 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
- 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
- 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
-
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
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable 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
- Agreement data extraction
- Agreement notifications
- Agreement generation
- Custom Send workflows
- Share users and agreements
Integrate with other products
- 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
Using the Send in Bulk CSV upload option does not support in-app authoring of fields. All fields must be placed on the document template before uploading to the Send in Bulk interface.
Create the CSV file
A CSV file is best created using a spreadsheet application like Excel, Numbers, Google Sheets, etc. Most spreadsheets can export into a CSV format, which is required for the upload to succeed.
Spreadsheets present the data in an easily readable table format, where the rows (i.e., records) and columns (i.e., fields) are easily discernable. When creating your CSV, each row represents one child agreement, and each column is one argument applied to the agreement (like the recipient email and personalized form fields).
Two things to consider before you start to build your CSV:
- The Send in Bulk template allows the configuration of many agreement options, and if the CSV does not explicitly define a setting, the default value from the parent template is used. So if all agreements have the same Agreement name, don't include that column in your CSV file.
- A value does not need to be placed in every field because a column exists. Empty fields are ignored, and the default from the parent Send in Bulk template is used. So there is no need to fill in every field in every record.
The CSV itself can be divided into three meaningful sections:
Customers using a legacy CSV file in the new experience will not be able to insert the Sender as the first signer. A new CSV using the new formatting must be created with the sender defined as the first recipient for each child agreement.
At least one and up to 100 recipients can be included in each child agreement.
Each recipient can be defined by five fields:
- Recipient_X:Email
- Recipient_X:Role
- Recipient_X:Auth_Type
- Recipient_X:Auth_Value
- Recipient_X:Private_Message
Where _X is the recipient index number (Recipient_1, Recipient_2, etc) and the argument after the : is the value used by the system to construct the agreement.
Only the email address is required. All other values can be ignored or inherited from the parent template by omitting the column or leaving the field empty.
Defining recipient values like the recipient name, title, and company can be achieved using uniquely named column headers that map to the like-named fields in the document. See Defining custom fields for merging field data into the agreements below.
Column headers are case-sensitive and must match the field names exactly.
Field values:
:Email - This field accepts any string in an email format (x@y.zz). Values in the :Email field that don't comply with the email format trigger an error.
:Role - Accepts the standard Roles for agreements:
- DELEGATE_TO_SIGNER
- DELEGATE_TO_APPROVER
- DELEGATE_TO_ACCEPTOR
- DELEGATE_TO_CERTIFIED_RECIPIENT
- DELEGATE_TO_FORM_FILLER
:Auth_Type - Accepts one of the below authentication methods. If an authentication method is defined that isn't enabled for the sending group, and error will be generated.
- PASSWORD - Password authentication requires the customer to enter the password value defined in the :Auth_Type field.
- KBA - Knowledge-based Authentication. US authentication only. The recipient is required to answer several questions drawn from public database sources.
- ADOBE_SIGN - Adobe Acrobat Sign authentication. Requires the recipient to authenticate to the Adobe identity system.
- PHONE - Text or Voice authentication delivered to the phone number defined in the :Auth_Value field.
- EMAIL_OTP - One Time Password via email authentication requires the user to enter a numeric password sent to the recipient's email address.
- GOV_ID - Government ID authentication requires the recipient to provide a government-issued identification (e.g., Driver's License or Passport).
:Auth_Value - Only applicable to PHONE and PASSWORD authentications. No other Auth_Type should include an Auth_Value. Accepts a string that defines the value used to validate the authentication method (when applicable).:
- PASSWORD authentication - A string that defines a value the recipient must enter to pass the authentication challenge.
- PHONE authentication - A string of numbers that defines the recipient's phone number. The phone number will be used to communicate the code to the recipient.
- The phone number must be formatted to have a hyphen between the country code and the phone number (e.g., 1-5555551212 and 91-9934765344)
- The phone number format may include a plus at the beginning and hyphens within the number to produce a more human-readable string as desired. (e.g., +1-555-555-1212)
- The phone number must be formatted to have a hyphen between the country code and the phone number (e.g., 1-5555551212 and 91-9934765344)
:Private_Message - A string of up to 1000 characters delivered to the recipient as a private message in their email body and on the e-signing page.
CC_X:Email - The email of an agreement participant who is CC'd to the agreement and only views the agreement once completed. Like the Recipient, the X value is a number that starts with 1 and increments up if you have multiple CC'd parties. e.g., IF you have three CC'd parties you would need to configure three columns: CC_1:EMAIL, CC_2:EMAIL, CC_3:EMAIL