Start a new agreement.
What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
- Enterprise Trial
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Admin Console SSO
- 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
- Group management
- 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
- PDF/A workflows
- Healthcare customer
- New request signature experience
- New custom workflow experience
- New create template experience
- 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
- Enable classic Reporting
- 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
- In-person signing config
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Remove recipients from in-flight agreements
- 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
- Enable hybrid signature flows
- Add myself
- Send only to internal recipients
- 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
User profile and configurable features
- Address Book
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
- Compose in-person agreement
- Recipient signing order
- Hybrid recipient workflow
- 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
- Verified forms
- 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
- Bulk actions
- Hide multiple agreements
- Digitally sign multiple agreements
- Audit Report
- Reporting and Data exports
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Manage Shared 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
- Integration keys
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Combine ordered routing with parallel participation so complex agreements move through the right people at the right time.
Hybrid recipient workflows help senders build agreements where some recipients act in sequence, and others act during the same routing step. Use this workflow when one recipient must complete their action before a group can act, or when several recipients need to act before the agreement moves to the next step.
Adobe Acrobat Sign supports hybrid workflows by combining sequential routing with recipient groups. A recipient group represents one recipient step in the routing order and contains multiple recipients who receive access to the agreement at the same time. The agreement moves forward after the recipient group completes the required action.
Before you begin
- Hybrid recipient routing must be enabled by an administrator.
- Start the agreement as a sequential signing flow before adding the parallel recipient group step.
- Confirm the recipient order before sending the agreement.
- For best performance and manageability, keep hybrid workflows below 50 total participants.
- Electronic seals are not supported in hybrid signature workflows.
How hybrid recipient workflows work
A hybrid workflow starts with a sequential routing structure. One or more steps in that sequence can include a recipient group, allowing multiple recipients to act during the same step.
For example, a hybrid workflow might route like this:
- Recipients 1-3 are a parallel signature group with three members.
- The three members of the group are notified at the same time and can complete their actions in any order within the group.
- All members must complete their actions before the signature flow moves to the next recipient
- Recipient 4 is an individual recipient.
- Recipient 5 is a recipient group with three members.
- All three members of the group are notified at the same time.
- Only the first member to complete the group's action is needed to move the signature flow to the next recipient.
- Recipient 6 is an individual recipient.
(See pattern 3 below)
Create a hybrid workflow
A hybrid workflow starts from a sequential signing order. After the signing order is enabled, each routing step can contain an individual recipient, a parallel recipient group, or a recipient group.
Use a group step wherever multiple people need to act before the agreement moves forward.
-
-
Set the recipient routing to sequential signing order.
-
Add the first routing step:
- Add an Individual recipient if one person should act at this step.
- Add a Group if multiple people should be included at this step.
- Enter a group name.
- Enable All members must complete to define a parallel group, or leave disabled for a recipient group.
- Select Add members and then add all of the members to the group. Define each member's:
- Name (if required)
- Role
- Delivery method (If required)
- Private message (if needed)
- Authentication method
- Select Done.
-
Continue adding individual recipients or groups in the order they should act.
-
Review the full recipient order and Send the agreement when ready.
A recipient group appears as one recipient step in the routing order, even though several people may be available to act for that step. A recipient group appears as one recipient step in the routing order, even though several people may be available to act for that step.
Review participant count before sending
For optimal performance, hybrid workflows should include fewer than 50 participants in total. Count each individual recipient and each member of a recipient group toward the total.
For example:
- 5 individual recipients = 5 participants.
- 1 recipient group with 10 members = 10 participants.
- 1 parallel group with 3 members = 3 participants.
- 5 individual recipients plus one 10-member recipient group plus one 3-member parallel group = 18 total participants.
Larger hybrid workflows can be harder to review, modify, and troubleshoot. They may also take longer to process, especially if the agreement is modified after it's sent.
If the workflow requires 50 or more participants, consider splitting the process into separate agreements or simplifying the routing structure before sending.
Best practices
- Use hybrid workflows when the signing order matters, but multiple recipients need to act during the same stage.
- Use a parallel recipient group when every recipient in the step must complete their action.
- Use a recipient group when any allowed group member can act for one recipient step.
- Use clear group names so senders and admins can understand the routing sequence later.
- Keep the participant count below 50 whenever possible.
- Review the recipient order before sending.
- Use Custom Send Workflows for repeatable, business-critical routing patterns that should not be rebuilt manually each time.
- Avoid adding large groups unless the members truly need to participate in the same agreement step.
Things to know before sending
- A hybrid workflow must start as a sequential signing flow.
- A parallel recipient group contains multiple individual recipients in the same routing step. All recipients in the parallel recipient group must complete before the agreement moves forward.
- Members of a parallel recipient group can complete their actions in any order.
- A recipient group is one recipient step with multiple group members.
- Recipient group completion depends on the group configuration. If only one member is required, the agreement moves forward after one member completes the group action.
- A hybrid workflow can include one or more parallel recipient groups or recipient groups, depending on the agreement routing needs.
- Count each individual recipient and each recipient group member when reviewing total participant count.
- The fewer-than-50 participant guidance is a best-practice recommendation for performance and manageability, not a hard system limit.
- Larger hybrid workflows may be harder to review, modify, and troubleshoot, especially after sending.
- Electronic seals are not supported in hybrid signature workflows.